Skip to main content

​
Query by ID

Returns a summary of the issued CFDI.

​
Query parameters

​
string
required
Unique identifier of the CFDI.
​
string
required
Corresponds to the type of CFDI you are trying to query. Allowed values:
This endpoint will only show documents issued through API Web.

​
Other search filters

Endpoint
​
string
required
Integer that identifies the page of results to query.
Examples:
  • page=0 = Represents the first 10 items (1 through 10).
  • page=1 = Represents the second 10 items (11 through 20).

​
Search by CFDI status

Endpoint
​
string
Indicates the status of the invoices you want to query.
Where:
  • all: Represents every available invoice regardless of its current status (active, pending, canceled).
  • active: Represents every invoice that is active/valid.
  • canceled: Represents every canceled invoice.

​
Search by CFDI folio

​
string
Indicates the exact folio you want to query. The response will show every invoice that has the specified value.

​
Invoice folio range

​
string
Parameter that indicates the folio number from which invoices start to be shown.
​
string
Parameter that indicates the folio number up to which invoices are shown.
Combining the folio parameter with folioStart and folioEnd in the same search can return incorrect filtered content.

​
Search by issue date range

​
string
Parameter that indicates the start date and time from which invoices start to be shown, specified in yyyy-mm-ddThh:mm:ss format.
​
string
Parameter that indicates the end date and time up to which invoices are shown, specified in yyyy-mm-ddThh:mm:ss format.
​
string
Parameter that indicates the name or legal name of the invoice receiver. You can send it complete or only a part of it.

​
Other available filters

​
string
Parameter that indicates the order number.
​
string
Parameter that indicates the series.
​
string
Parameter that indicates the payment method (PUE || PPD).

​
Considerations

  • The type parameter is required.
  • Every other parameter is optional.
  • Filters can be combined to build more precise searches.
  • The rfc and taxEntityName parameters accept partial matches.
  • Dates must be sent in yyyy-mm-ddThh:mm:ss format.
  • Pagination starts at page 0.
  • Each request returns a maximum of 10 records.