The Trusted Email Verifier API provides a powerful solution to detect disposable and public email addresses, enhancing data integrity and security in user registration. This API enables users to determine if an email address is from a temporary or high-risk provider, helping to filter out low-value or risky emails. By employing advanced detection methods, including MX (Mail Exchange) record validation, it ensures the email domain is authentic and actively hosted.
The API also suggests corrections for common typos, optimizing the registration experience by helping users submit valid emails. Ideal for applications focused on secure sign-up processes, SaaS platforms requiring reliable data, or any service needing robust email validation, Trusted Email Verifier API is a simple yet comprehensive tool. It provides clean, reliable data by blocking disposable emails, enhancing marketing efficiency, and fostering secure interactions.
Sends the email parameter to the endpoint to verify if it belongs to a temporary or public domain.Receives a JSON with the status and details of the email.
Check Disposable Email - Endpoint Features
| Object | Description |
|---|---|
email |
[Required] |
{
"did_you_mean": null,
"domain": "gianes.com",
"is_disposable_domain": true,
"is_public_domain": false,
"mx": true,
"status": true
}
curl --location --request GET 'https://zylalabs.com/api/5478/trusted+email+verifier+api/7101/[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 an email to the endpoint to receive information about its legitimacy and possible public domain or temporary status.
Validates whether an email belongs to a public or temporary domain, helping to filter out low-value records.
The API receives an email and responds with data about its validity, type (temporary/public), and other details useful for evaluation.
User verification: Allows to accept only emails from reliable providers, blocking disposable accounts. Campaign optimization: Ensures that emails in marketing campaigns are valid and of high quality. Security protection: Prevents users from registering with temporary or spam emails, improving security.
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 endpoint returns a JSON object containing information about the email's legitimacy, including whether it belongs to a disposable or public domain, MX record validation, and suggestions for typos.
Key fields include "is_disposable_domain," "is_public_domain," "mx," "status," and "did_you_mean." These fields indicate the email's validity and provide suggestions for corrections.
The response is structured as a JSON object with key-value pairs. Each field provides specific information about the email's status, allowing for easy parsing and integration into applications.
The endpoint provides information on whether an email is from a disposable or public domain, its MX record status, and suggestions for correcting common typos.
The endpoint accepts a single parameter: the email address to be verified. Ensure the email is formatted correctly to receive accurate results.
Data accuracy is maintained through advanced detection methods, including MX record validation and continuous updates to the database of disposable and public domains.
Typical use cases include user registration validation, ensuring marketing campaign integrity, and enhancing security by filtering out temporary or spam emails.
Users can utilize the returned data to filter out invalid emails during registration, improve email list quality for campaigns, and enhance overall user security by blocking disposable accounts.
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.
Service Level:
100%
Response Time:
63ms
Service Level:
100%
Response Time:
71ms
Service Level:
100%
Response Time:
577ms
Service Level:
100%
Response Time:
765ms
Service Level:
100%
Response Time:
37ms
Service Level:
100%
Response Time:
681ms
Service Level:
100%
Response Time:
467ms
Service Level:
100%
Response Time:
1,014ms
Service Level:
100%
Response Time:
187ms
Service Level:
100%
Response Time:
844ms
Service Level:
100%
Response Time:
4,109ms
Service Level:
100%
Response Time:
2,345ms
Service Level:
100%
Response Time:
19,841ms
Service Level:
100%
Response Time:
6,994ms
Service Level:
100%
Response Time:
422ms
Service Level:
100%
Response Time:
448ms
Service Level:
100%
Response Time:
19,779ms
Service Level:
100%
Response Time:
5,684ms
Service Level:
100%
Response Time:
9,067ms
Service Level:
100%
Response Time:
10,140ms