Base URL: https://rfccheck.com/v1. All endpoints are POST, accept JSON, and require the x-api-key header. Pick the one scoped to what you already know.
| Endpoint | Inputs | Latency | Cost | Webhook |
|---|---|---|---|---|
/rfc/validate |
rfc | 7–11 s | 10 credits | optional |
/rfc/profile |
rfc | 1–3 s | 3 credits | no |
/rfc/find-zip |
rfc, name | 7–9 s | 5 credits | optional |
/rfc/verify |
rfc, optionally name + zip | 1–2 s | 1 credit | no |
/rfc/sat-lists |
rfc | ~ms | Free under plans | no |
/rfc/verify-batch |
up to 5,000 records | 10–15 s | 1 × N credits | required |
/rfc/commerce-registry
Beta
|
rfc, optionally name | 20–60 s | 100 credits | optional |
/cfdi/verify |
uuid + rfc_emisor + rfc_receptor, or xml | ~3 s | 5 credits | no |
/csf/verify |
file, qr, or rfc + id_cif | ~2 s | 5 credits | no |
How to choose
- Know only the RFC? Use verify for a fast existence check (1–2 s, 1 credit), profile if you need the SAT-registered name, CURP, and contact email (1–3 s, 3 credits), or validate if you also want the zip and SAT lists (7–11 s, 10 credits).
- Know the RFC and the name? Use find-zip to recover the postal code (7–9 s, 5 credits), or pass name to validate to make it faster.
- Have RFC + name + zip already? Use verify (full mode) for a fast combo check, or verify-batch if you have many records.
- Vetting a company? Use commerce-registry for its Registro Público de Comercio records: legal regime, shareholders, and registered acts (20–60 s, 100 credits).
- Received a factura? Use cfdi/verify to ask SAT whether the CFDI is registered, still current, or cancelled (~3 s, 5 credits).
- Received a Constancia de Situación Fiscal? Use csf/verify to read its fiscal address, regimes, economic activities, and tax obligations, and have SAT confirm when it was issued and what is current (~2 s, 5 credits).