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

# Getting Started

> Prepare a secure server-side integration before making your first request.

## Prerequisites

You need a Temp Mail Lab Premium account, an active API entitlement, and a scoped API key created in the dashboard. Production credentials will become available only after the approved public launch.

Call the API only from a trusted backend. Do not embed a key in browser JavaScript, a mobile binary, desktop client, public repository, URL, or analytics event.

## Recommended first workflow

1. Create a key with `domains:read`, `emails:write`, `emails:read`, and `messages:read`.
2. Call `GET /v1/domains` and select an active domain with creation and receiving enabled.
3. Call `POST /v1/emails` once with a unique `Idempotency-Key`.
4. Store the returned opaque email ID and address.
5. Send mail to that address from the system you are testing.
6. List messages at a conservative interval and stop after a fixed deadline.
7. Fetch only the message body, source, or attachment your workflow needs.

<CardGroup cols={2}>
  <Card title="Run the quickstart" icon="bolt" href="/developer-docs/quickstart">
    Follow a minimal cURL flow.
  </Card>

  <Card title="Review authentication" icon="shield" href="/developer-docs/authentication">
    Choose scopes and handle keys safely.
  </Card>
</CardGroup>

<Note>
  The API never waits in the background for a message. Your integration owns its
  retry cadence, jitter, and final deadline.
</Note>