Best-TempMail

Best Temp Mail API

Create disposable email inboxes and read what arrives, for automated testing, CI pipelines, and signup verification flows. Delivery methods Four ways to…

Communication#email

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Create disposable email inboxes and read what arrives, for automated
testing, CI pipelines, and signup verification flows.

Delivery methods

Four ways to receive mail, in rough order of how most callers use them:

  • Polling GET /inboxes/{address}/messages
  • Long poll GET /inboxes/{address}/wait holds the connection open up to 55s and returns the moment mail arrives
  • WebSocket wss://api.best-tempmail.com/ws for a persistent connection
  • Webhooks we POST to your own URL, signed so you can verify it came from us

Plans

CapabilityFreeFounders / DeveloperPro
Requests per hour15020005000
Burst per 10s100300300
Inbox creation3/day per IPunlimitedunlimited
Inbox lifetime (default)2 hours2 hours24 hours
Inbox lifetime (maximum)2 hours7 days30 days
Polling, wait, WebSocketyesyesyes
Webhooksnoyesyes
OTP extractionnoyesyes
Attachment downloadsnonoyes
Concurrent waits5520
Commercial usenoyesyes

Free access needs no key at all. Paid keys are sent in the x-api-key header.

Inbox ownership

An inbox created with an API key belongs to that key. Only that key can
read, wait on, or delete it; any other caller gets a 404, the same as an
address that never existed.

Inboxes created without a key (the free tier) have no owner and remain
readable by anyone who knows the address. Free callers only ever receive
random addresses, so this is not practically exploitable, but it is why
a paid key is the right choice for anything sensitive.

Endpoints 17

Inboxes

  • POSTCreate an inbox/inboxesCreates a disposable inbox. Both fields are optional: omit them and a random local part on a random domain is chosen. Plus-addressing works on every inbox,…
  • GETInbox metadata/inboxes/:address
  • DELETEDelete an inbox and its messages/inboxes/:address
  • POSTCreate several inboxes in one call (paid)/inboxes/bulkCreates count inboxes and returns them all. Intended for test suites building fixtures, which previously needed one call per address. Each inbox costs one…

Messages

  • GETList, search and filter messages/inboxes/:address/messagesNewest first. Returns summaries; fetch a single message for its body. With no parameters the response is the newest 100 messages, which is what this endpoint…
  • GETWait for the next message (long poll)/inboxes/:address/waitHolds the connection open until mail arrives or the timeout expires, replacing a polling loop with a single call. A timeout is not an error: it returns 200…
  • GETRead one message/inboxes/:address/messages/:idScoped to the inbox: a message id from another address returns 404, even though both share a domain.
  • GETExtract the verification code (paid)/inboxes/:address/messages/:id/otpReturns the verification code from a message, so you do not have to write a parser for every sender's format. Candidates are scored on the words around them,…
  • GETExtract the links, and the one to click (paid)/inboxes/:address/messages/:id/linksReturns every link in a message, classified, plus action_url: the one the email is asking the reader to click. A reset email holds eight links. Taking the…

Attachments

  • GETDownload an attachment (Pro)/inboxes/:address/messages/:id/attachments/:indexReturns the raw file with Content-Type and Content-Disposition set, so curl -O and browsers save it correctly. Attachments above 4 MB are refused with 413. In…

Webhooks

  • GETCurrent webhook and recent deliveries (paid)/webhooksIncludes the last delivery attempts with status codes and errors, so you can debug your own endpoint without contacting support.
  • POSTRegister a webhook URL (paid)/webhooksRegisters where mail should be POSTed. One URL per key; registering again replaces it and issues a new signing secret, which is how you rotate that secret.…
  • DELETEStop sending webhooks (paid)/webhooks

Service

  • GETList the domains inboxes can be created on/domainsFetch this rather than hardcoding a domain: the list changes as domains are added or rotated, and callers who read it keep working.
  • GETService health/health
  • GETCaller's current usage and limits/stats

Account

  • GETYour quota, plan and renewal date/usageEverything about the calling key: the hourly quota and how much of it is left, the lifetime request count, the plan, and when the subscription renews. Open to…

API details

Base URL
https://api.best-tempmail.com/v1
Authentication
An API key in the x-api-key header
Operations
17 operations on 14 pathsGET 12POST 3DELETE 2
Main resources
Messages 5Inboxes 4Service 3Webhooks 3Account 1Attachments 1
Response formats
application/json application/octet-stream
Description format
OpenAPI 3.0.3, API version 1

How to test the Best Temp Mail API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Best Temp Mail API collection, without the publisher's secrets.
  3. Add your credentialsThis API uses an API key in the x-api-key header. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Create an inbox” (POST /inboxes), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Best Temp Mail API?

Create disposable email inboxes and read what arrives, for automated testing, CI pipelines, and signup verification flows. Delivery methods Four ways to… It is listed under Communication and has 17 endpoints.

Who publishes the Best Temp Mail API?

It is listed from Best-TempMail's public API description (an OpenAPI document), not published by Best-TempMail on Swastik Codes. Anyone who controls best-tempmail.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Best Temp Mail API?

Requests go to https://api.best-tempmail.com/v1. Endpoint paths are added to this base URL.

How do I authenticate with the Best Temp Mail API?

With an API key in the x-api-key header.

How many endpoints does the Best Temp Mail API have?

17 operations on 14 paths (12 GET, 3 POST, 2 DELETE). The largest groups are Messages, Inboxes, Service, Webhooks.

Is forking the Best Temp Mail API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.