Transient Mail Verification API

The Transient Mail Verification API validates email addresses, identifying temporary or disposable ones to prevent spam and fraud.

About the API:  

The Transient Mail Verification API designed to verify the legitimacy of email addresses by identifying temporary or disposable email addresses commonly used for spam, fraudulent activities, or temporary access. In today's digital landscape, protection against spam, fraud and abuse is crucial for businesses, developers and individuals alike. The Transient Mail Verification API offers a perfect solution to validate email addresses and ensure the integrity and security of communication channels.

Basically, the Transient Mail Verification API performs extensive checks on email addresses to determine if they belong to temporary or disposable email services. These services provide users with temporary email addresses that are often used for short-term purposes, such as registering for online services, accessing restricted content, or evading email verification requirements. While these email addresses may serve legitimate purposes in some cases, they are commonly associated with spam, fraudulent activities, and other malicious intent.

In conclusion, the Transient Mail Verification API helps users seek to validate email addresses and protect themselves against spam, fraud, and abuse. With its comprehensive validation capabilities, the API enables users to enhance their email security measures and ensure the integrity and security of communication channels. Whether preventing spam submissions from web forms, blocking fraudulent account registrations, or filtering suspicious emails from mailing lists, the Transient Mail Verification API provides a reliable solution for identifying temporary or disposable email addresses and mitigate associated risks.

 

What this API receives and what your API provides (input/output)?

It will receive parameters and provide you with a JSON.

 

What are the most common uses cases of this API?

  1. Account Registrations: Verify the legitimacy of email addresses during user account registrations to prevent fraudulent registrations and ensure data accuracy.

    Contact Forms – Validate email addresses entered into website contact forms to prevent spam and maintain communication integrity.

    Subscription Services – Authenticate email addresses for subscription services to filter out temporary or disposable email addresses and ensure genuine subscribers.

    Online Purchases: Confirm the validity of email addresses provided by customers during online purchases to prevent fraudulent transactions and ensure accurate order communication.

    User Feedback: Validate email addresses provided by users for feedback forms or surveys to ensure genuine feedback and maintain data integrity.

     

Are there any limitations to your plans?

1,000 requests per hour in all plans.

API Documentation

Endpoints


To use this endpoint you must indicate a domain. You can also optionally indicate an email address.



                                                                            
GET https://zylalabs.com/api/3536/transient+mail+verification+api/3879/email+checker
                                                                            
                                                                        

Email Checker - Endpoint Features

Object Description
domain [Required] Indicates a domain
email [Optional] Indicates a email
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"score":100,"tests_passed":"3/3","passed":true,"mail_server_ip":"142.250.4.26","mx_records":[{"host":"gmail-smtp-in.l.google.com.","pref":5},{"host":"alt1.gmail-smtp-in.l.google.com.","pref":10},{"host":"alt2.gmail-smtp-in.l.google.com.","pref":20},{"host":"alt3.gmail-smtp-in.l.google.com.","pref":30},{"host":"alt4.gmail-smtp-in.l.google.com.","pref":40}]}
                                                                                                                                                                                                                    
                                                                                                    

Email Checker - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/3536/transient+mail+verification+api/3879/email+checker?domain=gmail.com&email=brethdain' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Transient Mail Verification API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

Transient Mail Verification API FAQs

To use this API, users must provide a domain or email to verify its validity.

The Transient Mail Verification API designed to validate email addresses, specifically focusing on identifying transient or temporary email addresses commonly used for short-term purposes.

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 Email Checker endpoint returns a JSON object containing validation results for the provided email or domain. This includes a score indicating validity, the number of tests passed, and details about the mail server, such as its IP address and MX records.

Key fields in the response include "score" (validity score), "tests_passed" (number of successful checks), "passed" (boolean indicating validity), "mail_server_ip" (IP address of the mail server), and "mx_records" (list of mail exchange records).

The response data is structured as a JSON object. It includes a primary validity score, a boolean for overall pass status, and detailed information about the mail server, organized into fields for easy access and interpretation.

The Email Checker endpoint provides information on the validity of an email address, including whether it is temporary or disposable, the mail server's IP address, and MX records, which help determine the email's routing.

Users can provide a domain as a required parameter and optionally include an email address for more specific validation. This allows for flexibility in checking either a domain or a specific email address.

Users can utilize the returned data to filter out invalid or disposable email addresses during account registrations or form submissions, enhancing security and reducing spam. The score and tests_passed fields help assess the reliability of the email.

The API sources its data from various email service providers and databases that track disposable email services. This ensures a comprehensive and up-to-date validation process for identifying temporary email addresses.

Data accuracy is maintained through regular updates and quality checks against known email service providers and disposable email lists. This helps ensure that the API provides reliable and current validation results.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the β€˜X-Zyla-API-Calls-Monthly-Remaining’ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The β€˜X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.


Related APIs


You might also like