CURP results (legacy)

  • Updated on Mar 9, 2026
  • Published on Jan 30, 2025
Prev Next
Get
/v1/sessions/{id}/decision/curp-registry

Returns the check result with CURP identification number and status

  • The CURP (Clave Única de Registro de Población - Unique Key of Population Registry) is the Mexican national identification number
  • This endpoint returns the validation result from querying the CURP database with the person data provided during session creation

When to use this endpoint

  • Use this endpoint to retrieve CURP database validation results for Mexican identity verification sessions

  • Common use cases include:

    • Verifying the status of a CURP identification number (active, inactive, changed)
    • Confirming CURP registry data matches the provided person information
    • Checking registration status changes or cancellations

Response data

  • The response includes:

    • statusCurp: Status code indicating the CURP registration state (active, inactive, changed)
    • curp: The 18-character CURP identification number

  • Active CURP status codes:

    • 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 registered without affecting CURP
    • RCC (Registro de Cambio Afectando a CURP) - Change registered affecting CURP

  • Inactive CURP status codes:

    • BD (Baja por Defuncion) - 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 without affecting CURP

Implementation notes

  • The version query parameter is required for API versioning
  • The statusCurp field may be null if the check could not be completed or no data was found
  • This endpoint requires session-level HMAC signature authentication
  • 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.
Header parameters
x-auth-client
stringRequired

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.

Exampleyour-api-key
x-hmac-signature
stringRequired

Session id signed with the shared secret key. Required to authenticate the request sender.

Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
Path parameters
id
string (uuid) Required

Verification session ID.

Examplef04bdb47-d3be-4b28-b028-a652feb060b5
Query parameters
version
stringRequired

API version parameter

Examplev1
Responses
200

Result of the CURP registry check

Headers
Content-Type
string
Response content type.
Exampleapplication/json
x-auth-client
string
API key echoed back in response.
Exampleyour-api-key
x-hmac-signature
string
Response body signed with the shared secret key. Required to authenticate the response sender.
Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
active_curp_normal_registration

CURP is active with normal registration status (AN)

{
  "statusCurp": "AN",
  "curp": "FOHJ920625HGTLRR06"
}
active_curp_change_not_affecting

CURP is active with a change registered that did not affect the CURP number (RCN)

{
  "statusCurp": "RCN",
  "curp": "GOMZ890415MDFNTR03"
}
inactive_curp_deceased

CURP has been cancelled because the person is deceased (BD)

{
  "statusCurp": "BD",
  "curp": "SAMP560712HDFRLN08"
}
inactive_curp_duplicate

CURP has been cancelled because it was a duplicate registration (BDA)

{
  "statusCurp": "BDA",
  "curp": "RIVE830923MMCRRS04"
}
no_data_found

No data found

The CURP check was completed but no data was found in the registry

{
  "statusCurp": null,
  "curp": "ABCD000000HVZRGS00"
}
object

Response containing CURP registry validation results.

statusCurp
string | null

Status of the CURP data in the registry.

Returns null if the check could not be completed or no data was found.

Valid values[ "AN", "AH", "CRA CU", "RCN", "RCC", "BD", "BDA", "BCC", "BCN" ]
ExampleRCN
curp
string

18-character alphanumeric code of the person (the CURP identification number).

ExampleFOHJ920625HGTLRR06
400

Bad request

Headers
Content-Type
string
Response content type.
Exampleapplication/json
x-auth-client
string
API key echoed back in response.
Exampleyour-api-key
x-hmac-signature
string
Response body signed with the shared secret key. Required to authenticate the response sender.
Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
object
status
string
Valid values[ "fail" ]
Examplefail
code
string
Example1101
message
string
ExampleValidation failed
401

Unauthorized

Headers
Content-Type
string
Response content type.
Exampleapplication/json
x-auth-client
string
API key echoed back in response.
Exampleyour-api-key
object
status
string
Valid values[ "fail" ]
Examplefail
code
string
Example1101
message
string
ExampleMandatory X-AUTH-CLIENT header containing the API key is missing from the request.
404

Session not found

Headers
Content-Type
string
Response content type.
Exampleapplication/json
x-auth-client
string
API key echoed back in response.
Exampleyour-api-key
x-hmac-signature
string
Response body signed with the shared secret key. Required to authenticate the response sender.
Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
object
status
string
Valid values[ "fail" ]
Examplefail
code
string
Example1101
message
string
ExampleResource not found
500

Internal server error

Headers
Content-Type
string
Response content type.
Exampleapplication/json
x-auth-client
string
API key echoed back in response.
Exampleyour-api-key
x-hmac-signature
string
Response body signed with the shared secret key. Required to authenticate the response sender.
Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
object
status
string
Valid values[ "fail" ]
Examplefail
code
string
Example1101
message
string
ExampleSomething went wrong



Document Versioning

Changelog

Date

Description

Mar 9, 2026

Documentation updated: parent categories rearranged, intro section expanded, request and response examples added

Oct 2, 2025

vrf- headers removed from response headers

Aug 6, 2025

Response headers added

Mar 12, 2025

Documentation published