DQE APIs let you validate, standardise and enrich customer data in real time — postal addresses, email addresses, phone numbers, names, company data and identity — directly from your own applications and forms.
Start here
- Classic authenticationCall DQE APIs with your licence key.
- OAuth2 authenticationGenerate a temporary Bearer token before calling DQE APIs.
- Response codes & errorsComplete reference of API response codes.
API catalogue
- AddressAutocomplete, check and verify postal addresses.
- Geocoding & Reverse GeocodingGet GPS coordinates from an address, or an address from coordinates.
- EmailValidate email addresses and suggest corrections.
- PhoneValidate and standardise phone numbers.
- NameValidate first names and last names.
- B2BSearch companies and get company information.
- CityDateFind a birth locality by postcode.
- ID MobileSilent phone verification, identity match without OTP, SIM swap detection.
- SMS Phone ConfirmationSend and verify one-time passwords by SMS.
- ID CheckVerify an identity document.
Request and response format
- GET or POSTDQE APIs can be called using either the GET or POST method.
- JSON responsesResponses are always returned in JSON format.
- ISO 3166-1 alpha-3For some services, the country parameter is mandatory and must use the ISO 3166-1 alpha-3 country code.
Important notes
Warning: These APIs must not be used for batch processing.
DQE is not responsible for issues arising from API implementations used in blocking mode. Blocking-mode implementation is at the sole discretion and responsibility of the client.
If this implementation leads to service disruption or financial loss, DQE cannot be held liable under any circumstances. We strongly recommend that clients thoroughly assess and test their API integration to ensure it matches their operational requirements and risk management strategy.
Related to