Honduras - DNI verification - Didit Documentation

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=HND" \
  -F "services=hnd_dni" \
  -F "vendor_data=user-1234" \
  -F "document_number=1111111111111"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "HND",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "hnd_dni",
      "service_name": "Honduras - DNI verification",
      "source_data": {
        "document_type": "sample_value",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe"
      },
      "validation": {
        "identification_number": "full_match"
      }
    }
  ]
}

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "HND",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "hnd_dni",
      "service_name": "Honduras - DNI verification",
      "source_data": {
        "identification_number": "NO_MATCH"
      },
      "validation": {
        "identification_number": "no_match"
      }
    }
  ]
}

POST

database-validation

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=HND" \
  -F "services=hnd_dni" \
  -F "vendor_data=user-1234" \
  -F "document_number=1111111111111"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "HND",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "hnd_dni",
      "service_name": "Honduras - DNI verification",
      "source_data": {
        "document_type": "sample_value",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe"
      },
      "validation": {
        "identification_number": "full_match"
      }
    }
  ]
}

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "HND",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "hnd_dni",
      "service_name": "Honduras - DNI verification",
      "source_data": {
        "identification_number": "NO_MATCH"
      },
      "validation": {
        "identification_number": "no_match"
      }
    }
  ]
}

Verifies Honduran DNI data against CNE electoral registry records. 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: 90-95%
Country: Honduras
Service ID: hnd_dni
Data domain: Identity
Category: NationalIDRegistry

Inputs

Field	Required	Example
`document_number`	Yes	`1111111111111`
`first_name`	No	`John`
`last_name`	No	`Doe`
`vendor_data`	No	`user-1234`

Required inputs: document_number
Optional inputs: first_name, last_name, vendor_data
Consent: Not required
Workflow availability: Available in workflow
Coverage: 90-95%
Price: $0.20 per successful query

Body parameters

string

default:"HND"

required

ISO 3166-1 alpha-3 country code for this database service.Example: HND

string

default:"hnd_dni"

required

Array containing this service ID. Pinning the service keeps the request scoped to this exact database.Example: hnd_dni

string

default:"1111111111111"

required

Document number extracted from or provided by the user.Example: 1111111111111

string

default:"John"

Given name to validate.Example: John

string

default:"Doe"

Family name to validate.Example: Doe

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

Honduran DNI (exactly 13 digits)
document_number must contain digits only; remove spaces, hyphens, and punctuation before sending the request.
document_number must be exactly 13 characters long.

How to call it

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=HND" \
  -F "services=hnd_dni" \
  -F "vendor_data=user-1234" \
  -F "document_number=1111111111111"

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 can override it.

MATCH — The registry confirmed the identity and every checked field matched.

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "HND",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "hnd_dni",
      "service_name": "Honduras - DNI verification",
      "source_data": {
        "document_type": "sample_value",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe"
      },
      "validation": {
        "identification_number": "full_match"
      }
    }
  ]
}

NO_MATCH — The registry returned no match for the submitted data.

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "HND",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "hnd_dni",
      "service_name": "Honduras - DNI verification",
      "source_data": {
        "identification_number": "NO_MATCH"
      },
      "validation": {
        "identification_number": "no_match"
      }
    }
  ]
}

Returned data

The exact fields surfaced in source_data depend on what the registry returns. The generated example for hnd_dni currently documents this normalized shape:

document_type
first_name
full_name
identification_number
last_name

Pricing & SLAs

Honduras - DNI verification 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.

​Coverage

​Inputs

​Body parameters

​Input rules & validation notes

​How to call it

​Returned data

​Pricing & SLAs

​Continue reading

Coverage

Inputs

Body parameters

Input rules & validation notes

How to call it

Returned data

Pricing & SLAs

Continue reading