Skip to main content
POST
/
v3
/
database-validation
/
curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=IND" \
  -F "services=ind_aadhaar" \
  -F "vendor_data=user-1234" \
  -F "consent=true" \
  -F "full_name=John Doe" \
  -F "date_of_birth=1990-01-01" \
  -F "personal_number=111111111111" \
  -F "pan=ABCDE1234F"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "IND",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "ind_aadhaar",
      "service_name": "India Aadhaar (UIDAI)",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345"
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "full_match",
        "identification_number": "full_match"
      }
    }
  ]
}
Verifies the input Aadhaar number against UIDAI identity 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: ~ 100%
  • Country: India
  • Service ID: ind_aadhaar
  • Data domain: Identity
  • Category: NationalIDRegistry

​
Inputs

FieldRequiredExample
full_nameYesJohn Doe
date_of_birthYes1990-01-01
personal_numberYes111111111111
panYesABCDE1234F
vendor_dataNouser-1234
  • Required inputs: full_name, date_of_birth, personal_number, pan
  • Optional inputs: vendor_data
  • Consent: Required
  • Workflow availability: Available in workflow
  • Coverage: ~ 100%
  • Price: $0.11 per successful query

​
Body parameters

​
issuing_state
string
default:"IND"
required
ISO 3166-1 alpha-3 country code for this database service.Example: IND
​
services
string
default:"ind_aadhaar"
required
Array containing this service ID. Pinning the service keeps the request scoped to this exact database.Example: ind_aadhaar
​
consent
boolean
default:"true"
required
Explicit end-user consent for this service.Example: true
​
full_name
string
default:"John Doe"
required
Full legal name to validate.Example: John Doe
​
date_of_birth
string
default:"1990-01-01"
required
Date of birth in YYYY-MM-DD format.Example: 1990-01-01
​
personal_number
string
default:"111111111111"
required
Country-specific personal identity number.Example: 111111111111
​
pan
string
default:"ABCDE1234F"
required
Permanent Account Number.Example: ABCDE1234F
​
vendor_data
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

  • pan must use uppercase letters.
  • pan must match [A-Z]{5}\d{4}[A-Z].
  • personal_number must contain digits only; remove spaces, hyphens, and punctuation before sending the request.
  • personal_number must be exactly 12 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=IND" \
  -F "services=ind_aadhaar" \
  -F "vendor_data=user-1234" \
  -F "consent=true" \
  -F "full_name=John Doe" \
  -F "date_of_birth=1990-01-01" \
  -F "personal_number=111111111111" \
  -F "pan=ABCDE1234F"

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.

​
Returned data

The exact fields surfaced in source_data depend on what the registry returns. The generated example for ind_aadhaar currently documents this normalized shape:
  • date_of_birth
  • full_name
  • identification_number

​
Pricing & SLAs

India Aadhaar (UIDAI) queries are billed only when Didit receives a conclusive result from the validation source.
  • Per-call price: $0.11 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.

​
Continue reading