DQVerify
AddressEmailPhone

API Response Codes — Complete Reference

This page is a complete reference for all response codes returned by DQVerify APIs — both HTTP-level errors and service-specific validation codes. Use the sections below to look up any code you receive.

HTTP Errors

These errors occur at the HTTP transport level and are common across all DQVerify API services.

Classic APIs

HTTP StatusCauseTypical Response
400 Bad RequestMissing or empty mandatory parameter (Licence, Email, Tel, Pays, Adresse)400 Bad Request or empty JSON response
500 Internal Server ErrorMissing mandatory parameter in Geocoding endpoints (IDVoie, Num, Pays)500 Internal Server Error
Licence errorMissing, empty, or invalid Licence parameter** LICENCE KO ** (Email), Licence Down in JSON (Phone), or empty response (Address)
unauthorized_clientIncorrect licence number (Email Classic API only)unauthorized_client

RESTful APIs

RESTful APIs return structured JSON error objects:

{
  "status": 400,
  "message": "Missing parameters",
  "details": "Licence",
  "error": "bad request"
}
Status / ErrorCause
400 bad requestMissing or empty mandatory parameter. The details field names the missing parameter.
401 unauthorized_clientInvalid or inactive licence key
401 UnauthorizedMissing or invalid OAuth2 authentication token (RESTful Email and Phone APIs)

Email API

Returned by Email API — Validate an email address (Classic) and RESTful Email API — email/lookup

IdError codes

CodeDescriptionSuggested UI Message
00Valid email addressValid email
01Email syntax correct but username could not be checked (catch-all domain)Valid email
02Email address not found for this domainPlease check your email address
03Inbox is full — soft bouncePlease check your email address
04Empty email addressPlease check your email address
91Syntax errorPlease check your email address
92Unknown domainPlease check your email address
93Blacklisted email address or domainPlease check your email address
94Unauthorized usernamePlease check your email address
95Disposable or temporary email addressPlease check your email address
99Verification service temporarily unavailable — treat as validValid email

CodeActivite codes

Returned only when level 2 verification is enabled. M = current month.

CodeDescription
100Email was delivered at least once
200Email address is valid and active
201Active within the last month (M-1)
202Active between M-1 and M-2
203Active between M-2 and M-3
204Active between M-3 and M-4
206Active between M-4 and M-6
209Active between M-6 and M-9
212Active between M-9 and M-12
300Inactive email address

Phone API

Returned by Phone API — Classic and RESTful Phone API — phone/lookup

IdError codes

CodeDescription
0Invalid or non-existing phone number
1Valid and attributed phone number
2Valid syntax only — number has not been attributed (reserved range)

Status codes

French mobile numbers only. Set Status=Y in the request. (Level 2 verification, Classic API only.)

CodeDescription
0Reachable — mobile number is currently reachable
1Not Reachable — mobile number is currently not reachable

Address API — CheckAddress (DQECodeDetail)

Returned by Classic API — CheckAddress and RESTful Address — checkaddress. The DQECodeDetail field gives the address validation quality score.

CodeDescriptionSuggested UI Message
10Address is fully correctValid address
20Address is correct — street not found but is CEDEX or POValid address
21Small city — street number out of rangePlease check your postal address
22Small city — street number missing, rest of address correctPlease check your postal address
23Large city — street number out of rangePlease check your postal address
24Large city — street number missing, rest of address correctPlease check your postal address
25CEDEX address unknown (when CEDEXA is active)Valid address
30Small city — street name not recognizedPlease check your postal address
31Small city — street name not recognized (alternative match)Please check your postal address
40Small city — street missing, district recognized but insufficientPlease check your postal address
41Small city — street name missingPlease check your postal address
50Large city — street name not recognizedPlease check your postal address
51Large city — street not recognized, district recognized but insufficientPlease check your postal address
60Large city — street missing, district recognized but insufficientPlease check your postal address
61Large city — street name missingPlease check your postal address
70Postal code / city mismatch — cannot be corrected (street present)Please check your postal address
71Postal code / city mismatch — cannot be corrected (street missing)Please check your postal address
80Address input block is emptyPlease check your postal address
81Address input block is empty (alternative)Please check your postal address
90International address detected — validValid address
95Missing or incorrect country codePlease check your postal address

Quick interpretation guide

  • 10, 20, 25, 90 — valid address
  • 21–24 — street number issue
  • 30–61 — street name issue
  • 70–71 — postal code / city mismatch
  • 80–81 — empty input
  • 95 — wrong or missing country code

