{
"email": "[email protected]",
"normalizedEmail": "[email protected]",
"status": "valid",
"score": 100,
"isValid": true,
"checks": {
"syntax": {
"valid": true,
"localPart": "zuck",
"domain": "fb.com"
},
"length": {
"valid": true,
"localPartLength": 4,
"domainLength": 6,
"totalLength": 11
},
"domain": {
"resolvable": true,
"hasMx": true,
"mxRecords": [
"mxa-00082601.gslb.pphosted.com",
"mxb-00082601.gslb.pphosted.com"
],
"hasAddressRecord": false,
"nullMx": false
},
"disposable": {
"isDisposable": false
},
"free": {
"isFreeProvider": false
},
"role": {
"isRoleAccount": false
},
"typo": {
"hasSuggestion": false
}
},
"reasons": [
"Domain has MX records"
]
}
curl --location --request GET 'https://zylalabs.com/api/13027/emaillabs+email+verification+api/26144/[email protected]' --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 EmailLabs Email Verification 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 commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
EmailLabs Email Verification API
EmailLabs verifies and scores any email address in milliseconds, running every meaningful deliverability check short of an SMTP probe — so you catch bad, fake, and risky addresses before they ever hit your database.
What it checks
gmial.com → gmail.com).What you get back
A single JSON response with a per-check breakdown, a 0–100 confidence score, and a clear verdict: valid, risky, or invalid — plus human-readable reasons for the result.
Why use it
Highlights
The Verify Email endpoint returns a JSON response containing a breakdown of various checks performed on the email address, including syntax validation, domain existence, disposable status, and more. It also provides a confidence score and a verdict indicating whether the email is valid, risky, or invalid.
Key fields in the response include "email" (the original email), "normalizedEmail" (formatted email), "status" (valid, risky, invalid), "score" (0-100 confidence score), and "checks" (detailed results of each validation check).
The response data is structured in a JSON format, with a top-level object containing the email address, status, score, and a nested "checks" object that details the results of each validation check, such as syntax, length, domain, and more.
The endpoint provides information on email syntax validity, length compliance, domain and MX record checks, disposable email detection, identification of free providers, role-based account flags, and typo suggestions for misspelled domains.
Data accuracy is maintained through rigorous validation checks based on established standards (RFC 5321 and RFC 5322) and real-time DNS queries to verify domain existence and MX records, ensuring reliable results for email verification.
Typical use cases include reducing bounce rates by validating email addresses during sign-up, blocking disposable email registrations, enhancing user experience with typo suggestions, and cleaning existing email lists for better deliverability.
Users can customize their requests by specifying the email address they wish to verify in the GET request to the Verify Email endpoint. The API processes this input and returns detailed validation results based on the provided email.
Standard data patterns include a clear "status" indicating the email's validity, a "score" reflecting confidence in the result, and detailed checks that return boolean values and additional information, such as suggestions for typos or flags for disposable addresses.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund