TMTEMPMAILpublic otp receiver
HOMEPUBLIC GMAILSBLOGTOOLSABOUT
Emails are publicly visible & automatically wiped out permanently every 5 minutes. Not affiliated with Google LLC.

live imap engine free tool · no signup

Real Gmail IMAP Inbox for QA & API Testing DEV & QA

A real IMAP mailbox as a service — built for engineers, testers and bots.

Sending test emails is easy; receiving them in automation is the painful half. QA suites, E2E runners, and OTP-flows cruncher all face the same wall: you need a real mailbox that your pipeline can read programmatically without brittle POP3 polling or personal-account gymnastics.

This page turns that pain into a one-line problem. Every public Gmail here is a genuine IMAP inbox. Your test or API client can poll the live feed every few seconds, parse the OTP via the JSON payload, and stay green — while a 5-minute auto-purge keeps the mailbox from growing without bound.

LIVEnext purge 05:00
selected

The OTP testing architecture that works

The pattern is simple: your E2E test signs up with a temp Gmail, then reads `GET /api/mail?gmail=...` until the OTP appears, extracts `extractedOtp` from the JSON, and feeds it into the forms under test. No IMAP credentials, no MIME parsing, no flaky folders.

For even lower latency, subscribe to the SSE endpoint and get pushed the instant a message lands. Combined with the REST fallback, you get a deterministic, self-cleaning test dependency.

Why real Gmail matters for testing

Staging and sandbox environments often use catch-all mailers that do not behave like production. Real Gmail accounts reproduce authentic deliverability — DKIM-signed newsletters, HTML previews, quoted-printable bodies — so your tests validate the formats your users actually receive.

The sanitized HTML and plain-text fields in the API response mirror what a production parser would see, making assertions meaningful.

Rate limits and responsible automation

Public inboxes are shared infrastructure, so keep test volume reasonable — the API rate limiter enforces that. For high-throughput CI or commercial pipelines, add dedicated Gmail accounts through the admin panel so your automation owns its own mailbox and never competes for attention.

Quick answers, no fluff

Yes. Use the JSON REST endpoint or SSE stream. The payload includes sender, subject, bodyText, and a regex-extracted OTP field designed for exactly this.