As users increasingly rely on email communication for a variety of purposes, such as customer acquisition, marketing campaigns and account management, ensuring the accuracy and validity of email addresses has become crucial. The Email Integrity API is designed to address this need by providing comprehensive email verification and validation capabilities.
In essence, the Email Integrity API performs a series of checks and validations on email addresses to ensure their accuracy and validity. These checks include syntax validation, domain verification and mailbox verification. Syntax validation checks the structure of the e-mail address to ensure that it follows the standard format (e.g., [email protected]). Domain verification checks the existence of the domain part of the email address by querying DNS records, while mailbox verification checks whether the mailbox associated with the email address exists and is accessible.
By performing these checks, the Email Integrity API helps companies identify and remove invalid or inaccurate email addresses from their databases. This not only improves the overall quality of customer data, but also helps avoid problems such as bounced messages, spam complaints and low email deliverability rates.
One of the main advantages of using the Email Integrity API is its ability to detect and flag disposable or temporary email addresses. These are email addresses provided by temporary email services that users typically use for short-term purposes, such as registering for online services or accessing restricted content. While these email addresses may serve legitimate purposes in some cases, they are often associated with spam, fraud and abuse. By identifying and filtering disposable email addresses, the API helps companies maintain a clean and reliable email database, thereby improving the effectiveness of their email marketing campaigns and communication efforts.
In conclusion, the Email Integrity API is a valuable tool for companies looking to improve the accuracy and validity of their email databases. By performing comprehensive checks and validations, detecting disposable email addresses, and offering additional features such as real-time validation and integration capabilities, the API helps users maintain clean and reliable email databases, improve email deliverability, and enhance overall communication effectiveness.
It will receive parameters and provide you with a JSON.
Besides the number of API calls, there is no other limitation.
{"duplicates":[],"results":[{"email":"[email protected]","domain":"gmail.com","classification":"Risky","status":["Attempt_Rejected","Delivery failed; the reason is similar to \"rejected\"."],"result":{"syntaxValidation":{"passed":true,"message":"The address is valid according to syntax rules."},"domainValidation":{"passed":true,"message":"gmail.com is verified","suggestion":""},"isDisposableEmail":{"passed":false,"message":"Disposable validation passed for gmail.com"},"mxRecords":{"exists":true,"records":[{"exchange":"alt3.gmail-smtp-in.l.google.com","priority":30},{"exchange":"alt4.gmail-smtp-in.l.google.com","priority":40},{"exchange":"alt1.gmail-smtp-in.l.google.com","priority":10},{"exchange":"alt2.gmail-smtp-in.l.google.com","priority":20},{"exchange":"gmail-smtp-in.l.google.com","priority":5}],"message":"gmail.com domain has valid DNS records."},"roleAccount":{"passed":false,"role":"","message":"The email address is not a recognized role account"},"ispSpecific":{"passed":true,"message":"Following the syntactic rules of the target mail exchanger for the gmail.com domain, the address is considered syntactically valid."},"freeEmail":{"passed":true,"message":"This email address is associated with a well-known free email provider"},"smtpPing":{"passed":true,"message":"SMTP ping passed"}}},{"email":"[email protected]","domain":"gmail.com","classification":"Risky","status":["Attempt_Rejected","Delivery failed; the reason is similar to \"rejected\"."],"result":{"syntaxValidation":{"passed":true,"message":"The address is valid according to syntax rules."},"domainValidation":{"passed":true,"message":"gmail.com is verified","suggestion":""},"isDisposableEmail":{"passed":false,"message":"Disposable validation passed for gmail.com"},"mxRecords":{"exists":true,"records":[{"exchange":"alt1.gmail-smtp-in.l.google.com","priority":10},{"exchange":"gmail-smtp-in.l.google.com","priority":5},{"exchange":"alt4.gmail-smtp-in.l.google.com","priority":40},{"exchange":"alt3.gmail-smtp-in.l.google.com","priority":30},{"exchange":"alt2.gmail-smtp-in.l.google.com","priority":20}],"message":"gmail.com domain has valid DNS records."},"roleAccount":{"passed":false,"role":"","message":"The email address is not a recognized role account"},"ispSpecific":{"passed":true,"message":"Following the syntactic rules of the target mail exchanger for the gmail.com domain, the address is considered syntactically valid."},"freeEmail":{"passed":true,"message":"This email address is associated with a well-known free email provider"},"smtpPing":{"passed":true,"message":"SMTP ping passed"}}},{"email":"[email protected]","domain":"gmail.com","classification":"Risky","status":["Attempt_Rejected","Delivery failed; the reason is similar to \"rejected\"."],"result":{"syntaxValidation":{"passed":true,"message":"The address is valid according to syntax rules."},"domainValidation":{"passed":true,"message":"gmail.com is verified","suggestion":""},"isDisposableEmail":{"passed":false,"message":"Disposable validation passed for gmail.com"},"mxRecords":{"exists":true,"records":[{"exchange":"alt1.gmail-smtp-in.l.google.com","priority":10},{"exchange":"gmail-smtp-in.l.google.com","priority":5},{"exchange":"alt3.gmail-smtp-in.l.google.com","priority":30},{"exchange":"alt2.gmail-smtp-in.l.google.com","priority":20},{"exchange":"alt4.gmail-smtp-in.l.google.com","priority":40}],"message":"gmail.com domain has valid DNS records."},"roleAccount":{"passed":false,"role":"","message":"The email address is not a recognized role account"},"ispSpecific":{"passed":true,"message":"Following the syntactic rules of the target mail exchanger for the gmail.com domain, the address is considered syntactically valid."},"freeEmail":{"passed":true,"message":"This email address is associated with a well-known free email provider"},"smtpPing":{"passed":true,"message":"SMTP ping passed"}}},{"email":"[email protected]","domain":"gmail.com","classification":"Risky","status":["Attempt_Rejected","Delivery failed; the reason is similar to \"rejected\"."],"result":{"syntaxValidation":{"passed":true,"message":"The address is valid according to syntax rules."},"domainValidation":{"passed":true,"message":"gmail.com is verified","suggestion":""},"isDisposableEmail":{"passed":false,"message":"Disposable validation passed for gmail.com"},"mxRecords":{"exists":true,"records":[{"exchange":"alt2.gmail-smtp-in.l.google.com","priority":20},{"exchange":"gmail-smtp-in.l.google.com","priority":5},{"exchange":"alt1.gmail-smtp-in.l.google.com","priority":10},{"exchange":"alt4.gmail-smtp-in.l.google.com","priority":40},{"exchange":"alt3.gmail-smtp-in.l.google.com","priority":30}],"message":"gmail.com domain has valid DNS records."},"roleAccount":{"passed":false,"role":"","message":"The email address is not a recognized role account"},"ispSpecific":{"passed":true,"message":"Following the syntactic rules of the target mail exchanger for the gmail.com domain, the address is considered syntactically valid."},"freeEmail":{"passed":true,"message":"This email address is associated with a well-known free email provider"},"smtpPing":{"passed":true,"message":"SMTP ping passed"}}}]}
curl --location --request POST 'https://zylalabs.com/api/3542/email+integrity+api/3886/validation' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"emails": [
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]"
]
}'
| 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.
To use this API users will have to indicate emails to get information about whether they are valid emails.
The Email Integrity API designed to ensure the accuracy, reliability and security of email communications by providing comprehensive email validation, verification and integrity checks.
There are different plans to suit all tastes, including a free trial for a small number of requests, but your rate is limited to avoid abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The Validation endpoint returns a JSON object containing details about the validity of the provided email addresses. This includes fields such as syntax validation, domain verification, disposable email status, and mailbox accessibility.
Key fields in the response include "email," "domain," "classification," "status," and detailed validation results like "syntaxValidation," "domainValidation," and "isDisposableEmail," which provide insights into the email's validity.
The response data is structured as a JSON object with an array of results. Each result contains specific validation details for each email, including validation status and messages, allowing for easy interpretation of the data.
The Validation endpoint provides information on syntax correctness, domain existence, mailbox accessibility, and whether the email is disposable or a role account, helping users assess email validity comprehensively.
Users can input one or more email addresses as parameters in the POST request to the Validation endpoint. Each email address will be individually validated and returned in the response.
Data accuracy is maintained through multiple validation checks, including syntax validation, DNS queries for domain verification, and mailbox checks, ensuring reliable results for each email address processed.
Typical use cases include user registration validation, newsletter subscription verification, contact form submissions, account verification, and password recovery processes, enhancing data quality and communication effectiveness.
Users can analyze the returned data to filter out invalid or disposable emails, improve their email lists, and enhance deliverability rates. The detailed validation results allow for targeted actions based on the classification and status of each email.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
1,541ms
Service Level:
100%
Response Time:
316ms
Service Level:
100%
Response Time:
755ms
Service Level:
100%
Response Time:
799ms
Service Level:
100%
Response Time:
3,692ms
Service Level:
100%
Response Time:
57ms
Service Level:
100%
Response Time:
49ms
Service Level:
100%
Response Time:
342ms
Service Level:
100%
Response Time:
813ms
Service Level:
100%
Response Time:
628ms
Service Level:
60%
Response Time:
2,150ms
Service Level:
100%
Response Time:
1,254ms
Service Level:
100%
Response Time:
427ms
Service Level:
100%
Response Time:
1,017ms
Service Level:
100%
Response Time:
2,379ms
Service Level:
100%
Response Time:
605ms
Service Level:
100%
Response Time:
2,283ms
Service Level:
100%
Response Time:
1,120ms
Service Level:
100%
Response Time:
1,282ms