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_passport" \
  -F "vendor_data=user-1234" \
  -F "consent=true" \
  -F "full_name=John Doe" \
  -F "date_of_birth=1990-01-01" \
  -F "passport_file_number=A12345678" \
  -F "passport_number=SAMPLE-PASS-12345"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "IND",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "ind_passport",
      "service_name": "India Passport",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "identification_number": "SAMPLE-ID-12345",
        "verifications": {
          "date_of_birth": true,
          "full_name": true,
          "identification_number": true
        }
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "full_match",
        "identification_number": "full_match"
      }
    }
  ]
}
Verifies input data against the database of passports issued by Passport Seva Kendra. 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: ~ 25%
  • Country: India
  • Service ID: ind_passport
  • Data domain: Document
  • Category: Passport

​
Inputs

FieldRequiredExample
full_nameYesJohn Doe
date_of_birthYes1990-01-01
passport_file_numberYesA12345678
passport_numberYesSAMPLE-PASS-12345
vendor_dataNouser-1234
  • Required inputs: full_name, date_of_birth, passport_file_number, passport_number
  • Optional inputs: vendor_data
  • Consent: Required
  • Workflow availability: Available in workflow
  • Coverage: ~ 25%
  • Price: $0.19 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_passport"
required
Array containing this service ID. Pinning the service keeps the request scoped to this exact database.Example: ind_passport
​
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
​
passport_file_number
string
default:"A12345678"
required
passport_file_number value required by this database service.Example: A12345678
​
passport_number
string
default:"SAMPLE-PASS-12345"
required
Passport number.Example: SAMPLE-PASS-12345
​
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

  • Send the fields listed above exactly as captured from the user or document.
  • Didit validates required fields before calling the database. Requests rejected before source lookup are not charged.

​
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_passport" \
  -F "vendor_data=user-1234" \
  -F "consent=true" \
  -F "full_name=John Doe" \
  -F "date_of_birth=1990-01-01" \
  -F "passport_file_number=A12345678" \
  -F "passport_number=SAMPLE-PASS-12345"

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_passport currently documents this normalized shape:
  • date_of_birth
  • identification_number

​
Pricing & SLAs

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