/sat/taxpayers/list

POST /api/sat/taxpayers/list

Price: 1 credit

List taxpayers from a Mexican SAT blacklist

How to use it

List taxpayers from a single Mexican SAT blacklist in published order. Choose the list with list_type: art_69b (presumed nonexistent operations — EFOS/EDOS) or one of the Art. 69 CFF lists (firmes, cancelados, no localizados, condonados, exigibles, sentencias, retorno de inversiones). Narrow with situación (art_69b only), tipo de persona (individual or legal entity) and entidad federativa. Each record includes situación, amounts, publication dates and — for Art. 69-B — the cascade of official-letter numbers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• list_type string required — Which blacklist to read (one of: "art_69b", "firmes", "cancelados", "no_localizados", "condonados", "exigibles", "sentencias", "retorno_inversiones")
• situacion string nullable — Filter Art. 69-B records by situación (only applies to the art_69b list) (one of: "presunto", "desvirtuado", "definitivo", "sentencia_favorable")
• supuesto string nullable — Filter Art. 69 records by supuesto (case-insensitive substring), e.g. the cancelados sub-types CANCELADOS or CANCELADOS POR INSOLVENCIA (examples: "CANCELADOS POR INSOLVENCIA")
• tipo_persona string nullable — Filter by taxpayer kind: F (individual) or M (legal entity) (one of: "F", "M")
• entidad string nullable — Filter by federal entity / state (case-insensitive substring) (examples: "JALISCO")
• count integer required — Max result count (examples: 20; min: 1)

Response

• @type string (default: "SatTaxpayer")
• rfc string required
• name string required
• list_type string required (one of: "art_69b", "firmes", "cancelados", "no_localizados", "condonados", "exigibles", "sentencias", "retorno_inversiones")
• situacion string nullable
• tipo_persona string nullable
• entidad string nullable
• monto string nullable
• publication_date string nullable
• amount_publication_date string nullable
• cancellation_date string nullable
• detail_69b object nullable
  • @type string (default: "SatTaxpayer69bDetail")
  • presuncion object nullable
    • @type string (default: "SatTaxpayer69bStage")
    • oficio_sat string nullable
    • fecha_sat string nullable
    • oficio_dof string nullable
    • fecha_dof string nullable
  • desvirtuaron object nullable
    • @type string (default: "SatTaxpayer69bStage")
    • oficio_sat string nullable
    • fecha_sat string nullable
    • oficio_dof string nullable
    • fecha_dof string nullable
  • definitivos object nullable
    • @type string (default: "SatTaxpayer69bStage")
    • oficio_sat string nullable
    • fecha_sat string nullable
    • oficio_dof string nullable
    • fecha_dof string nullable
  • sentencia_favorable object nullable
    • @type string (default: "SatTaxpayer69bStage")
    • oficio_sat string nullable
    • fecha_sat string nullable
    • oficio_dof string nullable
    • fecha_dof string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.