Skip to main content
Temp Mail Lab API gives backend applications isolated temporary addresses and private access to received messages, sanitized content, raw RFC 822 source, and attachments. It is designed for test automation, verification workflows, QA systems, and other server-side integrations that need temporary inbound mail without depending on an open website session.

Quickstart

Create an address and read its first messages.

Get an API key

Create a scoped server-side credential in the dashboard.

API reference

Review the complete eight-operation v1 contract.

Dashboard

Manage credentials, entitlement, and account usage.

​
What the API provides

  • Random or custom temporary addresses from domains available to your account.
  • A 30-day receiving reservation that does not depend on a browser session.
  • Parsed message metadata, text, sanitized HTML, raw source, and attachments.
  • Explicit ownership checks, scoped keys, opaque identifiers, and private storage.
  • Authoritative usage headers and a dedicated usage endpoint.

​
Important boundaries

The product is receive-only. It does not send email, invoke customer webhooks, open streaming connections, or run a polling job on your behalf. Every request is finite, and your application chooses when to make another read. Email reservations last 30 days. Messages, parsed bodies, raw source, and attachments expire 15 minutes after arrival. Review service limits before building your workflow.
Production is unavailable until the approved public launch. Customers do not receive staging or test keys.
Last modified on August 2, 2026