API Pull documentation · Updated 26 October 2026

CURP validator: format checks and registry verification

A CURP validator can check the shape of a code or query whether a record is found. These are different operations. A regular expression cannot establish that a person is registered, and a registry match alone does not establish ownership of an identity.

VerifyCurp documentation and Online TestAPI pricing and recharge options

Choose the check your integration needs

Use the VerifyCurp endpoint

The API Pull catalog exposes VerifyCurp as GET /curp/verify in the Mexican data hub. Its required query parameter is curp, a string containing the CURP to check. Authenticate using your own X-Api-Token. The example below follows the same gateway path used by Online Test.

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

Set both variables locally before running this example. Supply a CURP you are authorized to process. The example deliberately contains no real person's identifier or usable token.

Integrate in three steps

1. Read the endpoint's parameter and response documentation, sign in, and obtain your API token. Check the current unit price and account balance before submitting a request.
2. Validate obvious input mistakes locally. If your interface removes accidental surrounding spaces or normalizes case, make that behavior explicit. Do not replace the submitted identifier with masked display text.
3. Test an authorized record using Online Test. Handle transport status, the business result and missing fields separately, then map that result into your own review process.

Interpret the business response, not just HTTP 200

The current VerifyCurp description documents a successful result when the CURP is found with mensaje = "CURP encontrado" or when its status is RCN. Use the current endpoint response example for the field layout; do not assume every supplier returns the same JSON schema. An HTTP success alone is not proof of a matched record.

Keep malformed input, an empty or unmatched result, unavailable upstream service, invalid credentials and insufficient balance as separate outcomes. Do not label a timeout as an invalid CURP. Avoid automatic retries until you have checked the endpoint's retry and charging behavior.

Price per call and a small evaluation budget

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.

On 26 October 2026, the public catalog listed VerifyCurp at 0.05 USDT per call before discount and 0.04 USDT at the displayed 20% discount. This is a dated catalog reference, not a permanent price guarantee. The endpoint page shows the current price and billing rules, including how empty results and errors are treated.

Estimate usage as billable calls multiplied by the applicable unit price. For illustration, 100 billable calls at 0.04 USDT equal 4 USDT. A recharge amount is account funding; it is not a fixed number of calls across every API. Do not assume a free monthly allowance from this calculation.

Continue to the related workflow

Use QueryCurpBasicInfo when you need its documented basic fields, CurpToNss for the CURP-to-NSS workflow, or the CURP-to-RFC integration guide for the tax-identifier lookup. For Spanish documentation, open validación de CURP por API.