Send the email in the email parameter to receive its status, SMTP validation, if it is disposable, and if it belongs to a role account.
Verify Email - Endpoint Features
| Object | Description |
|---|---|
email |
[Required] |
{"address":"[email protected]","status":"valid","catch_all":false,"role":false,"disposable":false,"account":"example.user","domain":"gmail.com","mx_record":"alt1.gmail-smtp-in.l.google.com.","mx_found":true}
curl --location --request GET 'https://zylalabs.com/api/5320/validify+mail+api/6880/[email protected]' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Send a mail in the email parameter, and get its status, including whether it is valid, disposable or role.
It is an API that verifies emails to optimize deliverability and avoid bounces with SMTP and DNS validation.
Receives an email; returns validity status, role, and bounce or catch-all details.
Validation of mailing lists for marketing purposes. Reduction of bounces in email campaigns. Detection of temporary emails and role accounts.
Beside the number of API calls per month allowed, there are no other limitations.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
The API uses API keys for authentication. To access the API, include your API key in the request header. The API key is provided upon registration and should be kept secure.
The API returns detailed information about the age and history of a domain, including years, months and days since its creation, as well as expiration and update dates.
The Verify Email endpoint returns data regarding the validity of an email address, including its status (valid, invalid, catch-all, or unknown), whether it is disposable, and if it belongs to a role account.
Key fields in the response include "address" (the email checked), "status" (validity), "catch_all" (if it's a catch-all address), "role" (if it's a role account), "disposable" (if it's a temporary email), and "mx_record" (the mail exchange server).
The response data is structured in JSON format, with key-value pairs that provide specific details about the email's validity and characteristics, making it easy to parse and utilize in applications.
The endpoint provides information on email validity, SMTP validation, whether the email is disposable, and if it belongs to a role account, helping users assess the quality of their email lists.
Users can customize their requests by sending different email addresses in the "email" parameter to receive tailored validation results for each specific address.
The Validify Mail API sources its data from DNS records, SMTP servers, and various databases that track disposable and role-based email addresses, ensuring comprehensive validation.
Data accuracy is maintained through regular updates and checks against multiple sources, including real-time SMTP responses and DNS queries, to ensure the information is current and reliable.
Typical use cases include validating email addresses before sending marketing campaigns, cleaning up mailing lists to reduce bounce rates, and identifying temporary or role-based emails to improve engagement.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
601ms
Service Level:
100%
Response Time:
605ms
Service Level:
100%
Response Time:
797ms
Service Level:
100%
Response Time:
814ms
Service Level:
100%
Response Time:
376ms
Service Level:
100%
Response Time:
699ms
Service Level:
100%
Response Time:
120ms
Service Level:
100%
Response Time:
16,709ms
Service Level:
100%
Response Time:
392ms
Service Level:
100%
Response Time:
726ms
Service Level:
100%
Response Time:
2,672ms
Service Level:
100%
Response Time:
3,110ms
Service Level:
100%
Response Time:
3,513ms
Service Level:
100%
Response Time:
3,386ms
Service Level:
100%
Response Time:
3,383ms
Service Level:
50%
Response Time:
1,673ms
Service Level:
50%
Response Time:
5,254ms
Service Level:
50%
Response Time:
4,387ms
Service Level:
100%
Response Time:
2,298ms
Service Level:
33%
Response Time:
1,570ms