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

# List partner status variants

> Returns all status variants for the authenticated partner, each with its
mapped internal category. Ordered by category sort_order.




## OpenAPI

````yaml openapi.yaml get /reference/status
openapi: 3.1.0
info:
  title: Thalamus Partner API
  description: >
    API for external systems (n8n, Zendesk connectors, etc.) to create and
    manage

    tickets, contacts, organizations, and comments in Thalamus.


    ## Authentication

    All endpoints require a Bearer token in the Authorization header.

    API keys are issued per partner and follow the format
    `nerds_{environment}_{random}`.

    The partner context (partner_uuid) is derived from the API key — no need to
    pass it in the request body.


    ## Conventions

    - All create/update endpoints are idempotent (upsert) — if the `id` already
    exists for the partner, the record is updated.

    - IDs in path parameters and request/response bodies refer to the canonical
    identifiers from the partner's source system (e.g., Zendesk ticket ID).

    - Timestamps use ISO 8601 format.

    - All responses follow `{ success, data?, message?, error? }` shape.

    - POST returns `201` when a new record is created, `200` when an existing
    record is updated.

    - Only provided fields are updated — omitted fields remain unchanged
    (partial update).
  version: 1.3.0
  contact:
    name: Thalamus Engineering
    email: development@nerds.nl
servers:
  - url: https://thalamus.nerds.nl/api/v1/partner
    description: Production
  - url: http://localhost:3001/api/v1/partner
    description: Local development
security:
  - BearerAuth: []
tags:
  - name: Tickets
    description: Create, update, and retrieve tickets
  - name: Comments
    description: Create comments on tickets
  - name: Contacts
    description: Create, update, and retrieve contacts
  - name: Organizations
    description: Create, update, and retrieve organizations
  - name: Tasks
    description: Create task records (callbacks, appointments, etc.)
  - name: References
    description: Manage reference data (statuses, types, groups, categories, agents)
paths:
  /reference/status:
    get:
      tags:
        - References
      summary: List partner status variants
      description: |
        Returns all status variants for the authenticated partner, each with its
        mapped internal category. Ordered by category sort_order.
      operationId: getStatuses
      responses:
        '200':
          description: List of status variants with mapped categories
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StatusVariantListResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    StatusVariantListResponse:
      type: object
      properties:
        success:
          type: boolean
          example: true
        data:
          type: array
          items:
            type: object
            properties:
              uuid:
                type: string
                format: uuid
              id:
                type: string
                description: Machine-readable status identifier
                example: waiting_on_customer
              label:
                type: string
                example: Waiting on Customer
              source_system:
                type: string
                nullable: true
                example: freshdesk
              status:
                type: string
                enum:
                  - active
                  - inactive
              mapped_status:
                $ref: '#/components/schemas/MappedStatusCategory'
                nullable: true
    MappedStatusCategory:
      type: object
      description: The internal default category a status variant maps to
      properties:
        uuid:
          type: string
          format: uuid
        value:
          type: string
          description: Category key (new, open, hold, pending, solved, closed)
          example: pending
        label:
          type: string
          example: Pending
        sort_order:
          type: integer
          example: 4
        color:
          type: string
          nullable: true
          description: Hex color for the status pill in the UI
          example: '#8b5cf6'
        description:
          type: string
          nullable: true
          description: Human-readable description of this category
          example: Ticket is pending awaiting response from the ticket requester
    ErrorResponse:
      type: object
      properties:
        success:
          type: boolean
          example: false
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            details:
              type: array
              nullable: true
              items:
                type: object
                properties:
                  field:
                    type: string
                  message:
                    type: string
  responses:
    Unauthorized:
      description: Missing or invalid API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            error:
              code: UNAUTHORIZED
              message: Invalid or revoked API key
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: Partner API key (e.g. `nerds_live_a8f3d9k2m5n7p1q4r6t8v0w2x4y6z8`)

````