Use Claude to interact with Hireflix

What is this?

Hireflix publishes a skill file at hireflixsl.mintlify.app/skill.md. It contains everything an AI (we use Claude in this example) needs to talk to the Hireflix API directly — the GraphQL schema and example queries — so that once you provide your API key, you can ask Claude to do things in plain English instead of writing GraphQL yourself. That includes building a position from scratch (name, questions, intro/outro, timing) just by describing it in chat.

Quick path:

1. Complete setup — allow network access and upload the skill file to Claude.
2. Create a position via Claude chat — describe a role in plain English, Claude builds it.
3. Explore your account with Claude — ask about positions, stats, and interview results.

You’ll need a Hireflix API key to use the skill. If you don’t have one yet, follow the Quickstart to create an account and generate a key. You’ll also need to complete the network egress setup below before starting your chat session — see step 1.

Setup

1. Allow Hireflix domains in your network egress settings

   In Claude, go to Settings → Capabilities, scroll all the way down to the Allow network egress section, and enable the domain allowlist. Add all three of the following domains before you start a new chat — all three are required, regardless of what you’ll be asking Claude to do:

   • api.hireflix.com — the GraphQL API endpoint Claude talks to for every query and mutation.
   • media.hireflix.com — where signed video playback URLs resolve; needed whenever Claude fetches or plays back an interview video.
   • com-hireflix-production-media.s3-accelerate.amazonaws.com — the signed S3 URL Hireflix issues for video uploads (intro, outro, or per-question videos).

   Missing any one of these three domains can cause requests to silently fail partway through a task (e.g. Claude can create a position but can’t upload the video you attached). Add all three now to avoid troubleshooting it later.

   
2. Get the Hireflix skill file

   Open hireflixsl.mintlify.app/skill.md and save the page as skill.md. You can hit CTRL + S or on Mac CMD + S to store the page as skill.md on your machine.

3. Upload the skill to Claude

   Still under Settings → Skills, upload the skill.md file you just saved by clicking the “Add” button and selecting “Upload a skill”.

   
4. Start a new chat and add your API key

   Start a new chat (so the network egress rule from step 1 applies), and give Claude your Hireflix API key so it can authenticate against api.hireflix.com. See the Quickstart if you still need to create one.

   When sharing an API key with Claude AI, make sure to revoke it after your session has ended as a safety precaution.

Create a position via Claude chat

Once the skill is set up, the fastest way to build a new position is to just describe it to Claude in a normal chat message — no GraphQL required. Claude uses the createPosition mutation from the skill file (and the matching upload mutations if you attach video files) to build the position, question by question, exactly as you describe it.

The three templates below go from bare minimum to full control. Pick whichever matches how much you want to specify versus leave at Hireflix’s defaults, copy it into your chat with Claude, fill in the bracketed values, and attach any video files you mention — Claude uploads them for you.

You can also just ask Claude “what info do you need to create a position?” — but a free-form ask won’t necessarily surface every option (per-question video prompts, timing overrides, tags) the way these templates do.

Question titles are capped at 40 characters — short enough that most titles will just be a label. Use the optional description (up to 1200 characters) for the actual instructions or context the candidate needs; you’ll want one on most questions.

Minimal template

The fastest option: just the role and the questions. Claude will use Hireflix’s defaults — video answers, no intro/outro, 30 seconds thinking time, 2 minutes to answer. You can always add an intro/outro, branding, or per-question overrides later from the dashboard, or by asking Claude to update the position.

Create a Hireflix position called "[Position name]" with these questions:
1. Title: [short title, max 40 characters]
   Description (optional): [more context or instructions for the candidate]
2. Title: [...]
   Description (optional): [...]
3. Title: [...]
   Description (optional): [...]

When to use: quick screening rounds, internal tests, or when you just want something usable in the dashboard in one message and will fine-tune it there later.

Simple template

A lighter version for most day-to-day use: a shared outro video, a plain question list, and one question that needs something different. See Tailoring the Interview if you want to know what the answer time limit actually controls for candidates.

Create a Hireflix position called "[Position name]".

