RENAPO

Retrieve CURP via Demographics

Credits: 2 per call.

Reconstructs a CURP from the four official input fields: given names, first surname, second surname, gender, date of birth, and birth state code. Calls RENAPO and returns the matching CURP plus the full personal record (same shape as validateCurp).

Use this endpoint when your KYC form collects names and date of birth but not the CURP, and you need the CURP to file a financial product or report to regulators. The lookup uses RENAPO’s strict matching — if any field is misspelled, no match is returned (CURP_NOT_FOUND).

cURL

curl -X POST https://api.origoid.com/mex/renapo/v1/curp-lookups \
  -H "x-api-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{"givenNames": "JUAN", "firstSurname": "PEREZ", "secondSurname": "LOPEZ", "dateOfBirth": "1990-01-01", "gender": "H", "birthStateCode": "DF", "generateRfc": true}'

{
  "status": "OK",
  "type": "SUCCESS",
  "message": "CURP found and validated",
  "data": {
    "personalInfo": {
      "curp": "TEST900101HDFRRN09",
      "givenNames": "JUAN",
      "firstSurname": "PEREZ",
      "secondSurname": "LOPEZ",
      "gender": "H",
      "dateOfBirth": "1990-01-01",
      "birthState": "DISTRITO FEDERAL",
      "birthStateCode": "DF",
      "nationality": "MEXICO"
    },
    "documentDetails": {
      "curpStatus": "AN",
      "probatoryDocumentCode": 1
    },
    "registrationDetails": {
      "state": "DISTRITO FEDERAL",
      "stateCode": "09",
      "municipality": "CUAUHTEMOC",
      "municipalityCode": "015",
      "year": "1990",
      "foreignNumber": ""
    }
  },
  "transactionId": "550e8400-e29b-41d4-a716-446655440020",
  "processedAt": "2026-03-15T12:35:00-06:00",
  "billable": true
}

Authorizations

x-api-key

string

header

required

Body

application/json

givenNames

string

required

Example:

"JUAN"

firstSurname

string

required

Example:

"PEREZ"

dateOfBirth

string

required

Format YYYY-MM-DD

Example:

"1990-01-01"

gender

enum<string>

required

Available options:

H,

M,

X

Example:

"H"

birthStateCode

string

required

Example:

"DF"

secondSurname

string

Example:

"LOPEZ"

generateRfc

boolean

Example:

true

Response

Business Responses (Strict Envelope Pattern).

status

enum<string>

required

High-level outcome. OK means the request was successfully processed (regardless of business result). ERROR means the request was rejected or could not be processed.

Available options:

OK,

ERROR

type

string

required

Stable result type code. Includes generic codes (SUCCESS, INVALID_REQUEST, UNAUTHORIZED, SERVICE_UNAVAILABLE, INTERNAL_ERROR, RATE_LIMIT_EXCEEDED) plus endpoint-specific result codes — see this endpoint's response examples.

message

string

required

Human-readable summary of the result. Always in English (per Language Conventions in the API overview).

transactionId

string<uuid>

required

Unique identifier of this request, generated by the API Gateway. Propagated end-to-end for traceability.

processedAt

string<date-time>

required

ISO 8601 datetime with Mexico City offset (-06:00). Always set by the API Gateway when the response leaves the system.

billable

boolean

required

Whether this request will be charged against the client's plan. Typically true for successful business results and false for validation errors or system errors that prevented processing.

data

object

Response payload. null on error responses. Shape depends on the endpoint — see each operation's response schema.

errors

object[]

Per-field error details. Present only on INVALID_REQUEST responses.

Show child attributes

CURP Official Document (PDF)**Credits:** 2 per call. Retrieves the official RENAPO CURP document ("Constancia de la CURP") as a PDF, together with the full validated record and the CURP's RENAPO status — the **same status matrix as `curp-validations`** (active, homonymy, deceased, apocryphal, judicial suspension, inactive). Use it when you need the citizen's official, printable certificate, not just the validated data. The PDF is returned **inline as base64** in `data.document.content`, alongside the parsed identity fields. This is a **synchronous** call. Optionally pass `generateRfc: true` to also receive the deterministic `personalInfo.rfc` (computed from the CURP, no SAT call) — identical to `curp-validations`. **Why it differs from `curp-validations`:** this endpoint retrieves the actual document from RENAPO, so a response takes a little longer to return. It is priced at **2 credits** and has a lower rate limit than the high-volume `curp-validations`.

cURL

curl -X POST https://api.origoid.com/mex/renapo/v1/curp-lookups \
  -H "x-api-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{"givenNames": "JUAN", "firstSurname": "PEREZ", "secondSurname": "LOPEZ", "dateOfBirth": "1990-01-01", "gender": "H", "birthStateCode": "DF", "generateRfc": true}'

{
  "status": "OK",
  "type": "SUCCESS",
  "message": "CURP found and validated",
  "data": {
    "personalInfo": {
      "curp": "TEST900101HDFRRN09",
      "givenNames": "JUAN",
      "firstSurname": "PEREZ",
      "secondSurname": "LOPEZ",
      "gender": "H",
      "dateOfBirth": "1990-01-01",
      "birthState": "DISTRITO FEDERAL",
      "birthStateCode": "DF",
      "nationality": "MEXICO"
    },
    "documentDetails": {
      "curpStatus": "AN",
      "probatoryDocumentCode": 1
    },
    "registrationDetails": {
      "state": "DISTRITO FEDERAL",
      "stateCode": "09",
      "municipality": "CUAUHTEMOC",
      "municipalityCode": "015",
      "year": "1990",
      "foreignNumber": ""
    }
  },
  "transactionId": "550e8400-e29b-41d4-a716-446655440020",
  "processedAt": "2026-03-15T12:35:00-06:00",
  "billable": true
}