.
) in the name like period.from
are a way to denote object paths. For example, period.from
should actually be sent as
Option | Description | Type | Default Value |
---|---|---|---|
types | Filter by invoice type | array | [‘I’,‘E’,‘P’,‘N’,‘T’] |
period.from | Filter by issuing date (greater than) | string | 2014-01-01 |
period.to | Filter by issuing date (less than) | string | now |
issued | Include invoices issued by the taxpayer | bool | true |
received | Include invoices received by the taxpayer | bool | true |
xml | Include the invoice CFDI XML file | bool | true |
Include the invoice CFDI PDF file | bool | true | |
complement | Filter by complement | int | -1 |
Option | Description | Type | Default Value |
---|---|---|---|
period.from | Filter by filing date (greater than) | string | 2014-01-01 |
period.to | Filter by filing date (less than) | string | now |
Option | Description | Type | Default Value |
---|---|---|---|
period.from | Filter by filing date (greater than) | string | 2014-01-01 |
period.to | Filter by filing date (less than) | string | now |
Option | Description | Type | Default Value |
---|---|---|---|
period.from | Filter by filing date (greater than) | string | 2014-01-01 |
period.to | Filter by filing date (less than) | string | now |
Option | Description | Type | Default Value |
---|---|---|---|
period.from | Filter by filing date (greater than) | string | 2014-01-01 |
period.to | Filter by filing date (less than) | string | now |
Option | Description | Type | Default Value |
---|---|---|---|
period.from | Filter by issuing date (greater than) | string | 2014-01-01 |
period.to | Filter by issuing date (less than) | string | now |
issued | Include tax retentions issued by the taxpayer | bool | true |
received | Include tax retentions received by the taxpayer | bool | true |
xml | Include the tax retention CFDI XML file | bool | true |
Include the tax retention CFDI PDF file | bool | true | |
complement | Filter by complement | int | -1 |
Option | Description | Type | Default Value |
---|---|---|---|
productType | The Buró de Crédito product type (e.g. INFORME_BURO, 007, RCO) | string | 007 (person / PDF), INFORME_BURO (company / PM) |
Status | Description |
---|---|
pending | The initial extraction status. The extraction is enqueued and waiting to be processed. |
waiting | The extraction does not meet the requirements to begin. |
running | The extraction process started and is currently running. The running time varies depending on the extractor type and the entity’s transactional volume. You may find partial data available in our API endpoints during this time. |
finished | The extraction finished successfully. All data is available to be retrieved from our API endpoints. |
failed | The extraction couldn’t start or failed during the process. Our internal retry policies weren’t able to finish the extraction successfully. We may have partial data available in our API endpoints, but new extractions should be created to ensure all the entity’s data is available. You can check the extraction error code to understand why it failed and determine whether it can be retried or not. |
stopping | The extraction was requested to be stopped by the user. It is in the process of being stopped. |
stopped | The extraction was stopped by the user after it started running. This extraction is included in billing. |
cancelled | The extraction was stopped by the user before it started running. This extraction is not included in billing. |
Code | Description | Retryable |
---|---|---|
invalid_credentials | The taxpayer Credential is no longer valid. | No |
login_failed | We couldn’t log in the taxpayer account. | Yes |
unrecoverable | The extraction process failed many times, and we reached a maximum number of retries. | Yes |
sat_unavailable | We detected that SAT itself is down or unresponsive. | Yes |
internal_error | We detected an internal error in our own infrastructure. | Yes |
undefined | We couldn’t determine the error cause and our internal team will investigate it. | Yes |