Skip to main content
POST
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: 100%
  • Country: Argentina
  • Service ID: arg_renaper
  • Data domain: Identity
  • Category: NationalIDRegistry
RENAPER is the registry that issues every Argentine DNI, so every DNI number is on file, including the DNIs issued to foreign residents. The face match compares the selfie with the photo RENAPER holds for that DNI.

Inputs

  • Required inputs: document_number, selfie, gender
  • Optional inputs: first_name, last_name, date_of_birth, vendor_data
  • Consent: Not required
  • Workflow availability: Available in workflow
  • Coverage: 100%
  • Price: $0.20 per successful query

Body parameters

string
default:"ARG"
required
ISO 3166-1 alpha-3 country code for this database service.Example: ARG
string
default:"arg_renaper"
required
Array containing this service ID. Pinning the service keeps the request scoped to this exact database.Example: arg_renaper
string
default:"11111111"
required
Document number extracted from or provided by the user.Example: 11111111
file
required
Selfie image file to upload for biometric database validation. Accepted formats: JPEG, PNG, or WebP.Example: @./selfie.jpg
string
default:"M"
required
Gender value, when required by the database.Allowed values: M (male), F (female), X (other or unknown).Example: M
string
Given name to validate.Example: John
string
Family name to validate.Example: Doe
string
Date of birth in YYYY-MM-DD format.Example: 1990-01-01
string
default:"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

Input rules & validation notes

  • Argentine DNI (7-8 digits, optional M/F prefix)
  • document_number must be 7-9 characters long.
  • document_number must match [MFmf]?\d{7,8}.

How to call it

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:
  • date_of_birth
  • face_match_score
  • first_name
  • full_name
  • identification_number
  • last_name
  • 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.

Face match score

face_match_score is RENAPER’s similarity between the selfie and the photo on file for the DNI, sent as a whole number from 0 to 100 in a string, for example "92". It is not a probability between 0 and 1. The check returns BIOMETRIC_NO_MATCH when RENAPER reports that the face does not match, or when the score is below 50. At 50 or above the face is accepted, and the registered name and date of birth are then compared with the data you sent. The photo on file can be several years old, so a genuine user can score low after a large change in appearance. Consider sending BIOMETRIC_NO_MATCH to manual review rather than declining it outright, with the Partial Match / No Match actions.

When RENAPER does not answer

If RENAPER cannot be reached or answers with an error, the result is REGISTRY_UNAVAILABLE: nothing about the person was checked, and the call is not billed. The same request can succeed when you retry it later. See Outcome Codes for how to handle it.

Documents a workflow reads

Inside a workflow, the DNI number and gender come from the ID Verification step, which reads the Argentine DNI card and the digital DNI. Foreign residents hold the same DNI card and are verified the same way. The old booklet DNI (libreta) is not a supported ID Verification document, so a user who only holds one cannot complete that step. You can still check their DNI number directly with POST /v3/database-validation/.

Use it in a workflow

Add the service to a Database Validation step after ID Verification. For example, with POST /v3/workflows/:
With a Liveness step before it, RENAPER compares the live selfie. Without one, Didit sends the portrait printed on the ID document instead, which confirms the document photo but not that the person in front of the camera is its holder. A service ID the workflow cannot run is rejected with a 400 that names it, so the step is never saved without the check you asked for. See Workflow Feature Configs for every Database Validation setting.

Continue reading

Last modified on October 29, 2026