Skip to main content
Four steps. Everything on this page is copy-paste runnable.
1

Get a free key

No signup, no email required. The key is shown once and is not recoverable.
Read endpoints work with no key at all — you can skip this step and still call the API. A key raises your limits 5-10× and unlocks long-polling, which is the feature you actually want. See Authentication.
2

Generate an inbox

Nothing is provisioned server-side — an address starts receiving the moment it exists. GET /api/v1/domains lists the domains that accept mail.
3

Wait for mail to arrive

Pass wait and the server holds the connection until mail lands, up to 30 seconds. No polling loop.
Set your HTTP client’s timeout above your wait value, or your own client will hang up before the server answers.
4

Read the full body

The list endpoint returns summaries without bodies. Fetch one email for the text and HTML parts plus attachment metadata.

A complete verification-code flow

This is the shape almost every integration ends up with: create an inbox, drive your own signup, block until the mail arrives, pull the code out.
The loop above is not a polling loop in disguise. Each iteration blocks server-side for up to 30 seconds, so a 60-second budget costs you two requests, not sixty. The reason it loops at all is to survive a wait that times out with nothing to report. Read the cursor contract before adapting it.