Returns combined INE (National Electoral Institute) and CURP (Unique Population Registry Code) validation results from Mexican government registries
When to use this endpoint
Use this endpoint to retrieve both INE and CURP validation results in a single API call for verification sessions that include Mexican registry checks.
This endpoint returns detailed information about:
- INE/IFE credential status and validity
- CURP registration status and person details
- Birth certificate evidence data
- Electoral registration information
Response data
- The response contains two main sections:
- INE data includes credential validity status, electoral information (voter key, federal district, OCR code), and validity period. The
activefield indicates if the credential is currently valid for voting. - CURP data includes person details (names, gender, birth date/region), CURP status code, and document evidence from birth certificate records (book, sheet, volume, act number).
- INE data includes credential validity status, electoral information (voter key, federal district, OCR code), and validity period. The
Implementation notes
- This endpoint requires the
versionquery parameter ifeIdentifierandineIdentifierboth represent person's identification number.ifeis a legacy name, it was changed toine.- This endpoint requires session-level HMAC signature authentication
- Data availability depends on integration configuration with Mexican registry providers
- Always ensure that you use the correct API URL to send requests. See the API URL section for more info.
- The order of parameters in the real API response can differ from the order you see in this documentation. This is expected and part of the Backwards compatible changes requirements.
Your integration's API key (occasionally referred to as the "Token", "API public key" or "Publishable key"). Required for all API requests.
You can find your API key in the Veriff Customer Portal > Settings > API keys.
Session id signed with the shared secret key. Required to authenticate the request sender.
Verification session ID.
Version parameter for registry validation
Combined INE and CURP registry validation results
{
"data": {
"ine": {
"active": true,
"status": "La credencial esta vigente",
"information": "CIC 000000000 Clave de elector JRLGLS00000000H000 Número de emisión 1 Distrito Federal 3 Distrito Local 4 Número OCR 0000000000000 Año de registro 2009 Año de emisión 2020 Fecha de actualización de la información: 10 de agosto del 2023 19:48 Fecha de consulta: 11 de agosto del 2023 Esta vigente como medio de identificación y puedes votar. Tus datos se encuentran en el Padrón Electoral, y también en la Lista Nominal de Electores. Será válida hasta el 31 de diciembre de 2030",
"comments": [
"Fecha de consulta: 11 de agosto del 2023",
"Tus datos se encuentran en el Padrón Electoral, y también en la Lista Nominal de Electores"
],
"ifeIdentifier": null,
"ineIdentifier": "000000000"
},
"curp": {
"curp": "ABCD000000HVZRGS00",
"names": "JUAN CARLOS",
"gender": "HOMBRE",
"regionCode": "VZ",
"statusCurp": "RCN",
"descriptionStatusCurp": "Registro de cambio no afectando a curp",
"birthRegion": "Veracruz",
"dateOfBirth": "1991-06-04T00:00:00Z",
"nationality": "MEX",
"firstSurname": "JUAREZ",
"secondSurname": "LAGUNES",
"docEvidenceData": {
"book": "5",
"sheet": "4",
"volume": "2",
"actNumber": "001234",
"registryCity": "VERACRUZ",
"regionRegistry": "30",
"registrationYear": "2009",
"registryCityCode": "4",
"registryRegionCode": "VZ"
},
"documentEvidence": 1
}
}
}Data related to the INE/IFE identification number and the CURP identification number.
Details about the INE/IFE identification number.
Indicates if the INE identification number is active (true) or inactive (false).
Explanation of the credential status in data.status field in Spanish.
Detailed information about the INE credential including CIC, voter key, emission number, federal/local district, OCR number, registration year, emission year, update date, query date, validity status, and expiration date.
Array of comments regarding the status of the identification.
IFE (Federal Electoral Institute) identification number. When this is returned, the ineIdentifier is not present.
INE (National Electoral Institute) identification number. When this is returned, the ifeIdentifier is not present.
Details about the CURP identification number.
CURP (Unique Population Registry Code) identification number - 18-character alphanumeric code.
Person's given name(s) as registered in CURP.
Person's gender (HOMBRE for male, MUJER for female).
Two-letter code for the birth region/state.
Status of the CURP registration.
Possible values:
- AN (Alta Normal - Normal registration)
- AH (Alta con Homonimia - Registration with homonymy)
- CRA CU (CURP Reactivada - Reactivated CURP)
- RCN (Registro de Cambio no Afectando a CURP - Change record not affecting CURP)
- RCC (Registro de Cambio Afectando a CURP - Change record affecting CURP)
- BD (Baja por Defunción - Cancelled due to death)
- BDA (Baja por Duplicidad - Cancelled due to duplication)
- BCC (Baja por Cambio en CURP - Cancelled due to CURP change)
- BCN (Baja no Afectando a CURP - Cancelled not affecting CURP)
Human-readable explanation of the statusCurp value in Spanish.
Name of the person's birth region/state.
Person's date of birth in DD/MM/YY format.
Person's nationality code.
Person's first surname (paternal surname).
Person's second surname (maternal surname).
Birth certificate evidence data from civil registry.
Birth certificate book number from civil registry.
Birth certificate sheet number within the book.
Birth certificate volume number.
Birth certificate act number (registration number).
City where the birth was registered.
Region code where the birth was registered.
Year when the birth was registered.
Numeric code for the registry city.
Two-letter code for the registry region/state.
Document evidence type indicator.
Bad request
Unauthorized
Session not found
Internal server error
Changelog
Date | Description |
|---|---|
Mar 9, 2026 | Documentation updated: parent categories rearranged, intro section expanded, request and response examples added |
Oct 2, 2025 |
|
Aug 6, 2025 | Response headers added |
Mar 12, 2025 | Documentation published |