Skip to main content
The hosted TempInbox service has no supported public automation API. These implementation examples are for an instance you operate and must be checked against its deployed version, authentication, inbound mail routing, and rate limits. Do not export hosted browser access tokens for CI. For hosted manual use, see QA workflows.

Pattern

Puppeteer drives the browser; plain fetch (Node 18+) talks to the TempInbox API. Zero dependencies beyond Puppeteer itself. If you’re choosing a framework today, see the Playwright guide — the API integration is identical.

Helper

Reuse the zero-dependency Node client from API Client Snippets — createInbox(), waitForMail(), extractOtp().
For automation, configure and use your own instance. Hosted browser access tokens are not a supported integration credential.

Example: OTP signup (Jest + Puppeteer)

signup.test.mjs


Tips

  • Poll the API, never scrape the TempInbox UI with Puppeteer — faster and flake-free
  • One inbox per test — parallel Jest workers never collide
  • 2–3s poll interval, 60s timeout in CI — list responses cached up to 60s at offset=0