Honduras DNI Verification API: RNP Identity Number Name Lookup

Updated November 2026

This guide shows how to verify a DNI in Honduras 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 Honduras

Honduras’ Documento Nacional de Identificación (DNI) is issued by the Registro Nacional de las Personas (RNP). Its 13-digit number starts with the department and municipality codes of registration, followed by the holder’s year of birth and a sequence.

Verifik’s endpoint uses the document type DNIHN and returns the registered first name, last name and full name.

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

How to call the Honduras DNI API

Endpoint: GET https://api.verifik.co/v2/hn/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/hn/cedula?documentType=DNIHN&documentNumber=0801199012345' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <token>'

200 response from the docs (personal data masked):

{
  "data": {
    "documentType": "DNIHN",
    "documentNumber": "12*****89",
    "firstName": "J***",
    "lastName": "P****",
    "fullName": "J*** P****"
  },
  "signature": {
    "message": "Certified by Verifik.co",
    "dateTime": "January 16, 2024 3:44 PM"
  },
  "id": "HN001"
}

A successful call returns HTTP 200 with a data object containing: documentType, documentNumber, firstName, lastName, fullName. 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/hn/cedula

• 401 UNAUTHORIZED (“Authentication required”): the token is missing or invalid; check the Authorization header.
• 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.
• 500 InternalServerError (“Server error”): a server or source error; retry with backoff and log the request id.

Integration tips

• Remove the hyphens shown on the card (0801-1990-12345) before sending.
• documentType must be DNIHN.
• Missing parameters return 409 MissingParameter listing what is absent.
• For remittance and lending flows, compare fullName with the account holder and keep the signature as evidence.

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

• Guatemala CUI verification API
• El Salvador DUI 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.