Skip to main content
POST
Verifies Mexican CURP against the RENAPO national identifier registry. Didit exposes this service through POST /v3/database-validation/ so you can verify the submitted data against the authoritative source and receive normalized match results.

Coverage

  • Coverage: ~ 100%
  • Country: Mexico
  • Service ID: mex_curp
  • Data domain: Identity
  • Category: NationalIDRegistry

Inputs

  • Required inputs: personal_number
  • Optional inputs: first_name, last_name, vendor_data
  • Consent: Not required
  • Workflow availability: Available in workflow
  • Coverage: ~ 100%
  • Price: $0.20 per successful query

Body parameters

string
default:"MEX"
required
ISO 3166-1 alpha-3 country code for this database service.Example: MEX
string
default:"mex_curp"
required
Array containing this service ID. Pinning the service keeps the request scoped to this exact database.Example: mex_curp
string
default:"ABCD900101HDFABC09"
required
Country-specific personal identity number.Example: ABCD900101HDFABC09
string
default:"John"
Given name to validate.Example: John
string
default:"Doe"
Family name to validate.Example: Doe
string
default:"user-1234"
Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise.Example: user-1234

Input rules & validation notes

  • Mexican CURP (exactly 18 alphanumeric characters)
  • personal_number must be exactly 18 characters long.

How to call it

Returned data

The exact fields surfaced in source_data depend on what the registry returns. The generated example for mex_curp currently documents this normalized shape:
  • curp_status
  • date_of_birth
  • doc_probatorio
  • first_name
  • full_name
  • gender
  • identification_number
  • last_name
  • nationality
  • num_acta
  • registration_municipality
  • registration_state
  • registration_year
  • state_of_birth

Pricing & SLAs

Mexico - CURP verification queries are billed only when Didit receives a conclusive result from the validation source.
  • Per-call price: $0.20 USD.
  • Billing: per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source.
  • Latency: typical p95 < 2 s.
  • Availability: 99.9% per quarter on Didit’s side; downstream source availability varies by country and dataset.

Continue reading