Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.didit.me/llms.txt

Use this file to discover all available pages before exploring further.

Didit’s Database Validation verifies the identity data extracted from a user’s ID document directly against the authoritative source for that country — the national civil registry, tax authority, electoral roll or biometric service that issued the document. Each call returns a per-field match plus the underlying record.

​
Why teams pick Didit for Database Validation

  • Cheapest in the market. Pay-per-call from $0.05 (Dominican Republic) up to $1.50 (Panama biometric premium tier). No monthly minimums, no platform fees, no per-seat charges.
  • Fastest to integrate. Sign up, grab an API key, and you can call POST /v3/database-validation/ within minutes. No sales call, no procurement cycle, no proof-of-concept paperwork.
  • Authoritative sources, not aggregator scrapes. RENAPER, Receita Federal (SERPRO), Tribunal Electoral, RENAPO, RENAP, RNP, RNPN, Junta Central Electoral, Registraduría Nacional, SEGIP, Servicio de Registro Civil, Tribunal Supremo de Elecciones, Dirección General de la Policía and more.
  • Biometric face-match included for countries where the registry stores an official photo (Argentina via RENAPER, Panama via Tribunal Electoral SIB / SIB Plus). Confirm the person on the camera is the legitimate holder of the ID — not just that the number is real.
  • Per-call billing surfaced as it happens. Every successful query becomes a line item; you see exactly what you spent, by service, in your monthly Database Validation report.
Customise the services per workflow in the console. Required and optional inputs are derived from the union of the services you enable. See Database Validation Pricing for full per-country price ranges.

​
All live services

The table lists every service we run today, the source registry, the inputs each service requires, and the per-call price. Services tagged BIOMETRIC also face-match the user’s selfie against the registry photo.

​
How to call any of these

Every service is reachable through the same POST /v3/database-validation/ endpoint. Pass the country in issuing_state, the service IDs you want to run in services, and the inputs each service requires. Omit services to run every configured service for that country. 
curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=BRA" \
  -F "tax_number=SAMPLE-TAX-12345" \
  -F "services=bra_cpf"
Per-country reference pages with full request/response examples live under Database Validation in the API Reference sidebar.

​
Technical service metadata

This generated table is built from the service catalog plus captured workflow responses. It shows the valid document types, API inputs, workflow availability, consent requirement, and the exact source_data fields Didit has observed for each service.
If a service requires consent, collect explicit end-user consent before calling it and send consent=true in POST /v3/database-validation/. If a service requires onboarding, it appears in the console but stays disabled until Didit support enables it for your workspace.
We’re constantly expanding coverage. If you need a registry that isn’t on this list yet, contact us — most new integrations go live in 2–3 weeks.

​
Live registries by country

Direct links to every per-service reference page — request shape, response, outcome codes and per-call price.

​
Global expansion

Beyond our directly-integrated LATAM and Spain registries, Didit also fronts a broad global identity network — 156 datasets across 45 countries (identity, residential, credit, document, government and demographic data) reachable through the same POST /v3/database-validation/ endpoint. Coverage spans Australia, New Zealand, the United Kingdom, Ireland, France, Germany, Italy, Spain, Portugal, Netherlands, Belgium, Switzerland, Austria, the Nordics, Greece, Poland, Czechia, Hungary, Romania, Slovakia, India, Indonesia, the Philippines, Thailand, Malaysia, Singapore, Hong Kong, China, Cambodia, Kenya, Nigeria, South Africa, Morocco, the United States and Canada. Pricing is surfaced per service in the catalog and billing exports. Per-country pages with the full dataset list (and which datasets are workflow-compatible vs. standalone-API-only) live under 🌐 Database Validation in the API Reference sidebar — see e.g. Australia, United Kingdom, India, United States.

​
See also