Introduction - Hotfix Jobs

Hotfix hiring has two ways in. They share the same jobs, applications, interviews, offers, mail, and automations.

Path	Who it is for	Base
HTTP under `/v1/employer`	Dashboard session (employer JWT)	`https://rest.hotfix.jobs`
MCP	Agents with a company API key (`hf_…`)	`https://rest.hotfix.jobs/mcp`

https://rest.hotfix.jobs/v1/employer/applications
https://rest.hotfix.jobs/mcp
https://docs.hotfix.jobs/openapi.json

The public job catalog is a different contract. Use it only when you need live tech jobs on Hotfix search, not hosted hiring for your company.

https://hotfix.jobs/openapi.json

Read these first

Authentication if you call MCP or GET resume with a key.
Jobs, Applications, Interviews, Offers and mail, and Automations before you chain tools.
MCP get started to wire a client, then Supported tools for the tool list.

The API reference is the HTTP playground and operation detail. Each page names the matching MCP tool when one exists. Do not treat rest.hotfix.jobs/openapi.json as the hiring spec.

Rules that surprise people

Creating a job, an offer, a booking link, a draft, or an automation action does not send email. A person still hits Send in the app. GET resume accepts a session or an API key. That path returns the PDF. Hiring stats and webhooks are not published. Do not invent them. Start hiring on hotfix.jobs/pricing. The app is on app.hotfix.jobs.