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

# Peru - DNI verification

> Verifies Peruvian DNI against the RENIEC civil registry. Authoritative real-time identity lookup for Peru. Real-time lookup, pay-per-call.

<div hidden data-didit-db-validation-defaults="{&#x22;issuing_state&#x22;:&#x22;PER&#x22;,&#x22;services&#x22;:&#x22;per_dni&#x22;,&#x22;personal_number&#x22;:&#x22;11111111&#x22;,&#x22;first_name&#x22;:&#x22;John&#x22;,&#x22;last_name&#x22;:&#x22;Doe&#x22;,&#x22;vendor_data&#x22;:&#x22;user-1234&#x22;}" />

Verifies Peruvian DNI against the RENIEC civil registry. Didit exposes this service through `POST /v3/database-validation/` so you can verify the submitted data against the authoritative source and receive normalized match results.

## Coverage

* **Coverage:** —
* **Country:** Peru
* **Service ID:** `per_dni`
* **Data domain:** Identity
* **Category:** NationalIDRegistry

## Inputs

| Field             | Required | Example     |
| ----------------- | -------: | ----------- |
| `personal_number` |      Yes | `11111111`  |
| `first_name`      |       No | `John`      |
| `last_name`       |       No | `Doe`       |
| `vendor_data`     |       No | `user-1234` |

* **Required inputs:** `personal_number`
* **Optional inputs:** `first_name`, `last_name`, `vendor_data`
* **Consent:** Not required
* **Workflow availability:** Available in workflow
* **Coverage:** —
* **Price:** \$0.20 per successful query

## Body parameters

<ParamField body="issuing_state" type="string" required default="PER" placeholder="PER">
  ISO 3166-1 alpha-3 country code for this database service.

  Example: `PER`
</ParamField>

<ParamField body="services" type="string" required default="per_dni" placeholder="per_dni">
  Array containing this service ID. Pinning the service keeps the request scoped to this exact database.

  Example: `per_dni`
</ParamField>

<ParamField body="personal_number" type="string" required default="11111111" placeholder="11111111">
  Country-specific personal identity number.

  Example: `11111111`
</ParamField>

<ParamField body="first_name" type="string" default="John" placeholder="John">
  Given name to validate.

  Example: `John`
</ParamField>

<ParamField body="last_name" type="string" default="Doe" placeholder="Doe">
  Family name to validate.

  Example: `Doe`
</ParamField>

<ParamField body="vendor_data" type="string" default="user-1234" placeholder="user-1234">
  Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise.

  Example: `user-1234`
</ParamField>

## Input rules & validation notes

* Peruvian DNI (exactly 8 digits)
* `personal_number` must contain digits only; remove spaces, hyphens, and punctuation before sending the request.
* `personal_number` must be exactly 8 characters long.

## How to call it

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://verification.didit.me/v3/database-validation/" \
    -H "x-api-key: YOUR_API_KEY" \
    -F "issuing_state=PER" \
    -F "services=per_dni" \
    -F "vendor_data=user-1234" \
    -F "personal_number=11111111"
  ```
</RequestExample>

<ResponseExample>
  Every successful call returns HTTP `200`. The **`outcome_code`** field tells you what actually happened — distinguishing, for example, a real biometric mismatch (`BIOMETRIC_NO_MATCH`) from a selfie that could not be read (`BIOMETRIC_IMAGE_UNUSABLE`). The `status` shown is the default feature status; your configured [Partial Match / No Match actions](/core-technology/database-validation/database-validation-warnings) can override it.

  **`MATCH`** — The registry confirmed the identity and every checked field matched.

  ```json 200 OK — MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Approved",
    "issuing_state": "PER",
    "match_type": "full_match",
    "validations": [
      {
        "outcome_code": "MATCH",
        "service_id": "per_dni",
        "service_name": "Peru - DNI verification",
        "source_data": {
          "first_name": "John",
          "identification_number": "SAMPLE-ID-12345",
          "last_name": "Doe",
          "maternal_name": "Doe Maternal",
          "paternal_name": "Doe Paternal",
          "verification_letter": "G",
          "verification_number": 2
        },
        "validation": {
          "identification_number": "full_match"
        }
      }
    ]
  }
  ```

  **`NO_MATCH`** — The registry returned no match for the submitted data.

  ```json 200 OK — NO_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "PER",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "NO_MATCH",
        "service_id": "per_dni",
        "service_name": "Peru - DNI verification",
        "source_data": {
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```

  **`DOCUMENT_NOT_FOUND`** — The submitted document number does not correspond to any record in the registry.

  ```json 200 OK — DOCUMENT_NOT_FOUND theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "PER",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "DOCUMENT_NOT_FOUND",
        "service_id": "per_dni",
        "service_name": "Peru - DNI verification",
        "source_data": {
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```
</ResponseExample>

## Returned data

The exact fields surfaced in `source_data` depend on what the registry returns. The generated example for `per_dni` currently documents this normalized shape:

* `first_name`
* `identification_number`
* `last_name`
* `maternal_name`
* `paternal_name`
* `verification_letter`
* `verification_number`

## Pricing & SLAs

Peru - DNI verification queries are billed only when Didit receives a conclusive result from the validation source.

* **Per-call price:** \$0.20 USD.
* **Billing:** per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source.
* **Latency:** typical p95 \< 2 s.
* **Availability:** 99.9% per quarter on Didit's side; downstream source availability varies by country and dataset.

## Continue reading

* [Peru Database Validation overview](/api-reference/database-validation/peru)
* [Database Validation overview](/core-technology/database-validation/overview)
* [Outcome Codes](/core-technology/database-validation/database-validation-outcome-codes)