The Disposable Email Validator API is an API specialized in identifying and verifying temporary and disposable email domains. This tool is essential to ensure the quality and authenticity of email addresses in registration systems, subscriptions and other digital interactions.
Temporary email domains are those that allow users to create email addresses that are valid for a limited time or for a single use. These emails are often used to avoid spam, sign up for services without revealing a personal email address, or test online services without compromising personal data. While they offer some privacy and convenience, they can also be used for less legitimate purposes, such as creating fake accounts or circumventing restrictions on digital platforms.
The Disposable Email Validator API operates efficiently to identify and validate domains associated with temporary emails. Its operation is based on an up-to-date database containing an extensive list of domains known to offer disposable email services. The API performs the following key functions:
Data Reception: The user sends a request to the API with the email domain they wish to verify. This request can be part of a user record validation process, spam filtering, or data analysis in a system.
Domain Verification: The API compares the received domain with its database of temporary email domains. It can also perform additional checks to detect common patterns associated with disposable mail services.
Response: The API returns a response indicating whether the domain is from a temporary or disposable email service. The response can include additional information such as the type of mail service (e.g., temporary or disposable) and details about the validity of the domain.
This API receives an email domain and provides a response indicating whether the domain is from a temporary or disposable email service.
Spam Registration Prevention: Uses the API to identify and block temporary email domains during the user registration process on web platforms, preventing the creation of fake accounts.
Subscription Filtering: Implements the API in subscription services to ensure that only permanent emails can sign up, improving the quality of the subscriber list and reducing the unsubscribe rate.
Contact Form Protection: Integrate the API into contact forms on websites to prevent users with temporary emails from sending messages, ensuring more legitimate and valuable communications.
E-Commerce Platform Security: Use the API to verify email addresses during the checkout process, preventing fraud and ensuring that customer contact data is valid and durable.
Test Account Validation: Apply the API to identify and filter disposable emails in test or demo accounts, preventing temporary users from gaining access without real purchase or subscription intent.
1 request per second on all planes.
To use this endpoint, you send an email domain in the request. The API checks if the domain is temporary or disposable and returns the result.
Email Domain - Endpoint Features
| Object | Description |
|---|---|
user_input_email |
[Required] |
{"success":true,"message":"Validation Done","result":{"email":"[email protected]","code":"5","role":false,"free_email":true,"result":"Safe to Send","reason":"Deliverable","send_transactional":1,"did_you_mean":""}}
curl --location --request GET 'https://zylalabs.com/api/4985/disposable+email+validator+api/6289/[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 a request to the endpoint with the email domain. You will receive a response as to whether it is disposable.
The Disposable Email Validator API verifies whether an email domain is temporary or disposable
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.
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.
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 API returns data indicating whether an email domain is temporary or disposable. It includes fields such as "success," "message," and "result," which provides details about the email's validity and type.
Key fields in the response include "email," "code," "role," "free_email," "result," "reason," and "send_transactional." These fields provide insights into the domain's status and deliverability.
The response data is structured in JSON format. It contains a top-level object with "success" and "message," followed by a "result" object that details the email domain's validation status and characteristics.
The API provides information on whether an email domain is disposable, its deliverability status, and additional insights like the type of email service (temporary or disposable) associated with the domain.
The API utilizes an up-to-date database containing a comprehensive list of known disposable email domains. This database is regularly maintained to ensure accuracy and reliability.
Users can leverage the returned data to filter out disposable email addresses during user registration, enhance the quality of subscriber lists, and prevent fraudulent activities on their platforms.
Typical use cases include preventing spam registrations, filtering subscriptions, securing contact forms, and validating email addresses during e-commerce transactions to ensure data integrity.
Users can customize their requests by specifying the email domain they wish to validate. The API processes this input and returns tailored results based on the provided domain.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
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:
1,090ms
Service Level:
100%
Response Time:
35ms
Service Level:
100%
Response Time:
764ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
517ms
Service Level:
100%
Response Time:
71ms
Service Level:
100%
Response Time:
217ms
Service Level:
100%
Response Time:
559ms
Service Level:
100%
Response Time:
639ms
Service Level:
100%
Response Time:
9,157ms
Service Level:
100%
Response Time:
1,541ms
Service Level:
90%
Response Time:
622ms
Service Level:
100%
Response Time:
3,408ms
Service Level:
100%
Response Time:
1,017ms
Service Level:
100%
Response Time:
172ms
Service Level:
100%
Response Time:
638ms
Service Level:
100%
Response Time:
130ms
Service Level:
100%
Response Time:
819ms
Service Level:
100%
Response Time:
222ms
Service Level:
83%
Response Time:
564ms