How to integrate our LIVE ENSOEMAIL solution
HistoryÂ
| Date | Version number | Description |
| 28/02/2022 | 1.0 | Version 1 - launch of the EnsoEmail API |
Â
The EnsoEmail solution is made available via a REST API to support your validation and online verification processes.
The EnsoEmail solution is based on the following technologies/verifications to guarantee a 99% reliability rate of the results:
- Email syntax check
- Domain verification
- SMTP test
- Temporary/Jetable mail
- Typo correction
Authentication
In order to access our services, it is essential to authenticate yourself via a unique secure key (or token) which is provided to you by Data Enso.
Your token must be integrated into the header under the "api_key" parameter and present during each call to the Enso Email API.
Calls to servers
Calls to the EnsoEmail service must be made to the following URL:
https://api.dataenso.com/mail
ENSOEMAIL API call
To check an e-mail address in real time and obtain reliable results, here's the list of fields available to compose your search.
| Field | Status | Type | Example | Comments |
| Api_key | Required | String | your-api-key | Token generated by Data Enso |
| Required | String | email-test@dataenso.com | Check e-mail address |
API call response
Once you have made the call to our services, here are the fields available in return:| Field | Type | Example | Comments |
| string | email-test@dataenso.com | Verified e-mail address. | |
| result | string | "ok" | Result of e-mail verification: ok, catch_all, unknown, error, disposable, invalid |
| resultcode | integer | 1 | The result of the e-mail verification in "integer": 1 (ok), 2 (catch_all), 3 (unknown), 4 (error), 5 (disposable), 6 (invalid) |
| subresult | string | "ok" | Additional check details: "unknown" "ok" "internal_error" "invalid_syntax" "no_local_ip_available" "dns_server_failed" "dns_no_mx" "dns_no_a" "could_not_connect" "no_code_in_banner" "invalid_banner_code" "no_code_in_ehlo_response" "no_code_in_helo_response" "no_code_in_mail_from_response" "no_code_in_rcpt_to_response" "ip_blocked" "no_mailbox" "mailbox_disabled" "mailbox_full" "greylisted" "connection_lost" "connection_timeout" "connection_refused" "connection_reset_by_peer" "connection_no_route_to_host" "host_not_accept_incoming_mail" "mail_service_unavailable" "bad_domain" "dns_error" "anti_spam_system" "dns_no_domain" "dns_refused" "timeout_error" |
| didyoumean | string | Suggested auto-correction for common typos. | |
| error | string | Error message displayed here if the result is "error". | |
| livemode | boolean | If the request was made with a Key API for production or testing |
Example query
https://api.dataenso.com/mail/?mail=email-test@dataenso.com \
-h "api_key:your-token"
Answer:
{
"email": "email-test@dataenso.com",
"result": "invalid",
"resultcode": 6,
"subresult": "no_mailbox",
"didyoumean": "",
"error": "",
"livemode": true
}
Example of return codes
API Response
{
"email": "testemail@gmal.com",
"result": "invalid",
"resultcode": 6,
"subresult": "unknown",
"didyoumean": "testmail@gmail.com",
"error": "",
"livemode": true
}
API BAD API KEY Response
{
"email": "testemail@gmal.com",
"result": "error",
"resultcode": 4,
"subresult": "unknown",
"didyoumean": "testmail@gmail.com",
"error": "apikey_not_found",
"livemode": true
}
API Response Missing Email
{
"email": "",
"result": "error",
"resultcode": 4,
"subresult": "unknown",
"didyoumean": "",
"error": "No email specified",
"livemode": true
}
To receive our various API Docs by e-mail, please fill in the form below