The Temporary Mail Blocker API provides advanced detection of temporary and disposable email domains, helping businesses maintain clean and accurate databases. Powered by a dynamic database updated in real time, this API identifies and blocks fraudulent sign-ups, ensuring a secure and trustworthy user experience. By analyzing new domains linked to disposable email services, it delivers proactive protection against abusive users and fake accounts. Ideal for platforms requiring reliable user authentication, it enhances data integrity, prevents fraud, and improves decision-making processes. Protect your platform with efficient and scalable email verification technology.
Detect Temporary Mail - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"domain":"hotmail.com","score":8,"meta":{"block_list":false,"domain_age":28,"website_resolves":true,"accepts_all_addresses":false,"valid_email_security":true}}
curl --location --request POST 'https://zylalabs.com/api/5749/temporary+mail+blocker+api/7478/detect+temporary+mail' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"domain": "[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 Temporary Mail Blocker API is a service that detects and blocks disposable email domains in real time, helping businesses maintain clean databases and prevent fraud.
By identifying and blocking fraudulent sign-ups linked to temporary email services, the API ensures that only legitimate users are able to register, thus maintaining the integrity of your data.
The API is ideal for any platform that requires reliable user authentication, such as e-commerce sites, online services, and membership platforms, where accurate user data is crucial.
The API is powered by a dynamic database that is updated in real time, allowing it to effectively identify new disposable email domains as they emerge.
Yes, the API is designed to be easily integrated into existing systems, providing scalable email verification technology to enhance user authentication processes.
The Detect Temporary Mail endpoint returns data indicating whether a given email domain is disposable. It includes a score, metadata about the domain, and its status regarding block lists and email security.
The key fields in the response include "domain" (the checked email domain), "score" (a numerical value indicating the likelihood of being disposable), and "meta" (which contains details like "block_list," "domain_age," and "valid_email_security").
The response data is structured in JSON format, with the main domain information at the top level and additional metadata nested within the "meta" object, allowing for easy parsing and access to specific details.
The primary parameter for this endpoint is the "domain," which should be included in the body of the POST request. Users can customize their requests by specifying different email domains to check.
Data accuracy is maintained through a dynamic database that is continuously updated with new information about disposable email domains, ensuring that the API can effectively identify and block fraudulent sign-ups.
Typical use cases include validating user registrations on e-commerce sites, preventing spam sign-ups on membership platforms, and ensuring data integrity in online services that require reliable user authentication.
Users can utilize the returned data by analyzing the "score" to determine the risk level of the domain and using the "meta" information to make informed decisions about whether to allow or block user registrations.
The API employs various quality checks, including real-time updates from trusted sources and validation against known disposable email services, to ensure the reliability and accuracy of the data returned.
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:
768ms
Service Level:
100%
Response Time:
764ms
Service Level:
100%
Response Time:
264ms
Service Level:
100%
Response Time:
209ms
Service Level:
100%
Response Time:
699ms
Service Level:
100%
Response Time:
113ms
Service Level:
100%
Response Time:
573ms
Service Level:
100%
Response Time:
804ms
Service Level:
100%
Response Time:
2,205ms
Service Level:
100%
Response Time:
334ms
Service Level:
100%
Response Time:
2,995ms
Service Level:
100%
Response Time:
4,758ms
Service Level:
100%
Response Time:
13,970ms
Service Level:
100%
Response Time:
340ms
Service Level:
100%
Response Time:
13,217ms
Service Level:
100%
Response Time:
636ms
Service Level:
100%
Response Time:
119ms
Service Level:
100%
Response Time:
12,826ms
Service Level:
100%
Response Time:
1,142ms
Service Level:
100%
Response Time:
13,217ms