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

# List every dated API version and how to pin one (public, no auth).

> Discovery endpoint for dated versioning. Returns every supported version with a human- and agent-readable changelog, the current version, and how to pin one via the `Invoice-Version` header. Requires no API key.



## OpenAPI

````yaml /api-reference/openapi.json get /v1/versions
openapi: 3.1.0
info:
  title: Invoice API
  description: >-
    Mexican CFDI 4.0 invoicing API. Versioned via the Invoice-Version header;
    current: 2026-07-15. See GET /v1/versions.
  version: 0.1.0
servers:
  - url: https://api.newinvoice.dev
    description: Production
  - url: http://localhost:3000
    description: Local development
security:
  - bearerAuth: []
tags:
  - name: api_keys
    description: Platform API-key lifecycle (create, list, revoke)
  - name: accounts
    description: 'Connect: platform-owned connected accounts (multi-tenant)'
  - name: fiscal_profiles
    description: Emitter RFC + CSD/FIEL registration
  - name: invoices
    description: Create, stamp, cancel CFDI 4.0 invoices
  - name: validations
    description: Validate arbitrary CFDI XML
  - name: downloads
    description: SAT descarga masiva jobs
  - name: webhook_endpoints
    description: HMAC-signed event delivery
  - name: events
    description: Event log
  - name: balance
    description: Remaining stamp credits
  - name: usage
    description: Metered usage records (stamps consumed)
  - name: catalogs
    description: SAT reference catalogs (uso CFDI, payment forms/methods, tax regimes, …)
  - name: docs
    description: Served documentation (error catalog + guides)
paths:
  /v1/versions:
    get:
      tags:
        - versions
      summary: List every dated API version and how to pin one (public, no auth).
      description: >-
        Discovery endpoint for dated versioning. Returns every supported version
        with a human- and agent-readable changelog, the current version, and how
        to pin one via the `Invoice-Version` header. Requires no API key.
      parameters:
        - $ref: '#/components/parameters/InvoiceVersion'
        - $ref: '#/components/parameters/InvoiceAccount'
      responses:
        '200':
          description: The version registry.
          content:
            application/json:
              schema:
                type: object
                required:
                  - object
                  - data
                  - current
                  - how_to_pin
                properties:
                  object:
                    type: string
                    enum:
                      - list
                  current:
                    type: string
                  how_to_pin:
                    type: string
                  data:
                    type: array
                    items:
                      type: object
                      required:
                        - version
                        - summary
                        - changes
                      properties:
                        version:
                          type: string
                        summary:
                          type: string
                        changes:
                          type: array
                          items:
                            type: string
                        deprecated:
                          type: object
                          properties:
                            sunsetAt:
                              type: string
                              format: date-time
              example:
                object: list
                data:
                  - version: '2026-07-10'
                    summary: Initial dated release.
                    changes:
                      - Initial public API surface.
                  - version: '2026-07-15'
                    summary: Adds machine-navigable error and list metadata.
                    changes:
                      - >-
                        problem+json error bodies now include `doc_url`
                        (absolute link to the error reference).
                      - >-
                        List envelopes now include `url` (the path the list was
                        requested from).
                current: '2026-07-15'
                how_to_pin: >-
                  Pin a version by sending the `Invoice-Version: <date>` request
                  header, or by attaching a pinned version to an API key. Omit
                  both to track the current version. An unknown version in the
                  header is rejected with 400 request.invalid_version.
          headers:
            Request-Id:
              $ref: '#/components/headers/RequestId'
            Invoice-Version:
              $ref: '#/components/headers/InvoiceVersionResponse'
            traceparent:
              $ref: '#/components/headers/Traceparent'
      security: []
components:
  parameters:
    InvoiceVersion:
      name: Invoice-Version
      in: header
      required: false
      description: >-
        Pin a dated API release (Stripe-style). Omit to use the current version.
        An unknown value returns 400 `request.invalid_version`. Echoed back on
        every response.
      schema:
        type: string
        example: '2026-07-10'
    InvoiceAccount:
      name: Invoice-Account
      in: header
      required: false
      description: >-
        Connect: act on behalf of one of your connected accounts (its
        `acct_…`/`org_…` id). Omit to act as your own organization. Not honored
        on /v1/api_keys.
      schema:
        type: string
        example: org_2P9connectedacct
  headers:
    RequestId:
      description: >-
        Unique id for this request. Also the `request_id` in every error body —
        log it and quote it to support; idempotency keys off it too.
      schema:
        type: string
        example: req_2P9K3sample
    InvoiceVersionResponse:
      description: >-
        The dated API version resolved for this request (request header → key
        pin → current). Echoed on every response.
      schema:
        type: string
        example: '2026-07-15'
    Traceparent:
      description: >-
        W3C Trace Context. When you send a valid `traceparent`, the response
        continues the trace (same trace-id, a fresh span-id, sampled flag).
      schema:
        type: string
        example: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: 'API key: `Authorization: Bearer sk_test_...` or `sk_live_...`.'

````