Get Invoice
Authenticate with either a Supabase session (member of the invoice’s organization) or an API key with the read:invoices scope belonging to that same organization. This is a FLAT route — no organizationId in the URL, unlike create/list above; the organization is resolved from the invoice’s globally-unique uuid. Returns the same shape as the Create Invoice response, including the full stamped XML inline.
/organizations/{organizationId}/ in the URL. The invoice’s uuid (its folio fiscal, globally unique across all organizations) is enough to resolve the owning organization server-side, combined with the caller’s own auth context (session or API key).
Authentication
Accepts either:- A Supabase Bearer session (
Authorization: Bearer <token>) — the authenticated user must be a member of the invoice’s organization. - An API key (
X-API-Key: sk_...) with theread:invoicesscope — the key’s own organization must match the invoice’s organization, or the request is rejected with403 Forbidden.
Path Parameters
Example Request
Example Response
status, type, and the full xml — fields not
present in the List Invoices summary shape. If
you only need the XML file itself (not wrapped in JSON), use Download Invoice
XML instead.Common Errors
401 Unauthorized
Missing or invalid Bearer token / API key.403 Forbidden
The authenticated user is not a member of the invoice’s organization, or the API key does not have theread:invoices scope / belongs to a different organization than the one that owns the invoice.
404 Not Found
uuid does not match any invoice.Authorizations
API Key for authentication (format: sk_...)
Path Parameters
Folio fiscal UUID of the invoice
Response
Timbrix invoice record ID
"0f2a1c3e-1a2b-4c3d-9e8f-1234567890ab"
Folio fiscal UUID asignado por el SAT vía PAC
"d3bfbc57-44af-4390-a064-f0afab85e5df"
valid "valid"
I = Ingreso, E = Egreso, T = Traslado
I, E, T "I"
"A"
"1"
116
"2026-07-30T22:50:00"
XML del CFDI timbrado (UTF-8)
"2026-07-30T22:50:03.412Z"