Verifies input data to a lead generation database. Authoritative real-time identity lookup for Netherlands. Pay-per-call, no contracts.
Verifies input data to a lead generation database. Didit exposes this service throughDocumentation Index
Fetch the complete documentation index at: https://docs.didit.me/llms.txt
Use this file to discover all available pages before exploring further.
POST /v3/database-validation/ so you can verify the submitted data against the authoritative source and receive normalized match results.
nld_consumer| Field | Required | Example |
|---|---|---|
first_name | Yes | John |
last_name | Yes | Doe |
date_of_birth | Yes | 1990-01-01 |
address | No | 123 Sample Street, Sample City, 10001 |
phone | No | +15550101000 |
email | No | john.doe@example.com |
first_name, last_name, date_of_birthaddress, phone, emailNLDnld_consumerJohnDoeYYYY-MM-DD format.Example: 1990-01-01123 Sample Street, Sample City, 10001+15550101000john.doe@example.comaddress is optional for this service. You can send one complete address string and Didit will split it into structured address elements when possible, or you can send the structured fields explicitly.address_element_1 is the street address, including street number and street type.address_element_2 is optional unit, building, floor, or extra address line. Didit only sends it when you provide it explicitly.address_element_3 is suburb, district, locality, or neighborhood.address_element_4 is city, town, state, province, or region.address_element_5 is postcode or postal code. postal_code is accepted as an alias.address_element_1 plus one searchable component such as address_element_3, address_element_4, or address_element_5; requests rejected before source lookup are not charged.source_data depend on what the registry returns. The generated example for nld_consumer currently documents this normalized shape:
date_of_birthfirst_namefull_namelast_namename_match_score