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 | ~30s | 10 credits | optional |
/rfc/profile |
rfc | ~1-3s | 3 credits | no |
/rfc/find-zip |
rfc, name | ~10-15s | 5 credits | optional |
/rfc/verify |
rfc, optionally name + zip | ~1-2s | 1 credit | no |
/rfc/sat-lists |
rfc | ~ms | Free under plans | no |
/rfc/verify-batch |
up to 5,000 records | ~10-15s | 1 × N credits | required |
How to choose
- Know only the RFC? Use verify for a fast existence check (~1-2s, 1 credit), profile if you need the SAT-registered name, CURP, and contact email (~1-3s, 3 credits), or validate if you also want the zip and SAT lists (~30s, 10 credits).
- Know the RFC and the name? Use find-zip to recover the postal code (~10-15s, 5 credits), or pass name to validate to halve its latency.
- Have RFC + name + zip already? Use verify (full mode) for a fast combo check, or verify-batch if you have many records.