The Temporal Email Verification API is designed to authenticate email addresses, discerning temporary or disposable ones, often linked to spam or fraud. In our digital age, it is critical to protect against spam, fraud and misuse. This API is an essential tool for users, as it ensures the integrity and security of communication channels.
Primarily, the Temporal Email Verification API performs thorough evaluations of email addresses to determine their association with temporary or disposable email services. These services provide users with transient email addresses, which are typically used for ephemeral purposes such as registering for online services, accessing restricted content, or circumventing email verification requirements. While these email addresses may serve legitimate purposes in certain cases, they are often aligned with spam, fraudulent activity and malicious intent.
In essence, the Temporal Email Verification API helps users validate email addresses and protect themselves from spam, fraud and misuse. With its extensive validation capabilities, the API enables users to strengthen their email security measures, preserving the integrity and security of communication channels. Whether it's preventing spam submission on web forms, thwarting fraudulent account registrations or filtering suspicious emails from mailing lists, the Transient Email Verification API offers a reliable solution to identify temporary or disposable email addresses and mitigate the associated risks.
It will receive parameters and provide you with a JSON.
Besides the number of API calls, there is no other limitation.
Email Check - Endpoint Features
| Object | Description |
|---|---|
email |
[Required] Email address to lookup. |
{"status":"invalid","reason":"rejected_email","email":"[email protected]","user":"shane","domain":"gmail.com","public":true,"disposable":false,"role":false}
curl --location --request GET 'https://zylalabs.com/api/3540/temporal+email+verification+api/4941/[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.
To use this API users must provide an email address to verify if it is a disposable email.
The Temporal Email Verification API designed to authenticate email addresses by identifying temporary or disposable email accounts commonly associated with spam or fraudulent activity.
There are different plans to suit all tastes, including a free trial for a small number of requests, but your rate is limited to avoid 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 POST Email Temporaly Detection endpoint returns data indicating whether an email is disposable, along with its provider and validity state. The GET Email Check endpoint provides detailed information about the email, including its disposable status, SMTP availability, and MX records.
Key fields include "disposable" (true/false), "state" (valid/invalid), "provider" (email service provider), "reason" (for invalid emails), and "mx_record" (mail exchange server) in the GET Email Check response.
The response data is structured in JSON format, with key-value pairs representing various attributes of the email address. For example, the GET Email Check response includes fields like "email," "user," and "success," making it easy to parse and utilize.
The POST endpoint provides basic validation of whether an email is temporary, while the GET endpoint offers comprehensive details, including the email's validity, disposable status, SMTP availability, and domain information.
Both endpoints require the "email" parameter, which should contain the email address to be verified. No additional parameters are necessary for basic functionality.
Users can leverage the "disposable" field to filter out temporary emails in registration forms or mailing lists. The "reason" field helps identify issues with invalid emails, allowing for better user experience and security measures.
The API sources its data from various email service providers and databases that track disposable email addresses, ensuring a broad coverage of known temporary email services.
Data accuracy is maintained through regular updates and quality checks against known disposable email providers. The API continuously monitors and validates email addresses to ensure reliable results.
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:
344ms
Service Level:
100%
Response Time:
381ms
Service Level:
100%
Response Time:
844ms
Service Level:
100%
Response Time:
432ms
Service Level:
100%
Response Time:
2,205ms
Service Level:
100%
Response Time:
197ms
Service Level:
100%
Response Time:
167ms
Service Level:
100%
Response Time:
904ms
Service Level:
100%
Response Time:
764ms
Service Level:
100%
Response Time:
116ms
Service Level:
100%
Response Time:
15,594ms
Service Level:
100%
Response Time:
17ms
Service Level:
100%
Response Time:
19ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
17,707ms
Service Level:
100%
Response Time:
17,825ms
Service Level:
100%
Response Time:
15ms
Service Level:
100%
Response Time:
18ms
Service Level:
100%
Response Time:
15,502ms
Service Level:
100%
Response Time:
15,679ms