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=GLB" \
  -F "services=glb_intelligence_service" \
  -F "vendor_data=user-1234" \
  -F "phone=+15550101000"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "GLB",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "glb_intelligence_service",
      "service_name": "Global - Core Intelligence Service",
      "source_data": {},
      "validation": {
        "identification_number": "full_match"
      }
    }
  ]
}
Performs a series of checks across multiple data partners and returns risks associated with each data point. 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: —
  • Country: Global
  • Service ID: glb_intelligence_service
  • Data domain: Telecom
  • Category: Telecom

​
Inputs

FieldRequiredExample
phoneYes+15550101000
vendor_dataNouser-1234
  • Required inputs: phone
  • Optional inputs: vendor_data
  • Consent: Not required
  • Workflow availability: Standalone API only
  • Coverage: —
  • Price: $0.41 per successful query

​
Body parameters

​
issuing_state
string
default:"GLB"
required
ISO 3166-1 alpha-3 country code for this database service.Example: GLB
​
services
string
default:"glb_intelligence_service"
required
Array containing this service ID. Pinning the service keeps the request scoped to this exact database.Example: glb_intelligence_service
​
phone
string
default:"+15550101000"
required
Phone number in international format.Example: +15550101000
​
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=GLB" \
  -F "services=glb_intelligence_service" \
  -F "vendor_data=user-1234" \
  -F "phone=+15550101000"

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 glb_intelligence_service currently documents this normalized shape:
  • Varies by registry response.

​
Pricing & SLAs

Global - Core Intelligence Service queries are billed only when Didit receives a conclusive result from the validation source.
  • Per-call price: $0.41 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