Download PDF - Validation CURP
Description
API of JAAK for validation of CURP Mexico. The service valid format, structure and authenticity against the official database RENAPO from Mexico.
Structure of CURP
Unique identifier of the Mexican population 18 alphanumeric characters codifying:
- First name and vowels
- Date of birth (AAMMDD format)
- Gender and status code
- Internal consonants
- Test name
Example: GAMC850815HDFRRL09 = = Carlos García Martínez, born August 15, 1985 in Mexico City.
Endpoint
POST /api/v1/government/mx/curp/validate
Authentication: Bearer token required
Parameters
Leaders
Authorization(Bearer token, required)Content-Type(application / json, required)Request-Id(optional, auto- generated if omitted)
Body
| Field | Type | Required | Description |
|---|---|---|---|
curp | string | Yes | CURP 18 characters to be validated |
require_pdf | boolean | No | Requesting an official certificate from RENAPO |
Response
Successful responses include:
- Validation details (format, structure, check digit, business rules)
- Personal information from CURP
- Status of confirmation of RENAPO
- particulars of the birth report
- PDF download URL (expiry of 15 minutes if requested)
States CURP
| Code | Description |
|---|---|
| AN (Normal Assets) | Valid, active status |
| AB (Low Assets) | Active but marked for disposal |
| IN (Invalid) | Fitted |
| RE (rectified) | Corrected / amended |
Errors Management
| Error | HTTP code |
|---|---|
| Invalid format | 400 |
| Incorrect verification | 400 |
| Invalid dates | 400 |
| Required missing fields | 400 |
| Authentication challenges | 401 |
| Rate limitation exceeded | 429 |
| Server error | 500 |
Cases of Use
- Validation of user registration
- Compliance KYC with certificates downloads
- Validation in lots with detailed reports
- Obtaining and storing official PDF certificates
Best Practices
- Retitle inputs
- Implement robust bug management
- Using Request IDs unique for debugging
- Cackling valid CURPs to reduce calls to API