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

# List person document types

> Returns every active person document type for the organization, ordered by name. No pagination — the full list is always returned.

Document types are configurable per organization, so the available keys differ between organizations. Call this to discover valid `document_types` values for `POST /v1/persons/search` and `GET /v1/persons/{id}/documents`, and valid `type` values when uploading a document.



## OpenAPI

````yaml /api-reference/openapi-v1.json get /v1/persons/document-types
openapi: 3.1.0
info:
  title: Stardex API (v1)
  version: 1.0.0
  description: >-
    Stardex ATS API — manage candidates, jobs, companies, and recruiting
    workflows.
servers:
  - url: https://api.stardex.ai
    description: Production API server
security:
  - bearerAuth: []
tags:
  - name: Persons
    description: Manage person records — contacts, work history, and custom fields.
  - name: Jobs
    description: Manage job postings — pipeline stages, team members, and custom fields.
  - name: Candidates
    description: Manage candidate records and pipeline stage transitions.
  - name: Companies
    description: Browse and retrieve company records.
  - name: Lists
    description: Create, search, and retrieve saved person and company lists.
  - name: Person Activities
    description: Create and manage activity records (notes, emails, meetings) for persons.
  - name: Team Members
    description: List team members for use in search filters and assignments.
  - name: Custom Fields
    description: Retrieve custom field definitions and tag options for search filters.
paths:
  /v1/persons/document-types:
    get:
      tags:
        - Persons
      summary: List person document types
      description: >-
        Returns every active person document type for the organization, ordered
        by name. No pagination — the full list is always returned.


        Document types are configurable per organization, so the available keys
        differ between organizations. Call this to discover valid
        `document_types` values for `POST /v1/persons/search` and `GET
        /v1/persons/{id}/documents`, and valid `type` values when uploading a
        document.
      operationId: listPersonDocumentTypes
      responses:
        '200':
          description: Document types fetched
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PersonDocumentTypesResponse'
              example:
                success: true
                data:
                  - type: resume_doc
                    name: Resume
                  - type: cover_letter
                    name: Cover Letter
                  - type: reference
                    name: Reference
                  - type: resume_link
                    name: Resume Link
                  - type: additional_links
                    name: Additional Links
                  - type: transcript
                    name: Transcript
                  - type: work_sample
                    name: Work Sample
                  - type: offer_letter
                    name: Offer Letter
                  - type: assessment
                    name: Assessment
                  - type: other
                    name: Other
        '400':
          description: Validation error
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    enum:
                      - false
                    description: Always false for error responses.
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                        description: >-
                          Machine-readable error code (e.g. "VALIDATION_ERROR",
                          "NOT_FOUND").
                      message:
                        type: string
                        description: Human-readable error description.
                    required:
                      - code
                      - message
                required:
                  - success
                  - error
        '404':
          description: Resource not found
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    enum:
                      - false
                    description: Always false for error responses.
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                        description: >-
                          Machine-readable error code (e.g. "VALIDATION_ERROR",
                          "NOT_FOUND").
                      message:
                        type: string
                        description: Human-readable error description.
                    required:
                      - code
                      - message
                required:
                  - success
                  - error
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    enum:
                      - false
                    description: Always false for error responses.
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                        description: >-
                          Machine-readable error code (e.g. "VALIDATION_ERROR",
                          "NOT_FOUND").
                      message:
                        type: string
                        description: Human-readable error description.
                    required:
                      - code
                      - message
                required:
                  - success
                  - error
components:
  schemas:
    PersonDocumentTypesResponse:
      type: object
      properties:
        success:
          type: boolean
          enum:
            - true
        data:
          type: array
          items:
            $ref: '#/components/schemas/PersonDocumentType'
      required:
        - success
        - data
    PersonDocumentType:
      type: object
      properties:
        type:
          type: string
          description: >-
            Type key. Use in document_types when filtering POST
            /v1/persons/search or GET /v1/persons/{id}/documents.
        name:
          type: string
          description: Display name shown in the app (e.g. "Resume").
      required:
        - type
        - name
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Authenticate with a Bearer token: API key, OAuth token, or session
        token.

````