API Pull documentation · Updated 26 October 2026

SAT RFC API: look up an RFC from CURP

If you are looking for a SAT RFC API, first identify the operation you need. Looking up an RFC from a CURP is different from validating an existing RFC, retrieving a tax-status certificate or filing a tax return. API Pull's documented operation here is CurpToRfc.

CurpToRfc documentation and Online TestPer-call pricing and recharge options

What this endpoint supports

The Mexican data hub lists GET /torfc/query_by_curp, named CurpToRfc. It accepts the required curp query parameter and is described as converting the supplied CURP into its corresponding RFC. Check the actual response schema and available fields on the endpoint page before mapping them into your application.

Request example

Use your own API token and a CURP you are authorized to query. The gateway route below matches the route construction used by API Pull's Online Test. This is a command template; it does not contain a person's identifier or a working credential.

curl --get 'https://www.apipull.com/gateway/v1/mexican-scraper/torfc/query_by_curp' \
  --header "X-Api-Token: $APIPULL_API_TOKEN" \
  --data-urlencode "curp=$CURP"

Set APIPULL_API_TOKEN and CURP locally first. Never put the token in a public repository, shared screenshot or query string.

From documentation to a working integration

1. Open the endpoint documentation and verify the required input, current response example and billing conditions.
2. Check the CURP's expected structure before sending it. If you also need a registry-oriented CURP check, evaluate VerifyCurp separately; another call can have its own charge.
3. Sign in and run Online Test with authorized input. Keep the original input intact; a masked display value is not a valid API input.
4. Map the returned business result into your application. Keep successful lookup, no record, invalid credentials, insufficient balance and upstream failure distinguishable.

Price per call

Each account has 10 free Online Test calls per day, shared across all endpoints. The quota resets at 00:00 New York time (America/New_York), following daylight saving time automatically. This allowance is for Online Test; normal API requests follow the endpoint billing rules.

The catalog checked on 26 October 2026 listed CurpToRfc at 0.05 USDT per call before discount and 0.04 USDT after the displayed 20% discount. Prices and promotions can change. Use the endpoint's current price and billing notes before calling; this dated example is not a fixed quote.

At an illustrative effective price of 0.04 USDT, 1,000 billable lookups would cost 40 USDT. Add any other endpoint calls separately. The recharge packages fund a balance; they do not make every API share one unit price. USDT is the currently described online recharge method; this guide does not promise card payment, local bank settlement or tax invoices.

Handle results without overstating them

Do not equate HTTP 200 with a matched tax record. Parse the returned business fields described by the current endpoint contract. Treat an empty result as an outcome requiring explicit handling, not as evidence of fraud or proof that a person is unregistered. An unavailable upstream service should not silently become a negative identity decision.

For an onboarding workflow, document which fields you retain and how they are reviewed. Avoid logging raw identifiers and credentials. A lookup does not certify tax compliance, establish account ownership or replace checks required by your own organization.

Spanish documentation and related APIs

Read the documentación para consultar RFC con CURP or browse the Mexican API hub in Spanish. For a separate social-security lookup, see CurpToNss documentation. Each operation has its own input, output and billing rules.