{
"tool": "email-verify",
"count": 1,
"results": [
{
"email": "[email protected]",
"syntaxValid": true,
"domain": "google.com",
"localPart": "josh",
"isRoleAccount": false,
"isFreeProvider": false,
"isDisposable": false,
"didYouMean": null,
"hasMx": true,
"mxHosts": [
"smtp.google.com"
],
"acceptsMailViaA": false,
"verdict": "valid",
"reason": "Domain accepts mail",
"checkedAt": "2026-10-20T19:49:15.322Z"
}
]
}
curl --location --request GET 'https://zylalabs.com/api/14367/bulk+email+validator+api/36024/[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 Bulk Email Validator 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.
Verify email addresses before you send: syntax, MX records, disposable and role-based detection, with a clear deliverability verdict.
JSON with tool, count and a results array. Each result row has the same fields as the example response on this page.
One call counts as one request, even when it asks for up to 25 emails at once. Asking for more options or a higher limit in the same call still counts as one request.
Official public APIs, public web pages, public files and DNS, fetched live at request time. No logins or paywalls are bypassed.
Most calls return in 2 to 15 s. Past 80 s you get HTTP 503 with Retry-After; send fewer items and retry.
Optional query parameters: dedupe. Each is listed under Parameters on this page with its allowed values or range. Values outside those limits return HTTP 400 with the allowed range.
JSON with an error message: 400 for a missing or invalid parameter (with the allowed values), 422 when no item can be processed (with a reason for each), 429 over the rate limit, and 503 with Retry-After when busy or past 80 s. If only some items fail, you get 200 with rows for the items that worked.
Send the items query parameter with up to 25 addresses to check, separated by commas, such as the contacts you plan to write to. Optional parameters: dedupe.
The Bulk Email Validator API returns data related to email address verification, including syntax validity, MX records, and whether the email is disposable or role-based. Each response includes a verdict and reasons for the validation.
Key fields in the response include "email," "verdict," "reason," "syntaxValid," "hasMx," "isDisposable," "isRoleAccount," and "mxHosts." These fields provide detailed insights into the email's validity and characteristics.
The response is structured in JSON format, containing a "tool" identifier, a "count" of processed emails, and a "results" array. Each item in the array corresponds to an email address and includes various validation details.
The endpoint provides information on email syntax validity, MX record presence, whether the email is disposable or role-based, and suggestions for similar valid emails. This helps ensure effective email communication.
Users can customize requests by including the "items" parameter with up to 25 comma-separated email addresses. The optional "dedupe" parameter can be added to remove duplicate entries from the results.
"syntaxValid" indicates if the email format is correct, "hasMx" shows if the domain can receive emails, "isDisposable" identifies temporary email services, and "isRoleAccount" indicates if the email is associated with a role rather than an individual.
Data accuracy is maintained through real-time checks against official public APIs, DNS records, and web pages. The API fetches data live at the time of the request, ensuring up-to-date information.
Typical use cases include cleaning email lists before campaigns, validating user sign-ups, and ensuring deliverability for marketing emails. This helps reduce bounce rates and improve communication effectiveness.
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