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.
To use this endpoint you must enter 1 or more emails.
| Object | Description |
|---|---|
Request Body |
[Required] Json |
Continue with Google
Continue with Github
{"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'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Email Integrity API REST API, simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
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.
Sure, you can use it and pay only when you use it. The credit can’t be expired.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
606ms
Service Level:
100%
Response Time:
2,720ms
Service Level:
100%
Response Time:
1,600ms
Service Level:
100%
Response Time:
5,726ms
Service Level:
100%
Response Time:
359ms
Service Level:
100%
Response Time:
570ms
Service Level:
100%
Response Time:
2,352ms
Service Level:
100%
Response Time:
2,943ms
Service Level:
100%
Response Time:
708ms
Service Level:
100%
Response Time:
524ms
Service Level:
100%
Response Time:
217ms
Service Level:
100%
Response Time:
1,024ms
Service Level:
100%
Response Time:
894ms
Service Level:
100%
Response Time:
3,738ms
Service Level:
100%
Response Time:
592ms
Service Level:
100%
Response Time:
1,352ms
Service Level:
100%
Response Time:
396ms
