Skip to main content

Issuing CFDIs in the Multi-issuer API

The Multi-issuer API lets you issue CFDIs using different issuing RFCs from a single integration. To issue receipts with a given RFC, that issuer must have its Digital Seal Certificates (CSD) registered beforehand.
Each issuing RFC must have its own CSDs registered before it can generate CFDIs. See the CSD management guide: CSD management

Endpoint V4 New

General data

Idempotency and retries Facturama identifies an operation by the combination of Folio and Date. To avoid duplicate receipts, generate both values only once when the operation starts and reuse them unchanged on every retry.
string
required
Unique identifier of the operation, generated by your system.
string
required
Start date and time of the operation, in YYYY-MM-DDTHH:mm:ss format.
Do not regenerate Folio or Date on retries, and do not use the current system date/time to recalculate Date. Any change to these values makes Facturama treat the retry as a new operation.
For example, an operation with:
Keeps these same values on every retry, no matter how much time has passed since the original request.

Issuer node

You must include the Issuer node, which identifies the RFC that will issue the receipt.

Receiver node

You must include the Receiver node, which identifies the receiver RFC of the receipt.

Line items

Complete form

API reference

To see the complete definition of the available fields, parameters, and response examples, refer to the reference documentation:

Additional information for the printed representation

In addition to the fiscal data required by the SAT, you can include supplementary information to customize the printed representation of the CFDI. The available optional fields include:
  • Issuer’s logo.
  • Issuer’s address.
  • Receiver’s address.
  • Observations or additional notes.
These fields are not part of the receipt’s fiscal information, but they can be used to enrich the PDF or printed version.
For version 4 of the Multi-issuer API, the JSON returns the invoice’s XML in the request response.
Response
Where
  • Id : Unique identifier of the invoice
  • XmlBase64: XML content in base64
  • OriginalString : Original String
  • TaxStamp.Uuid : Unique identifier of the invoice before the SAT

Endpoint V3

For version 3 of the Multi-issuer API, the JSON returns a general summary of the invoice.

Successful response