Verifying an Email

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\
    -d access_token=<ACCESS TOKEN>\
    -d email=<EMAIL>

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


    "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.

Please Note: Results are not available via the user dashboard and should be stored on the user’s requesting end.

Below is a list of the possible values for this parameter.

Point of Entry Usage

A common scenario for using the single endpoint is 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 valids, catchalls, and unknowns to proceed while blocking only disposable and invalid addresses. 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 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.

Result CodesAnchor

Value Description
0 Valid
1 Invalid
2 Disposable
3 Catchall
4 Unknown

For more information view the result code here.

Result Detail Codes

Value Description
0 No additional details
1 Provided email failed the syntax check