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

# resume_text

> The resume to read, word for word as the applicant wrote it, never summarized. format markdown is Hotfix's copy laid out as markdown; format text is the text as extracted from the file, when the layout couldn't be kept without changing a word. 404 when there is no resume. 422 with code unreadable when the file has no text, such as a scan: download it from resume instead. MCP tool: get_resume.



## OpenAPI

````yaml /openapi.json get /v1/employer/applications/{application_id}/resume/text
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/applications/{application_id}/resume/text:
    get:
      tags:
        - Applications
      summary: resume_text
      description: >-
        The resume to read, word for word as the applicant wrote it, never
        summarized. format markdown is Hotfix's copy laid out as markdown;
        format text is the text as extracted from the file, when the layout
        couldn't be kept without changing a word. 404 when there is no resume.
        422 with code unreadable when the file has no text, such as a scan:
        download it from resume instead. MCP tool: get_resume.
      operationId: resume_text
      parameters:
        - name: application_id
          in: path
          required: true
          description: Application UUID.
          schema:
            type: string
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
              example:
                format: markdown
                body: >-
                  ## Experience


                  ### Senior Software Engineer, Northvale Cloud


                  - Own the Go control-plane service that provisions managed
                  Postgres clusters for 9,000 customers
      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.