---
title: "CURP results (legacy)"
slug: "v1sessionsiddecisioncurp-registry-1"
updated: 2026-04-24T06:53:05Z
published: 2026-04-24T06:53:05Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.veriff.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CURP results (legacy)

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](https://devdocs.veriff.com/docs/hmac-authentication-and-endpoint-security#public-api-v1) authentication
- Always ensure that you use the correct API URL to send requests. See the [API URL section](https://devdocs.veriff.com/apidocs/veriff-public-api-guides#api-url) 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](https://devdocs.veriff.com/apidocs/veriff-public-api-guides#backwards-compatible-changes) requirements.

Header parametersX-AUTH-CLIENTstringRequired

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-SIGNATUREstringRequired

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

Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8

Path parametersidstring (uuid) Required

Verification session ID.

Examplef04bdb47-d3be-4b28-b028-a652feb060b5

Query parametersversionstringRequired

API version parameter

Examplev1

Responses200

Result of the CURP registry check

HeadersContent-TypestringResponse content type.Exampleapplication/json
X-AUTH-CLIENTstringAPI key echoed back in response.Exampleyour-api-key
X-HMAC-SIGNATUREstringResponse body signed with the shared secret key. Required to authenticate the response sender.Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
<select class='api-response-data' aria-label='Media type'><option value='306485b8-33ce-4454-9b6d-82a398188b25'>application/json</option>
</select><select class='select-example' aria-label='Media type'><option value='c3386143-6f2e-4d59-87f8-dbfe0204f356'>active_curp_normal_registration</option>
<option value='59fcefd9-f069-4f3f-8cf3-5cffe2bdcd80'>active_curp_change_not_affecting</option>
<option value='1ce687df-3422-403a-9989-08f76daf01c1'>inactive_curp_deceased</option>
<option value='e4b01c65-1ee7-45c9-a811-badfbcf48c60'>inactive_curp_duplicate</option>
<option value='c690c7ab-469c-49ac-902c-8dfff99174c0'>no_data_found</option>
</select>active_curp_normal_registration

CURP is active with normal registration status (AN)

```json
{
  "statusCurp": "AN",
  "curp": "FOHJ920625HGTLRR06"
}
```

active_curp_change_not_affecting

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

```json
{
  "statusCurp": "RCN",
  "curp": "GOMZ890415MDFNTR03"
}
```

inactive_curp_deceased

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

```json
{
  "statusCurp": "BD",
  "curp": "SAMP560712HDFRLN08"
}
```

inactive_curp_duplicate

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

```json
{
  "statusCurp": "BDA",
  "curp": "RIVE830923MMCRRS04"
}
```

no_data_found

No data found

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

```json
{
  "statusCurp": null,
  "curp": "ABCD000000HVZRGS00"
}
```

object  

Response containing CURP registry validation results.

statusCurpstring   | 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
curpstring    

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

ExampleFOHJ920625HGTLRR06

400

Bad request

HeadersContent-TypestringResponse content type.Exampleapplication/json
X-AUTH-CLIENTstringAPI key echoed back in response.Exampleyour-api-key
X-HMAC-SIGNATUREstringResponse body signed with the shared secret key. Required to authenticate the response sender.Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
<select class='api-response-data' aria-label='Media type'><option value='0c029aed-6eaa-4b55-abc8-0a5101f5bf7c'>application/json</option>
</select>object  statusstring    Valid values[
  "fail"
]Examplefail
codestring    Example1101
messagestring    ExampleValidation failed

401

Unauthorized

HeadersContent-TypestringResponse content type.Exampleapplication/json
X-AUTH-CLIENTstringAPI key echoed back in response.Exampleyour-api-key
<select class='api-response-data' aria-label='Media type'><option value='7bd7ac3b-9cc2-4f45-92a7-f36f72bd32ad'>application/json</option>
</select>object  statusstring    Valid values[
  "fail"
]Examplefail
codestring    Example1101
messagestring    ExampleMandatory X-AUTH-CLIENT header containing the API key is missing from the request.

404

Session not found

HeadersContent-TypestringResponse content type.Exampleapplication/json
X-AUTH-CLIENTstringAPI key echoed back in response.Exampleyour-api-key
X-HMAC-SIGNATUREstringResponse body signed with the shared secret key. Required to authenticate the response sender.Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
<select class='api-response-data' aria-label='Media type'><option value='3959aeb2-ea3f-4095-94b1-e312751eb0da'>application/json</option>
</select>object  statusstring    Valid values[
  "fail"
]Examplefail
codestring    Example1101
messagestring    ExampleResource not found

500

Internal server error

HeadersContent-TypestringResponse content type.Exampleapplication/json
X-AUTH-CLIENTstringAPI key echoed back in response.Exampleyour-api-key
X-HMAC-SIGNATUREstringResponse body signed with the shared secret key. Required to authenticate the response sender.Example4a7f6b8c9d2e3f1a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8
<select class='api-response-data' aria-label='Media type'><option value='dcee3825-e349-41cf-85e1-1721ac5ea486'>application/json</option>
</select>object  statusstring    Valid values[
  "fail"
]Examplefail
codestring    Example1101
messagestring    ExampleSomething went wrong

		
			

<title style="font-size:15px;">Document Versioning</title>

**Changelog**

| Date | Description |
| --- | --- |
| Apr 24, 2026 | Headers capitalization harmonized |
| Apr 17, 2026 | Typo fixed |
| 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 |