Argentina DNI Verification API: Name Lookup by Documento Nacional de Identidad

Updated November 2026

This guide shows how to verify a DNI in Argentina with Verifik’s API: the endpoint, its parameters, a request you can paste into a terminal, the documented response and errors, and what to watch for when you put it in production. Everything below comes from the official endpoint documentation.

About the DNI in Argentina

Argentina’s Documento Nacional de Identidad (DNI) is issued by RENAPER, the Registro Nacional de las Personas. The number has seven or eight digits and stays the same for life, so it is the key that ties together bank accounts, the CUIL/CUIT and most commercial contracts.

Verifik’s endpoint takes the document type DNIAR and the number and returns the registered name, already split into first name, last name and an array of name parts.

If the use case is clear, create an account and test the endpoint from your own code.

How to call the Argentina DNI API

Endpoint: GET https://api.verifik.co/v2/ar/cedula. Send your token in the Authorization: Bearer header. Parameters, as documented:

Request example with placeholder values (replace them with your user’s data):

curl --location --request GET 'https://api.verifik.co/v2/ar/cedula?documentType=DNIAR&documentNumber=12345678' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <token>'

200 response from the docs (personal data masked):

{
  "data": {
    "documentType": "DNIAR",
    "documentNumber": "12*****89",
    "fullName": "M**** V******",
    "firstName": "M****",
    "lastName": "V******",
    "arrayName": [
      "M****",
      "V******"
    ]
  },
  "signature": {
    "dateTime": "April 11, 2023 12:25 PM",
    "message": "Certified by Verifik.co"
  }
}

A successful call returns HTTP 200 with a data object containing: documentType, documentNumber, fullName, firstName, lastName, arrayName. Every response also carries a signature (timestamp and “Certified by Verifik.co”) and a unique id you can store as evidence of the check.

Documented errors for /v2/ar/cedula

• 404 NotFound (“Record not found”): no record was found; do not treat it as a match and route the case to review or ask for another document.
• 409 MissingParameter (“missing documentType missing documentNumber”): a required parameter is missing or has an invalid value; fix the request instead of retrying it as is.

Integration tips

• Strip dots before sending: users often type the DNI as 12.345.678, and the docs ask for the number without spaces.
• Use arrayName for fuzzy matching; it makes it easier to compare names when users omit a middle name.
• A 404 means no record was found. Ask the user to confirm the number before sending them to manual review.
• Personal data in Argentina is protected by Law 25.326; keep only the fields you need and document the purpose of the check.

Personal data and terms of use

Identity lookups process personal data. Use the API only for a lawful purpose you can document, such as onboarding, fraud prevention or contract checks, collect consent where the local law requires it, and keep only the fields you need. Usage is governed by the smartCHECK terms and conditions.

Pricing

Each successful request consumes credits from your Verifik plan. Current plans and per-endpoint costs are on the smartCHECK pricing page.

Related guides and documentation

• Argentina CUIT company lookup API
• Chile RUN verification API
• Endpoint documentation (English)
• Documentation in Spanish

Start testing

Create a Verifik account to get your API token, or book a meeting if you want to review coverage and volumes with the team.