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

# Get a single stamped CFDI by its folio fiscal UUID

> Authenticate with either a Supabase session (member of the invoice's organization) or an API key belonging to that same organization. Returns the same shape as the `POST /invoices` response — use this to recover an invoice's metadata/XML if the original create response was lost.



## OpenAPI

````yaml https://api.timbrix.mx/api/openapi.json get /invoices/{uuid}
openapi: 3.0.0
info:
  title: Timbrix API
  description: >-
    API de facturación electrónica CFDI 4.0 para México, con servidor OAuth2
    para gestionar organizaciones, miembros y webhooks. Compatible con agentes
    de IA — ver la extensión `x-ai-agent-friendly` en la raíz de esta spec.


    REST API with OAuth2 server for managing organizations, members, and
    webhooks.
  version: '1.0'
  contact: {}
servers: []
security: []
tags:
  - name: organizations
    description: Organization management endpoints
  - name: oauth
    description: OAuth2 authentication and authorization
  - name: webhooks
    description: Webhook configuration and delivery
  - name: users
    description: User information endpoints
  - name: api-keys
    description: API Keys management and validation
paths:
  /invoices/{uuid}:
    get:
      tags:
        - invoices
      summary: Get a single stamped CFDI by its folio fiscal UUID
      description: >-
        Authenticate with either a Supabase session (member of the invoice's
        organization) or an API key belonging to that same organization. Returns
        the same shape as the `POST /invoices` response — use this to recover an
        invoice's metadata/XML if the original create response was lost.
      operationId: InvoicesController_get
      parameters:
        - name: uuid
          required: true
          in: path
          schema:
            type: string
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InvoiceResponseDto'
        '403':
          description: Caller does not belong to the invoice's organization
        '404':
          description: uuid does not match any invoice
      security:
        - apiKey: []
        - bearer: []
components:
  schemas:
    InvoiceResponseDto:
      type: object
      properties:
        id:
          type: string
          description: Timbrix invoice record ID
          example: 0f2a1c3e-1a2b-4c3d-9e8f-1234567890ab
        uuid:
          type: string
          description: Folio fiscal UUID asignado por el SAT vía PAC
          example: d3bfbc57-44af-4390-a064-f0afab85e5df
        status:
          type: string
          enum:
            - valid
          example: valid
        type:
          type: string
          enum:
            - I
            - E
            - T
          example: I
          description: I = Ingreso, E = Egreso, T = Traslado
        series:
          type: string
          example: A
        folioNumber:
          type: string
          example: '1'
        total:
          type: number
          example: 116
        date:
          type: string
          example: '2026-07-30T22:50:00'
        xml:
          type: string
          description: XML del CFDI timbrado (UTF-8)
        createdAt:
          type: string
          example: '2026-07-30T22:50:03.412Z'
        environment:
          type: string
          enum:
            - sandbox
            - production
          example: production
          description: >-
            Ambiente en el que se timbró el CFDI. Los CFDI de sandbox no tienen
            validez fiscal ante el SAT.
      required:
        - id
        - uuid
        - status
        - type
        - series
        - folioNumber
        - total
        - date
        - xml
        - createdAt
        - environment
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: X-API-Key
      description: 'API Key for authentication (format: sk_...)'
    bearer:
      scheme: bearer
      bearerFormat: JWT
      type: http

````