Verifying an Email

This version has been depreciated

Existing integrations using this API will continue to work as usual. However, new integrations should be created using the V4 API. We will continue to support this API for the foreseeable future but will not be adding new features to it.​

Our API can be seamlessly integrated into your signup or onboarding process with just a single request.

To verify an email, simply use the request below, substituting your access_token and the email you want to verify.

curl -X POST https://api.neverbounce.com/v3/single\
    -d access_token={access_token}\
    -d email={email}

Unsure where to get an access_token? Click here to find out how to generate one.

Read more about the single endpoint here.

{
    "success": true,
    "result": 0,
    "result_details": 0,
    "execution_time": 0.47218990325928
}

In the response, you’ll find the result parameter. This parameter will indicate the status of the email. View the different result codes here.

Point of Entry Usage

Use in the browser

This version of the API is not suitable for use in client-side scripts (e.g. jQuery, Javascript). Using it on the client-side would require exposing sensitive API credentials, giving anyone access to your account.

A common scenario for using the single endpoint is to verify emails at the point of entry; helping to keep your user base or newsletter list clean. At the point of entry, we suggest allowing valid, catchall, and unknown emails to proceed, while blocking only disposable and invalid emails. It is important to allow unknown results to proceed, as they may occur more frequently with the single endpoint than it does with bulk verification.

Additionally, we’ve found that with some smaller email hosts, it is not uncommon to take several seconds (sometimes tens of seconds) to respond. It’s for this reason that we suggest enforcing a client side timeout of approximately 10 seconds in your HTTP request library (ie: Curl, Guzzle, Httparty, etc…) and treat any timeouts as unknowns.