Outro video: [file: outro.mp4]
Outro title: [e.g. "Thanks for applying!"]
Outro subtitle: [e.g. "We'll be in touch soon."]

Questions:
1. Title: [short title, max 40 characters]
   Description (optional): [more context or instructions for the candidate]
2. Title: [...]
   Description (optional): [...]
3. Title: [...]
   Description (optional): [...]
4. Title: [...]
   Description (optional): [...]

Question 3 should have a [90-second / no] time limit — all others can use the defaults.

Always name the attached file clearly, or say explicitly what it’s for — e.g. outro.mp4, or “this file is the outro video”. Claude matches uploaded files to their slot by what you tell it, not by guessing from an ambiguous filename like video1.mp4.

Outro title and subtitle are required as soon as a position has an outro at all — even if all you’re adding is the video. No custom copy in mind? Tell Claude to use its own short thank-you text instead of leaving these blank.

When to use: most standard hires — you have a closing video ready but don’t need to micromanage every question.

Full template

Use this when you want full control: a custom intro/outro video, shared defaults for every question, and one question that needs different rules than the rest. These map to the same settings you’d configure by hand in Tailoring the Interview (thinking time, answer time limit) and the interview builder (intro/outro, per-question video prompts, tags).

Create a Hireflix position called "[Position name]".

Tags: [tag1], [tag2]

Intro video: [file: intro.mp4, or "none"]

Outro video: [file: outro.mp4, or "none"]
Outro title: [e.g. "Thanks for applying!"]
Outro subtitle: [e.g. "We'll be in touch soon."]

Default settings for all questions:
- Format: video
- Thinking time: [e.g. 30 seconds]
- Answer time limit: [e.g. 90 seconds]

Questions:
1. Title: [short title, max 40 characters]
   Description (optional): [more context or instructions for the candidate]
2. Title: [...]
   Description (optional): [...]
3. Title: [...]
   Description (optional): [...]
4. Title: [...]
   Description (optional): [...]
   Video: q4.mp4

For question 4, use these custom settings instead of the defaults:
- Thinking time: [value or "none"]
- Answer time limit: [value or "none"]

When attaching several video files in the same message, name each one so Claude can tell them apart — e.g. intro.mp4, outro.mp4, q4.mp4 — or spell it out in the text (“the second file is for question 4”). With multiple files and no clear mapping, Claude has to guess which video goes where.

Outro title and subtitle are required as soon as a position has an outro at all — even if all you’re adding is the video. No custom copy in mind? Tell Claude to use its own short thank-you text instead of leaving these blank.

“Format” here describes the question, not the candidate’s answer — candidates always respond by recording video regardless of this setting. video means the question shows a recorded video prompt (attach the file); text means the candidate just sees the question title and description, with no video prompt.

When to use: onboarding a new role from scratch, or any position where one question needs different rules than the rest (e.g. a question answered without a video prompt, or a single question with its own recorded prompt).

Notes for all templates:

• Attach video files directly in the chat message — Claude uploads them for you, as long as you’ve allowed all three domains from the setup step above.
• If you don’t specify tags, format, or timing, Claude applies Hireflix’s defaults (video answers, no time limit).
• You can always ask Claude to list draft questions for a role first, then paste one of these templates back with the ones you like.

Explore your account with Claude

With your API key set for the session, try asking Claude things like (make sure to first create a position so you have some dummy data):

• “Can you help me list all positions for Hireflix in my account?”
• “Can you pull interview stats (per stage) for each of the positions (total, pending, to evaluate, shortlisted, and discarded)?”
• “Can you give me an overview of the questions and answers for the following completed interview for position <position-id>?”
• “Can you download all videos for position with ID <position-id>?”
• “Can you invite <firstname> <lastname> <email> to my new position?”

Claude will use the schema and examples from the skill file to write and run the right GraphQL queries against your account behind the scenes.

Claude's response after being asked to list all positions

What’s next?

GraphQL Basics

Understand the queries and mutations Claude is running on your behalf.

Interview Management

Explore the full interview flow: from inviting candidates to reviewing completed interviews.