/sat/taxpayers

POST /api/sat/taxpayers

Price: 1 credit

Get a Mexican taxpayer's blacklist records by RFC

How to use it

Look up a Mexican taxpayer on the SAT blacklists by RFC (tax id) and return every matching record. Covers the Art. 69-B list of taxpayers with presumed nonexistent operations (EFOS/EDOS shell-company scheme, with the full cascade of situación — presunto, desvirtuado, definitivo, sentencia favorable — and the associated SAT and DOF official-letter numbers and publication dates) and the Art. 69 CFF lists of noncompliant taxpayers (firmes, cancelados, no localizados, condonados, exigibles, sentencias, retorno de inversiones, with situación, tipo de persona, entidad federativa, amount and publication date). Restrict to a single list with list_type, otherwise every list is searched.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• rfc string required — Taxpayer RFC (Mexican tax id) (examples: "AAA120730823", "AAA080808HL8"; minLength: 1)
• list_type string nullable — Restrict the lookup to a single blacklist (searches every list when omitted) (one of: "art_69b", "firmes", "cancelados", "no_localizados", "condonados", "exigibles", "sentencias", "retorno_inversiones")

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 — No SAT taxpayer record found for the given RFC 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.