Skip to main content
cURL
curl -X POST https://api.origoid.com/mex/renapo/v1/curp-documents \
  -H "x-api-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{"curp": "TEST900101HDFRRN09"}'
{
  "status": "OK",
  "type": "SUCCESS",
  "message": "CURP document retrieved",
  "data": {
    "personalInfo": {
      "curp": "TEST900101HDFRRN09",
      "rfc": "TEST900101XXX",
      "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": ""
    },
    "files": [
      {
        "kind": "document",
        "contentType": "application/pdf",
        "sizeBytes": 48213,
        "content": "JVBERi0xLjQKJeLjz9MKMyAwIG9iago8PC9...TRUNCATED_BASE64..."
      }
    ]
  },
  "transactionId": "a1b2c3d4-e5f6-7a8b-9c0d-111111111111",
  "processedAt": "2026-06-01T10:00:00-06:00",
  "billable": true
}

Authorizations

​
x-api-key
string
header
required

Body

application/json
​
curp
string
required

The 18-character CURP whose official document is requested.

Example:

"TEST900101HDFRRN09"

​
generateRfc
boolean

Generate the RFC associated with the CURP. Deterministic from the CURP (no SAT call). When true, personalInfo.rfc is included — same as curp-validations.

Example:

true

Response

CURP document result (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.