Hey there! Welcome to the API documentation for the EmailRecon email address validation services. In the event that you have trouble following our guides and sample codes or you encounter any unexpected behaviour please contact us.



To authenticate your app with the API you must append your private API key to the API end point (please see the example code to the right). That's it, your request is now authenticated and logged in your API call log.


Response codes

The EmailRecon API uses standard HTTP response codes to communicate the result of an API call. Below is a list of the possible codes that could be returned and how they should be interpreted.

  • 200 Processed

    The command was processed successfully.

  • 422 Unprocessable

    Well formatted request however some technical issue is preventing the serving of the request

  • 400 Command unknown

    The end-point you have sent the request to is not valid (for example, the end point should be /email)

  • 405 Command invalid

    The HTTP request method used is not compatible with the selected end-point. This can occur when using POST rather than GET for example.

  • 409 Command malformed

    The request has been incorrectly constructed. This can occur when omitting required parameters or providing them in the wrong type.

  • 401 Unauthorized

    The request was not authorised. This can occur when using an incorrect key, if the server IP is not on the account whitelist, or if the account is banned.

  • 402 Billing

    The request was refused due to a billing issue with the associated account.

  • 500 Internal Server Error

    The client did everything correctly, but we've had an internal issue.

Email validation

This end-point accepts a supposed email address as the argument and performs multiple validation checks and returns results in a json object.

Request fields

Parameter Description
email The supposed email address to investigate.

Response fields

Parameter Description
valid_form Set to true if the submitted email address is of valid form. Do not use the output of this field alone to determine deliverability - please see the 'deliverable' field described below.
role Set to true if the email address pertains to a role in an organisation such as 'support' or 'billing' rather than a specific individual.
disposable Set to true if the email address is hosted and managed by a disposable ESP.
free Set to true if the email address is hosted at an ESP which is free to use by the general public, examples include Gmail and Hotmail.
typo Set to true if a typographical error was detected in the email address.
suggestion Set to null if no typographical error was detected or set to a single string value containing an alternate address suggestion if an error was detected.
valid_mx Set to true if the host of the email address is associated with a valid mail exchange server.
deliverable This field is a composite of various fields above, it will be set to true if the supplied email address meets the minimum requirements to be a deliverable valuable email, in short this field is set to true if the address has valid form and MX records, has no typos, and is disposable.
high_value A high value mailbox is classed as any mailbox that does not reside on a free mail platform, such as Gmail. For example, the email address of david@emailrecon.com would be classed as high value.
highest_value When the host of a mailbox is found in the Majestic world top 1 million website list the email is marked as of the highest value, allowing you to target some of your most important contacts first!
Majestic Million CSV by Majestic 12 is licensed under a Creative Commons Attribution 3.0 Unported License.

curl 'https://api.emailrecon.com/email?key=YOUR_KEY_HERE&email=david@emailrecon.com'