Skip to main content
POST
Verifies an Argentine DNI and gender against the official RENAPER civil registry without a selfie, and returns the registered name, date of birth and tax id for comparison with the submitted data. No biometric: the person is confirmed by data alone. 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
  • 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. No face is compared: the registered identity is confirmed against the DNI, gender, name and date of birth you send.

​
Inputs

  • Required inputs: document_number, 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_data"
required
Array containing this service ID. Pinning the service keeps the request scoped to this exact database.Example: arg_renaper_data
​
string
default:"11111111"
required
Document number extracted from or provided by the user.Example: 11111111
​
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_data currently documents this normalized shape:
  • date_of_birth
  • first_name
  • full_name
  • gender_match
  • identification_number
  • last_name
  • nationality
  • tax_id
  • tax_id_type

​
Pricing & SLAs

Argentina - DNI data verification (RENAPER, no selfie) 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.

​
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/:
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