This guide walks you from zero to your first validated RFC. New accounts get a $5 USD signup credit, so you can hit the API immediately.
1. Create an account
Sign up and confirm your email. Your $5 credit appears in your dashboard.
2. Generate an API key
From the dashboard, open API Keys and create a new key. Keys are shown once, so copy yours into your secret manager before leaving the page.
3. Make your first call
The verify endpoint is the cheapest call at 1 credit and the fastest to inspect. We'll use a known test RFC.
curl -X POST https://rfccheck.com/v1/rfc/verify \
-H "x-api-key: rfc_your_api_key" \
-H "Content-Type: application/json" \
-d '{"rfc": "XAXX010101000"}'
You should get back something like:
{
"rfc": "XAXX010101000",
"valid": true,
"message": "RFC válido, y susceptible de recibir facturas"
}
4. Pick the right endpoint
Each endpoint maps to a different question. The cheaper, scoped endpoints are faster, so use the smallest one that answers your question.
| If you want… | Use | Cost |
|---|---|---|
| "Is this RFC registered with SAT?" | /rfc/verify |
1 credit |
| "What is this RFC's name, CURP, and contact email?" | /rfc/profile |
3 credits |
| "What's the zip code for this RFC + name?" | /rfc/find-zip |
5 credits |
| "Give me everything you have on this RFC." | /rfc/validate |
10 credits |
| "Verify 5,000 records at once." | /rfc/verify-batch |
1 credit × N |
5. Handle errors
The API uses standard HTTP status codes. See Errors for the full list.