> ## 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
> Product noun is jobs.
> MCP at https://rest.hotfix.jobs/mcp is the hiring contract for agents. Clients sign in with Hotfix; API keys are for HTTP only.
> Do not invent unpublished REST or hiring stats. Webhooks are set up in the app; there is no REST route or MCP tool to manage them.
> Do not mention Greenhouse, Ashby, Quick Apply, or claim.
> Creating a draft, offer, or booking link does not send email.

# search_applications

> Find applications by what was written about or to the candidate: name, email, notes, email (the subject and preview Hotfix stores, not whole message bodies), and resumes already read as fields with get_resume. Archived and rejected applications are included. A term matches whole words and their forms, so interview finds interviewed, and text inside words while you type. Results with a name or email match come first, then by the newest match. Each result keeps up to three matches; total_matches counts them all. A query under two characters returns an empty list. MCP tool: search_hiring.



## OpenAPI

````yaml /openapi.json get /v1/employer/search
openapi: 3.1.0
info:
  title: Hotfix hiring API
  version: 1.0.0
  description: >-
    Employer hiring surface under /v1/employer, plus the public careers page
    reads under /v1/boards. 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/search:
    get:
      tags:
        - Applications
      summary: search_applications
      description: >-
        Find applications by what was written about or to the candidate: name,
        email, notes, email (the subject and preview Hotfix stores, not whole
        message bodies), and resumes already read as fields with get_resume.
        Archived and rejected applications are included. A term matches whole
        words and their forms, so interview finds interviewed, and text inside
        words while you type. Results with a name or email match come first,
        then by the newest match. Each result keeps up to three matches;
        total_matches counts them all. A query under two characters returns an
        empty list. MCP tool: search_hiring.
      operationId: search_applications
      parameters:
        - name: q
          in: query
          required: false
          description: What to look for. Up to 200 characters.
          schema:
            type: string
        - name: limit
          in: query
          required: false
          description: Most applications to return, 1 to 50.
          schema:
            type: integer
            default: 20
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
              example:
                data:
                  - application_id: 7c9e6679-7425-40de-944b-e07fc1f90ae7
                    applicant_name: Ada Lovelace
                    applicant_email: ada@example.com
                    job_id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
                    job_title: Staff Engineer
                    status: considering
                    archived: false
                    matches:
                      - source: note
                        snippet: >-
                          Strong on Rust and distributed systems. Interviewed
                          well.
                        at: '2026-09-21T15:04:05+00:00'
                        ref_id: 0fedcba9-8765-4321-0abc-def012345678
                      - source: resume
                        snippet: Rust, Go, Kubernetes
                        at: null
                        ref_id: null
                    total_matches: 2
        '422':
          description: limit is outside 1 to 50, or q is longer than 200 characters.
      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.