Disposable Mail Validator API is a powerful tool designed to help businesses identify and filter out temporary or fake email addresses during user registration or data collection processes. Disposable email addresses are often used once or twice, making them unreliable for communication and marketing efforts. By implementing this API, you can ensure that your campaigns reach real users, improving engagement rates and preserving the integrity of your database. This API offers a simple and efficient solution for detecting disposable domains and email providers in real-time. It compares input emails against an extensive and constantly updated database of known disposable email services. The response is fast, accurate, and easy to integrate into your existing systems or applications. Whether you're managing a registration system, verifying email lists, or protecting against spam signups, this API saves time and resources by automating the detection process. Start with a free plan to test its capabilities and scale as your validation needs grow. Maintain the quality of your user base and optimize your email campaigns with the API.
Send a POST request with email to validate the emails and receive a JSON response indicating validity.
Is Expendable - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"email":"[email protected]","is_disposable":true}
curl --location --request POST 'https://zylalabs.com/api/5677/disposable+mail+validator+api/7399/is+expendable' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"email": "[email protected]"
}'
| 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.
The Disposable Mail Validator API is a tool designed to identify and filter out temporary or fake email addresses during user registration or data collection, ensuring that your communications reach real users.
The API compares input emails against an extensive and constantly updated database of known disposable email services, allowing it to accurately identify disposable domains and email providers in real-time.
Using this API helps improve engagement rates by ensuring your campaigns reach real users, preserves the integrity of your database, and saves time and resources by automating the detection process.
Yes, the Disposable Mail Validator API is designed for easy integration into your existing systems or applications, allowing for a seamless user experience.
Yes, the API offers a free plan that allows you to test its capabilities before scaling up based on your validation needs.
The API returns a JSON response containing information about the validity of the provided email address, specifically indicating whether it is disposable or not.
The key fields in the response data include "email," which shows the input email address, and "is_disposable," a boolean value indicating if the email is from a disposable domain.
The response data is structured in JSON format, with key-value pairs that provide clear information about the email's validity, making it easy to parse and utilize in applications.
The primary parameter for the POST Is Expendable endpoint is the "email" field, where users submit the email address they wish to validate.
Data accuracy is maintained through continuous updates to the database of known disposable email services, ensuring that the API can reliably identify new disposable domains as they emerge.
Typical use cases include validating user registrations, cleaning email lists, and preventing spam signups, ensuring that marketing efforts target genuine users.
Users can utilize the returned data by checking the "is_disposable" field to filter out disposable emails, thereby enhancing the quality of their user base and improving engagement rates.
Users can expect a consistent response format with the email address and its disposable status, allowing for straightforward integration into validation workflows and decision-making processes.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
228ms
Service Level:
100%
Response Time:
213ms
Service Level:
100%
Response Time:
182ms
Service Level:
100%
Response Time:
39ms
Service Level:
100%
Response Time:
561ms
Service Level:
100%
Response Time:
75ms
Service Level:
100%
Response Time:
1,692ms
Service Level:
100%
Response Time:
1,971ms
Service Level:
100%
Response Time:
293ms
Service Level:
100%
Response Time:
2,084ms
Service Level:
33%
Response Time:
1,906ms
Service Level:
33%
Response Time:
1,452ms
Service Level:
33%
Response Time:
2,200ms
Service Level:
33%
Response Time:
4,478ms
Service Level:
100%
Response Time:
767ms
Service Level:
33%
Response Time:
1,829ms
Service Level:
100%
Response Time:
558ms
Service Level:
100%
Response Time:
634ms
Service Level:
100%
Response Time:
534ms
Service Level:
100%
Response Time:
17,611ms