Geocoding API (CodeQualiteGeo)

Returned by Geocoding API and by CheckAddress when Version=1.

CodeDescription
1ENTREE — Main access point to an enclosure or land parcel
2BATIMENT — Building or part of a building
3ESCALIERS — Stairwell inside a building
4LOGEMENT — Housing or room inside a building
5PARCELLE CADASTRALE — Cadastral parcel
6SEGMENT DE VOIE — Position derived from the connecting street segment
7POINT D'ACCES TECHNIQUE — Technical access point
8POINT DELIVRANCE POSTALE — Postal delivery point (mailbox)
9ZONE D'ADRESSAGE — Point placed in the dependent locality
10CENTRE VILLE — City centre, lowest precision
00CENTRE DE LA VOIE — Point in the centre of the street
90A CONTROLER — Coordinates should be verified
99NON PRESENTE — Coordinates could not be computed

When Licence is missing or invalid, the Geocoding API returns Latitude: 0.00 and Longitude: 0.00 instead of an HTTP error.

B2B API

Returned by B2B Classic API — RECSIRET, SIRETINFO, RESTful B2B API — Lookup, and GetInfo.

DQE_status (SIRETINFO extended form)

ValueDescription
FOUNDCompany was found in the database
NOT FOUNDNo matching company was found for the provided SIRET

CompanyStatus

ValueDescription
1Company is in operation
0Company is no longer in operation

MainCompanyFlag

ValueDescription
1This record is the company head office
0This record is a secondary establishment

SMS Phone Confirmation API

Returned by SMS Phone Confirmation API — Send OTP (GDPR_MSG) and Verify OTP (GDPR_VERIF).

GDPR_MSG — SMS delivery status

StatusDescription
PENDINGSMS sent to operator, awaiting delivery confirmation
DELIVEREDSMS successfully delivered
UNDELIVERABLESMS could not be delivered
EXPIREDSMS expired before delivery confirmation
REJECTEDSMS rejected by the operator

GDPR_MSG — error codes

CodeDescription
00No errors
01Missing parameters
02Service not authorized for this licence
03Invalid phone number
04Invalid country code
05Invalid duration
06Country not found
07Invalid company name (must be 3–11 characters)
08Internal API error
09No delivery status received from operator
10Invalid consent values
11At least one communication channel must be enabled

GDPR_VERIF — error codes

CodeDescription
00No errors — PIN verified successfully
01Missing parameters
02PIN must contain 6 digits
03PIN has expired
04PIN is invalid for this token or phone number
05Invalid token

ID Mobile API

Returned by all ID Mobile scopes: Simswap, Matching without OTP, Number Verify, Formfilling, and Billing. Errors are returned as a JSON object with error_id and error_type fields.

{
  "status": "error",
  "error_type": "invalid phone number",
  "error_id": "10"
}

Step 1 error codes — all scopes

error_iderror_typeDescription
01invalid requestThe request is not valid
02invalid licence keyThe licence is not valid
04invalid scopeThe requested scope is invalid
05missing or empty parameter (user_infos) for this scopeA required parameter is missing
06bad parameter format (user_infos) is not valid JSONThe user_infos parameter is not valid JSON
07missing mandatory key in user_infos (phone)The phone key is mandatory
09ineligible phone numberThe phone number is not eligible
10invalid phone numberThe phone number does not exist
11phone number is emptyThe phone number is empty
12phone check failedThe operator verification failed
13operator not foundThe operator could not be found
14operator not authorized for this licenceYour licence is not authorized for this operator
15operator not supported yetThe solution is not yet available for this operator
16operator unreachableThe operator could not be contacted
17scope not supported by this operator yetThis scope is not supported by the operator
30invalid or expired tokenAuthentication token has expired — obtain new token via Token endpoint

Step 2 error codes — Number Verify, Formfilling, Billing

Additional codes for the retrieval call (Step 2).

error_iderror_typeDescription
01invalid requestThe request is not valid
02invalid licence keyThe licence is not valid
04invalid scopeThe requested scope is invalid
18failed to retrieve data from operatorNo data received after OTP validation
20phone mismatchOTP validation not completed — phone mismatch
21access deniedOTP validation declined by user
30invalid or expired tokenAuthentication token has expired
99internal server errorServer error — retry or contact support