> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hotfix.jobs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Call them jobs, not postings, listings, or roles.
> To act for an employer, connect to the MCP server at https://rest.hotfix.jobs/mcp and sign in with a Hotfix account. API keys are for HTTP scripts, not MCP.
> Only describe the routes, tools, and numbers these docs publish. If something isn't documented, say so instead of guessing.
> Webhooks are managed in the app under Settings > API > Webhooks. An API key or MCP client can't create or change them.
> Hotfix is the applicant tracking system. Applications land in Applicants in Hotfix and aren't sent to another ATS.
> Creating a draft, offer, or booking link sends nothing. A person sends the email from Hotfix.

# draft_job_description

> A job description to start from, drafted from the title, the requirements, and optionally the team: about the role, what you'll do, and sometimes nice to have, in markdown. It never lists the requirements again; they are the job's own, and every resume is checked against them. Nothing is saved. Shares suggest_requirements' 20 a minute per company. 503 when no draft is available.



## OpenAPI

````yaml /openapi.json post /v1/employer/jobs/description/draft
openapi: 3.1.0
info:
  title: Hotfix hiring API
  version: 1.0.0
  description: >-
    Employer hiring surface under /v1/employer, plus the public company and job
    reads a company builds its own careers page from. Routes take an employer
    session Bearer token. Hiring data routes also accept a company API key
    (hf_…); mail and drafts are session only. Agents should prefer MCP at
    https://rest.hotfix.jobs/mcp, where they sign in with Hotfix. It is not a
    dump of rest.hotfix.jobs/openapi.json.
servers:
  - url: https://rest.hotfix.jobs
    description: Production
security: []
tags:
  - name: Applications
  - name: Jobs
  - name: Careers page
  - name: Interviews
  - name: Offers
  - name: Mail
  - name: Automations
  - name: Fields
paths:
  /v1/employer/jobs/description/draft:
    post:
      tags:
        - Jobs
      summary: draft_job_description
      description: >-
        A job description to start from, drafted from the title, the
        requirements, and optionally the team: about the role, what you'll do,
        and sometimes nice to have, in markdown. It never lists the requirements
        again; they are the job's own, and every resume is checked against them.
        Nothing is saved. Shares suggest_requirements' 20 a minute per company.
        503 when no draft is available.
      operationId: draft_job_description
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                title:
                  type: string
                  description: The job title.
                requirements:
                  type: array
                  items:
                    type: string
                  description: 1 to 7 requirements, in order.
                team:
                  type: string
                  description: Optional. The job's team, like backend; see create_job.
              required:
                - title
                - requirements
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
              example:
                description: >-
                  ## About the role

                  Own the services behind our public API and keep them fast and
                  boring in production.


                  ## What you'll do

                  - Run the deploy pipeline and observability for the API

                  - Harden auth and multi-tenant boundaries


                  ## Nice to have

                  - Experience with Terraform
        '503':
          description: No draft is available right now.
      security:
        - ApiKey: []
        - BearerAuth: []
components:
  securitySchemes:
    ApiKey:
      type: http
      scheme: bearer
      description: >-
        Company API key minted at Settings → API. Prefix hf_. Accepted on hiring
        data routes. Not accepted on MCP.
    BearerAuth:
      type: http
      scheme: bearer
      description: Employer session JWT from Better Auth.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.