To use this endpoint, send a GET request with the email address. You will receive instant results about the validity of the email and its ability to receive messages.
Single Email Check - Endpoint Features
| Object | Description |
|---|---|
email |
[Required] Enter an email address |
{"address":"[email protected]","status":"invalid","catch_all":false,"role":false,"disposable":false,"account":"example","domain":"gmail.com","mx_record":"gmail-smtp-in.l.google.com.","mx_found":true}
curl --location --request GET 'https://zylalabs.com/api/5498/inbox+verifier+api/7133/[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 POST requests with an address or a batch of emails in JSON.You will receive real-time results on the validity of the emails.
The Inbox Verifier API validates email addresses in real time, providing immediate results on their validity and ability to receive emails.
The API receives email addresses in JSON format and provides a response with the validation of the email, verifying if it exists and if it can receive emails.
Validation of email lists for marketing campaigns. Real-time checking of e-mails when registering on platforms. Reducing bounces in email communications through pre-validation.
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 Single Email Check endpoint returns a JSON object indicating the validity of the provided email address. It specifies whether the email is deliverable (true) or undeliverable (false).
The response data includes the email address as the key and a boolean value as the value. For example, `"[email protected]": true` indicates the email is valid, while `"[email protected]": false` indicates it is not.
The response data is structured as a JSON object where each email address is a key. The corresponding value is a boolean that indicates the email's deliverability status.
The endpoint provides information on whether an email address is valid and capable of receiving messages, including format validation and mailbox existence checks.
Data accuracy is maintained through regular updates and checks against MX records and mailbox existence, ensuring that the validation results reflect the current status of the email addresses.
Typical use cases include validating user registrations, cleaning email lists for marketing campaigns, and reducing bounce rates by pre-validating email addresses before sending communications.
Users can utilize the returned data to filter out invalid email addresses from their lists, ensuring higher deliverability rates and improving overall email campaign effectiveness.
Users can expect a straightforward JSON response with email addresses as keys and boolean values. Valid emails will return true, while invalid ones will return false, allowing for easy parsing and integration.
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:
369ms
Service Level:
100%
Response Time:
500ms
Service Level:
100%
Response Time:
746ms
Service Level:
100%
Response Time:
765ms
Service Level:
100%
Response Time:
605ms
Service Level:
100%
Response Time:
601ms
Service Level:
100%
Response Time:
841ms
Service Level:
100%
Response Time:
71ms
Service Level:
99%
Response Time:
2,279ms
Service Level:
100%
Response Time:
552ms
Service Level:
100%
Response Time:
206ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
193ms
Service Level:
100%
Response Time:
114ms
Service Level:
100%
Response Time:
56ms
Service Level:
100%
Response Time:
59ms
Service Level:
100%
Response Time:
111ms
Service Level:
100%
Response Time:
100ms
Service Level:
100%
Response Time:
10ms
Service Level:
100%
Response Time:
231ms