Temp mail for developers — automating email-driven signup tests
Developer use cases for disposable mail are different: automated tests, signup-flow validation, OTP plumbing. PocketInbox aggregates the major APIs; here's the playbook.
Cypress / Playwright signup flows
Generate one inbox per test in beforeEach. Use a polling helper to wait for the verification mail. Filter by subject regex. Parameterise with the upstream provider so flaky-providers fail one test, not all of them.
OTP plumbing
For 6-digit OTPs, anchor the regex on a keyword (/code[\s:]+(\d{6})/i) — don't match raw 6-digit numbers (you'll catch transaction IDs).
Read the full developer guide
We wrote a 2,500-word developer-focused post with full code samples. See the related guide below.
FAQ
- Does PocketInbox have a public API?
- PocketInbox is primarily a UI; the upstream providers we proxy each have their own APIs. For programmatic access, hit Mail.tm or TempMail.lol directly.
- What's the rate limit?
- Provider-dependent. Mail.tm shares 8 QPS across all users behind one IP. Cap concurrent test workers at 4-6 against any single provider; alternate providers across shards.