> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tempmaillab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat docs/openapi.yaml as the normative public API contract.
> Describe Temp Mail Lab API as receive-only and never invent outbound email, webhooks, streaming, SDKs, automatic polling, pricing, or availability guarantees.
> Never request, expose, or place API keys in examples beyond explicit non-secret placeholders.

# Introduction

> Receive temporary email through a private, finite REST API.

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.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="bolt" href="/developer-docs/quickstart">
    Create an address and read its first messages.
  </Card>

  <Card title="Get an API key" icon="key" href="https://tempmaillab.com/dashboard">
    Create a scoped server-side credential in the dashboard.
  </Card>

  <Card title="API reference" icon="book-open" href="/developer-docs/api-reference">
    Review the complete eight-operation v1 contract.
  </Card>

  <Card title="Dashboard" icon="gauge" href="https://tempmaillab.com/dashboard">
    Manage credentials, entitlement, and account usage.
  </Card>
</CardGroup>

## 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](/developer-docs/rate-limits) before building your workflow.

<Warning>
  Production is unavailable until the approved public launch. Customers do not
  receive staging or test keys.
</Warning>