Temporary Email Lookup API

API ID 14068

Verify temp-mail, SMTP and email history with this intelligent API. Protect your signups and consumers from tem-mail based access.

100% uptime 2,108 ms avg response

API Documentation

Endpoints

Request
Analyzes email addresses for deliverability, domain reputation, risk factors, authentication settings, provider details, and validity indicators to support email verification.
Endpoint ID: 34503
GET https://zylalabs.com/api/14068/temporary+email+lookup+api/34503/full+email+analysis
INPUT PARAMETERS

Full Email Analysis — Endpoint Features

Object Description
email Required paste your email here

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

email
API EXAMPLE RESPONSE
JSON
{
    "alias": false,
    "catch_all": false,
    "confidence": 95,
    "corporate": false,
    "deliverable": true,
    "disposable": false,
    "dkim_configured": false,
    "dmarc_configured": false,
    "domain": "gmail.com",
    "domain_age_days": 67,
    "domain_first_seen": "2026-07-27T22:49:33.438261Z",
    "domain_risk_score": 15,
    "education": false,
    "email": "[email protected]",
    "free_provider": true,
    "government": false,
    "local_part": "someone",
    "metadata": {
        "cache_hit": false,
        "query_time_ms": 413
    },
    "mx_configured": true,
    "normalized_email": "[email protected]",
    "parked": false,
    "provider": "Google",
    "reputation": "fair",
    "risk_factors": [
        "new_domain"
    ],
    "risk_score": 15,
    "role_account": false,
    "spf_configured": false,
    "temporary": false,
    "valid_mx": true,
    "valid_syntax": true
}
Full Email Analysis — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14068/temporary+email+lookup+api/34503/[email protected]' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
The "Email Validation" endpoint is designed to verify the authenticity and format of email addresses submitted by users or applications. Its primary purpose is to ensure that the provided email addresses are syntactically correct, exist on a server, and are reachable to prevent issues such as bounces and spam complaints. Upon processing a request, the endpoint returns a JSON response containing the validation status, which includes fields like "isValid", "domainExists", and "mxRecords", along with detailed messages indicating the reasons for any failures. This endpoint is particularly useful for onboarding processes, account creation, and any scenario where reliable email communication is crucial, thereby enhancing user experience and improving email marketing efficacy.
Endpoint ID: 34502
GET https://zylalabs.com/api/14068/temporary+email+lookup+api/34502/email+validtion
INPUT PARAMETERS

Email Validtion — Endpoint Features

Object Description
email Required paste your email address here

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

email
API EXAMPLE RESPONSE
JSON
{
    "deliverable": true,
    "disposable": false,
    "email": "[email protected]",
    "valid_mx": true,
    "valid_syntax": true
}
Email Validtion — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14068/temporary+email+lookup+api/34502/[email protected]' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
The "SMTP Validator" endpoint is designed to verify the validity and accessibility of email addresses through a structured SMTP (Simple Mail Transfer Protocol) check. It accepts a single email address as input and attempts to establish a connection with the mail server associated with that address, ensuring the domain is correctly configured to receive emails and confirming the email's existence without actually sending a message. This endpoint returns a detailed response containing a success status, potential errors, and whether the email address is deliverable or undeliverable. Potential use cases include improving email list hygiene for marketing campaigns, validating user inputs during registration on web applications, and reducing bounce rates by ensuring that communications are directed to active and correct email addresses.
Endpoint ID: 34504
GET https://zylalabs.com/api/14068/temporary+email+lookup+api/34504/smtp+validator
INPUT PARAMETERS

SMTP Validator — Endpoint Features

Object Description
email Required paste your email here
timeout_ms Optional Timeout For query

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

email
timeout_ms
API EXAMPLE RESPONSE
JSON
{
    "accepts_all": false,
    "duration_ms": 5000,
    "email": "[email protected]",
    "greylisted": false,
    "mailbox_disabled": false,
    "mailbox_full": false,
    "smtp_status": "timeout"
}
SMTP Validator — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14068/temporary+email+lookup+api/34504/[email protected]&timeout_ms=5000' --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 Temporary Email Lookup 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.

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

(Save 2 months with annual billing 🎉)

Starts at
$10,000/Year


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

Overview

Verify temp-mail, SMTP and email history with this intelligent API. Protect your signups and consumers from tem-mail based access.

Temporary Email Lookup API FAQs

Each endpoint returns JSON data. The "Email Validation" endpoint provides fields like "deliverable," "disposable," and "valid_mx." The "Full Email Analysis" endpoint includes metrics such as "confidence," "domain_age_days," and "risk_score." The "SMTP Validator" returns details like "smtp_status," "accepts_all," and potential errors.

Key fields vary by endpoint. For "Email Validation," important fields include "isValid" and "domainExists." In "Full Email Analysis," look for "confidence" and "reputation." The "SMTP Validator" highlights "smtp_status" and "duration_ms," which indicate the connection time and status.

Response data is structured in JSON format, with each endpoint returning a set of key-value pairs. For example, "Email Validation" returns fields like "valid_syntax" and "disposable," while "Full Email Analysis" includes nested objects like "metadata." This structure allows for easy parsing and integration into applications.

The "Email Validation" endpoint checks email authenticity and format. The "Full Email Analysis" evaluates email content for sentiment and readability. The "SMTP Validator" verifies email address accessibility and server configuration. Each endpoint provides unique insights to enhance email communication.

Users can customize requests by specifying the email address they wish to validate or analyze. Each endpoint accepts a single email as input, allowing for targeted checks. For example, the "SMTP Validator" requires just the email address to perform its checks.

Typical use cases include validating user email addresses during registration, analyzing email content for marketing campaigns, and ensuring email deliverability to reduce bounce rates. Businesses can leverage this data to enhance user experience and improve communication strategies.

Data accuracy is maintained through rigorous validation processes, including syntax checks and server responses. The API performs real-time checks against mail servers and uses established protocols to ensure the information returned is reliable and up-to-date.

Standard data patterns include boolean values for deliverability (true/false) and risk scores indicating the safety of an email domain. Users can expect consistent fields across responses, such as "valid_syntax" and "deliverable," which help in assessing email quality effectively.

General FAQs

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.

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.

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.

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 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.

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.
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]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs