Temporary Mail API

Temporary Mail API

Temporary Disposable E-mail, fast and easy API.
Free Plan $0.00 Monthly Subscribe
500 Requests / Monthly
Free for Lifetime
No Credit Card Required
MOST POPULAR
Starter Plan $19.99 Monthly Subscribe
5,000 Requests / Monthly
Standard Support
Disposable Email Address
Clean and Secure
Pro Plan $59.99 Monthly Subscribe
20,000 Requests / Monthly
Standard Support
Disposable Email Address
Clean and Secure
Enterprise Plan $99.99 Monthly Subscribe
50,000 Requests / Monthly
Standard Support
Disposable Email Address
Clean and Secure
Custom Plan Volume Monthly Contact Us
Any requests volume you need
Disposable Email Address
Clean and Secure

Temp Mail API allows Developers and QA Testing teams to automatically test their Email workflows like sign-ups, and password resets with an endless amount of disposable inboxes.

Whether you do Manual Testing, use an API, or a framework like Selenium, Cypress, Playwright, or Puppeteer - Temp Mail API will close the loop on email testing.

The Temp Mail API is also suitable for creating your own Temporary Disposable Email app or website.

How it works:

  • Generate any email address by using our domain names.
  • Sign up on sites that require confirmation by email.
  • The site sends email to the address you specify.
  • The message comes to our SMTP server, processed and added to the database.
  • You make a request to the API with login and domain part of email address and get a list of emails etc.
  • Request API with message ID to get JSON formatted message with body, subject, date, attachments, etc. Or get raw message as arrived in base64 encoding.

Please note

You can generate any email address using our domain names without API notification - just think of your email address as [email protected]_domains and use it anywhere. Our servers receive all incoming messages; you just need to call them correctly. All incoming email messages are automatically removed ( self-destroyed) from our services within 1-2 hours.

For security reasons, you cannot receive messages from government services and major financial institutions or read messages from addresses on our domains such as [email protected], [email protected], [email protected], [email protected], [email protected], [email protected] etc. All other addresses are free to use.

The API is free to try. Please feel free to ask any questions: [email protected]

Temporary Mail API Reference

This API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Just Getting Started?

Check out our development quickstart guide.

Authentication

Temporary Mail API uses API keys to authenticate requests. You can view and manage your API keys in the Accounts page.

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.

All requests made to the API must hold a custom HTTP header named "apikey". Implementation differs with each programming language. Below are some samples.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Endpoints

Get message attachments by message id. Content response field encoded in base64 RFC 4648.

Parameters

mail_id (required)

Unique mail id.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get message attachments by message id.

Parameters

mail_id (required)

Unique mail id.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Delete message, where mail_id unique identifier assigned by the system.

Parameters

mail_id (required)

Unique mail id.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get list of usable domains.

Parameters
No parameters.
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Check and get a list of emails for a mailbox.

Parameters

hashed_email_address (required)

Md5 hash of email address. Email address should include one of the eligible domains listed on /domains endpoint. For [email protected] you should use 041e3c606326862bc70f92ab8af8a3fe.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get one message attachments by message id and attachment id from attachments list. Content response field encoded in base64 RFC 4648.

Parameters

atId (required)

Unique attachment id.

Location: Path, Data Type: string

mail_id (required)

Unique mail id.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get one message by id.

Parameters

mail_id (required)

Unique mail id.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get message source by mail_id.

Parameters

mail_id (required)

Unique mail id.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Rate Limiting

Each subscription has its own rate limit. When you become a member, you start by choosing a rate limit that suits your usage needs. Do not worry; You can upgrade or downgrade your plan at any time. For this reason, instead of starting with a larger plan that you do not need, we can offer you to upgrade your plan after you start with "free" or "gold plan" options and start using the API.

When you reach a rate limit (both daily and monthly), the service will stop responding and returning the HTTP 429 response status code (Too many requests) for each request with the following JSON string body text.

{
"message":"You have exceeded your daily\/monthly API rate limit. Please review and upgrade your subscription plan at https:\/\/apilayer.com\/subscriptions to continue."
}

A reminder email will be sent to you when your API usage reaches both 80% and 90%, so that you can take immediate actions such as upgrading your plan in order to prevent your application using the API from being interrupted.

You can also programmatically check your rate limit yourself. As a result of each request made to the APILayer, the following 4 fields provide you with all the necessary information within the HTTP Headers.

x-ratelimit-limit-month: Request limit per month
x-ratelimit-remaining-month: Request limit remaining this month
x-ratelimit-limit-day: Request limit per day
x-ratelimit-remaining-day: Request limit remaining today

You can contact our support unit if you need any assistance with your application regarding to handle the returned result by looking at the header information.

Error Codes

APILayer uses standard HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate a clientside error, which means that failed given the information provided (e.g., a missing parameter, unauthorized access etc.). Codes in the 5xx range indicate an error with APILayer's servers (normally this should'nt happen at all).

If the response code is not 200, it means the operation failed somehow and you may need to take an action accordingly. You can check the response (which will be in JSON format) for a field called 'message' that briefly explains the error reported.

Status Code Explanation
400 - Bad Request The request was unacceptable, often due to missing a required parameter.
401 - Unauthorized No valid API key provided.
404 - Not Found The requested resource doesn't exist.
429 - Too many requests API request limit exceeded. See section Rate Limiting for more info.
5xx - Server Error We have failed to process your request. (You can contact us anytime)

You can always contact for support and ask for more assistance. We'll be glad to assist you with building your product.