> ## 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.

# Argentina - DNI verification (RENAPER)

> Verifies Argentine DNI against the official RENAPER civil registry, with biometric face-match against the photo on file. 100% population coverage. Authoritative real-time identity lookup for Argentina. Real-time lookup, pay-per-call.

<div hidden data-didit-db-validation-defaults="{&#x22;issuing_state&#x22;:&#x22;ARG&#x22;,&#x22;services&#x22;:&#x22;arg_renaper&#x22;,&#x22;document_number&#x22;:&#x22;1111111&#x22;,&#x22;gender&#x22;:&#x22;M&#x22;,&#x22;first_name&#x22;:&#x22;John&#x22;,&#x22;last_name&#x22;:&#x22;Doe&#x22;,&#x22;vendor_data&#x22;:&#x22;user-1234&#x22;}" />

Verifies Argentine DNI against the official RENAPER civil registry, with biometric face-match against the photo on file. 100% population coverage. 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:** Argentina
* **Service ID:** `arg_renaper`
* **Data domain:** Identity
* **Category:** NationalIDRegistry

## Inputs

| Field             | Required | Example         |
| ----------------- | -------: | --------------- |
| `document_number` |      Yes | `1111111`       |
| `selfie`          |      Yes | `@./selfie.jpg` |
| `gender`          |      Yes | `M`             |
| `first_name`      |       No | `John`          |
| `last_name`       |       No | `Doe`           |
| `vendor_data`     |       No | `user-1234`     |

* **Required inputs:** `document_number`, `selfie`, `gender`
* **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="ARG" placeholder="ARG">
  ISO 3166-1 alpha-3 country code for this database service.

  Example: `ARG`
</ParamField>

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

  Example: `arg_renaper`
</ParamField>

<ParamField body="document_number" type="string" required default="1111111" placeholder="1111111">
  Document number extracted from or provided by the user.

  Example: `1111111`
</ParamField>

<ParamField body="selfie" type="file" required placeholder="@./selfie.jpg">
  Selfie image file to upload for biometric database validation. Accepted formats: JPEG, PNG, or WebP.

  Example: `@./selfie.jpg`
</ParamField>

<ParamField body="gender" type="string" required default="M" placeholder="M" options="M,F,X">
  Gender value, when required by the database.

  Allowed values: `M` (male), `F` (female), `X` (other or unknown).

  Example: `M`
</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

* Argentine DNI (7-8 digits)
* `document_number` must contain digits only; remove spaces, hyphens, and punctuation before sending the request.
* `document_number` must be 7-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=ARG" \
    -F "services=arg_renaper" \
    -F "vendor_data=user-1234" \
    -F "document_number=1111111" \
    -F "selfie=@./selfie.jpg" \
    -F "gender=M"
  ```
</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": "ARG",
    "match_type": "full_match",
    "validations": [
      {
        "outcome_code": "MATCH",
        "service_id": "arg_renaper",
        "service_name": "Argentina - DNI verification (RENAPER)",
        "source_data": {
          "banks": "sample_value",
          "date_of_birth": "1990-01-01",
          "face_match_score": "0.990",
          "first_name": "John",
          "full_name": "John Doe",
          "highest_position": "sample_value",
          "identification_number": "SAMPLE-ID-12345",
          "last_name": "Doe",
          "last_position": "sample_value",
          "rejected_checks": "sample_value",
          "sit_1_since": "sample_value",
          "tax_id": "SAMPLE-12345",
          "tax_id_type": "SAMPLE-12345"
        },
        "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": "ARG",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "NO_MATCH",
        "service_id": "arg_renaper",
        "service_name": "Argentina - DNI verification (RENAPER)",
        "source_data": {
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```

  **`BIOMETRIC_NO_MATCH`** — The face-match score was below the acceptance threshold - the selfie is not the same person as the registry photo.

  ```json 200 OK — BIOMETRIC_NO_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "ARG",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "BIOMETRIC_NO_MATCH",
        "service_id": "arg_renaper",
        "service_name": "Argentina - DNI verification (RENAPER)",
        "source_data": {
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```

  **`BIOMETRIC_IMAGE_UNUSABLE`** — The selfie could not be processed (empty, no face, low quality, or the registry could not read it). Prompt the user to retake the selfie.

  ```json 200 OK — BIOMETRIC_IMAGE_UNUSABLE theme={null}
  {
    "request_id": "req_01H…",
    "status": "In Review",
    "issuing_state": "ARG",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "BIOMETRIC_IMAGE_UNUSABLE",
        "service_id": "arg_renaper",
        "service_name": "Argentina - DNI verification (RENAPER)",
        "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 `arg_renaper` currently documents this normalized shape:

* `banks`
* `date_of_birth`
* `face_match_score`
* `first_name`
* `full_name`
* `highest_position`
* `identification_number`
* `last_name`
* `last_position`
* `rejected_checks`
* `sit_1_since`
* `tax_id`
* `tax_id_type`

## Pricing & SLAs

Argentina - DNI verification (RENAPER) 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

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