Email Content Extractor API is designed to identify email addresses associated with temporary domains. These disposable email services are often used for quick registrations, system testing, or, in some cases, for malicious purposes such as fraud, spam, or promotion abuse. The API offers a reliable and accurate way to determine whether an email belongs to a temporary domain, returning structured information with a simple Boolean result: isDisposable: true or false.
Using this API provides multiple benefits. First, it improves the quality of data within user bases, reducing fake registrations or ghost accounts that affect retention metrics.
Its integration is simple thanks to its lightweight design and JSON format response. Simply send the email address and the API returns clear information, including the evaluated domain, the analyzed email, and an indicator of whether or not it belongs to a disposable service. This process can be incorporated into registration flows, form validation, user verification, or analysis of existing data in customer databases.
In conclusion, this API offers an efficient and scalable solution for detecting disposable emails, ensuring greater security, reliability, and cleanliness in user management and digital communications.
{"provider":null,"disposable":false,"state":"Undeliverable","hits":["Undeliverable"]}
curl --location --request POST 'https://zylalabs.com/api/10248/email+content+extractor+api/19755/email+disposable' --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 Email Disposable endpoint returns structured data indicating whether an email address belongs to a disposable domain. The response includes the evaluated email, the domain analyzed, and a Boolean value indicating if it is disposable (isDisposable: true or false).
The key fields in the response data include "email" (the analyzed email address), "domain" (the domain of the email), and "isDisposable" (a Boolean indicating if the email is from a disposable service).
The response data is organized in a JSON format, making it easy to parse. It typically includes fields for the email address, the domain, and the disposable status, allowing for straightforward integration into applications.
The primary parameter for the Email Disposable endpoint is the "email" parameter, which should contain the email address you want to analyze. This allows users to customize their requests based on specific email addresses.
Typical use cases include validating user registrations, preventing fraud, enhancing data quality in customer databases, and improving form validation processes by filtering out disposable email addresses.
Data accuracy is maintained through continuous updates and monitoring of disposable email domains. The API uses reliable sources to identify and verify temporary domains, ensuring high-quality results.
Users can utilize the returned data by integrating it into their registration flows or validation processes. For example, if "isDisposable" is true, the application can prompt users to provide a different email address, enhancing data integrity.
Standard data patterns include a clear indication of whether an email is disposable or not. Users can expect consistent responses with the same structure, allowing for predictable handling of results in their applications.
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
Service Level:
100%
Response Time:
428ms
Service Level:
100%
Response Time:
448ms
Service Level:
100%
Response Time:
372ms
Service Level:
100%
Response Time:
606ms
Service Level:
100%
Response Time:
28ms
Service Level:
100%
Response Time:
172ms
Service Level:
100%
Response Time:
312ms
Service Level:
100%
Response Time:
2,216ms
Service Level:
100%
Response Time:
368ms
Service Level:
100%
Response Time:
434ms