Test the email your application sends
A receive-only email testing API for developers, CI pipelines and QA teams. Create a real inbox in one call, trigger your signup or reset flow, wait for the message, assert on it.
Free tier: 100 inbox tests a month, no credit card.
What a test looks like
# 1. A fresh inbox for this test run
curl -X POST https://inboxdome.com/v1/inboxes \
-H "Authorization: Bearer $INBOXDOME_KEY"
# → { "inbox": { "id": "inb_…", "emailAddress": "qa-1b7f@mailoca.com" } }
# 2. Your app sends its signup mail to that address…
# 3. Block until it arrives and extract the OTP (no sleep(), no flakiness)
curl "https://inboxdome.com/v1/inboxes/$INBOX_ID/wait?for=otp&timeoutSeconds=30" \
-H "Authorization: Bearer $INBOXDOME_KEY"
# → { "otp": { "value": "482913" } }Full flows in the Playwright,Cypress andGitHub Actions guides, or theOpenAPI spec.
Everything a test suite needs from email
Inboxes on demand
POST /v1/inboxes returns a working address in one call. One inbox per test, isolated, auto-expiring. No mailbox setup, no IMAP.
Wait for the mail, not for a sleep()
Long-poll an inbox until the message lands. Extract OTP codes and verification links directly, with a timeout instead of a flaky fixed delay.
Assertions and scenarios
Declarative checks on delivery, subject, content, links and SPF/DKIM/DMARC results. Chain steps into multi-stage scenarios that run server-side.
Signed webhooks
Push new-message events to your own systems. Every payload is signed, with replay protection, so your receiver can trust what it gets.
SDKs, CLI and GitHub Action
JavaScript and Python SDKs, a CLI for local runs, a GitHub Action for CI, guides for Playwright and Cypress. Or just use the OpenAPI spec.
MCP server for AI agents
Claude and other MCP clients can create inboxes, wait for mail and assert on it as native tools, so an agent can test a signup flow end to end.
Domains built for clean test runs
Free keys use the shared public pool, which also serves the free demo inbox. Paid plans add a private pool: dedicated testing domains reserved for registered API customers and isolated from all anonymous traffic, so your test environment stays predictable. From Pro upward you can also bring your own domain and receive test mail on infrastructure whose reputation is entirely yours.
Built for testing, and only for testing
InboxDome is for testing the email flows of applications you own or are authorized to test. It is receive-only: nothing can be sent from an InboxDome address, ever. Using it to create accounts on third-party services, bypass OTP or verification checks, farm accounts or evade bans is prohibited, enforced and grounds for termination under ourAcceptable Use Policy. Paid API access requires a registered account.
Start with the free tier
100 inbox tests a month, every capability included, upgrade only when volume demands it.