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

# list_feedback

> Panel feedback on one application's ended interviews: each interviewer's overall verdict (strong_no, no, yes, strong_yes), ratings on the job's interview criteria, and notes, newest interview first. An API key sees every entry. Signed in, a member on a panel who hasn't added theirs sees the others as hidden, with only who submitted and when. Once the job has a hiring team, a member who isn't on it, isn't an owner or admin, and wasn't on the panel sees every entry hidden, with team_only true. MCP tool: list_feedback.



## OpenAPI

````yaml /openapi.json get /v1/employer/applications/{application_id}/feedback
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/applications/{application_id}/feedback:
    get:
      tags:
        - Interviews
      summary: list_feedback
      description: >-
        Panel feedback on one application's ended interviews: each interviewer's
        overall verdict (strong_no, no, yes, strong_yes), ratings on the job's
        interview criteria, and notes, newest interview first. An API key sees
        every entry. Signed in, a member on a panel who hasn't added theirs sees
        the others as hidden, with only who submitted and when. Once the job has
        a hiring team, a member who isn't on it, isn't an owner or admin, and
        wasn't on the panel sees every entry hidden, with team_only true. MCP
        tool: list_feedback.
      operationId: list_feedback
      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:
                interviews:
                  - interview_id: b1c2d3e4-f5a6-7890-1234-56789abcdef0
                    stage: technical
                    starts_at: '2026-09-29T17:00:00+00:00'
                    ends_at: '2026-09-29T18:00:00+00:00'
                    open: true
                    can_submit: false
                    due: false
                    hidden: false
                    team_only: false
                    criteria: []
                    entries:
                      - user_id: user_2abc
                        name: Alex Park
                        email: alex@acme.com
                        on_panel: true
                        submitted_at: '2026-09-29T19:10:00+00:00'
                        updated_at: '2026-09-29T19:10:00+00:00'
                        verdict: strong_yes
                        notes: >-
                          Sketched the fan-out and named the retry storm before
                          I asked.
                        ratings:
                          - id: c_1a2b3c4d
                            name: System design
                            hint: Scale, failure, tradeoffs
                            rating: strong_yes
                        hidden: false
      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.