Perform a single email validation request.

If you require a profile photo along with the validation results, just add &photo=true at the end of the API endpoint. We will bill you 0.2 extra credits for each successful profile photo added.

To find the full name and avatar of an email owner, you must add the &append=true in the validation endpoint and you will pay 2 extra credits for each successful data enrichment.

🚧

IMPORTANT NOTE:

If you are going to use this API within a sign-up form, you must consider Deliverable, Accept-all and Unknown statuses as valid, so you do not miss out on any sign-ups. Another simple way to do this is by checking the send_transactional parameter. If its value is 1, the email is eligible for being a new user.

If you require a profile photo along with the validation results, just add &photo=true at the end of the API endpoint. We will bill you 0.2 extra credits for each successful profile photo added.

Response Parameters:

Parameter

Type

Definition

email

[email]

The email address you are requesting to validate.

code

[Integer]

DeBounce validation response code. In order to understand DeBounce results and codes, visit this link.

role

[true, false]

Is the email role-based or not. Role emails such as "[email protected]", "[email protected]" etc. are not suitable for sending marketing emails to.

free_email

[true, false]

Is the email from a free email provider - like Gmail - or not.

result

[Invalid, Risky, Safe to Send, Unknown]

The final result of the validation process. This response will help to determine whether you should send marketing emails to a recipient or not.

reason

[string]

The reason why the result is given (view full reasons via this link).

send_transactional

[0, 1]

Is it suggested that you send transactional emails to the recipient or not (0: no, 1: yes). Generally, it is suggested to send transactional emails to Valid, Accept-all, and Unknown emails.

did_you_mean

[string]

If you use a misspelled email address like [email protected], the validation engine tries to suggest you the corrected email address.

success

[0, 1]

Is your call successful or not (0: no, 1: yes). If your credits are zero or you have provided an invalid API key, you will receive a 0 response.

balance

[Integer]

Remaining balance on your account after the current API call.

Other Responses

The response you get when your credits have been used:

HTTP/1.1 402 Payment Required
{
   "debounce":{
      "error":"Credits Low",
      "code":"0"
   },
   "success":"0"
}

The response you get when the API key is invalid:

HTTP/1.1 401 Unauthorized

{
   "debounce":{
      "error":"Wrong API",
      "code":"0"
   },
   "success":"0"
}

The response you get when your call rate is high (more than 10 concurrent calls):

HTTP/ 429 Too Many Requests

{
   "debounce":{
      "error":"Maximum concurrent calls reached",
      "code":"0"
   },
   "success":"0"
}

If you are using the Public_API key, each user (or unique IP address) can call your API endpoint 20 times per day. Otherwise, the API output will be:

HTTP/ 429 Too Many Requests

{
   "debounce":{
      "error":"Authentication Failed - The maximum number of calls per day reached."
   },
   "success":"0"
}
Language
Authentication
Query
Response
Click Try It! to start a request and see the response here!