> ## 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.

# suggest_requirements

> Requirements to start from: up to 3 drafted from the job's title and description, and those your company used on its other jobs, newest first. Nothing is saved; pick and edit them before sending requirements on create_job or update_job. drafted is empty when the description is, or when no draft is available. Limited to 20 a minute per company.



## OpenAPI

````yaml /openapi.json post /v1/employer/jobs/requirements/suggest
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/requirements/suggest:
    post:
      tags:
        - Jobs
      summary: suggest_requirements
      description: >-
        Requirements to start from: up to 3 drafted from the job's title and
        description, and those your company used on its other jobs, newest
        first. Nothing is saved; pick and edit them before sending requirements
        on create_job or update_job. drafted is empty when the description is,
        or when no draft is available. Limited to 20 a minute per company.
      operationId: suggest_requirements
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                title:
                  type: string
                  description: The job title.
                description:
                  type: string
                  description: The job description to draft from.
                job_id:
                  type: string
                  description: >-
                    Optional. The job being edited, so its own requirements
                    aren't offered back under used.
              required:
                - title
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
              example:
                drafted:
                  - Has shipped Go code in production
                  - Has worked with PostgreSQL at scale
                  - Has 5+ years building backend systems
                used:
                  - Has been on an on-call rotation
      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.