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.
Ready-to-use client helpers for the three most common automation environments. All of them implement the same three operations:
  1. Create inbox — POST /api/new_address → { address, jwt }
  2. Wait for mail — poll GET /api/mails?limit=1&offset=0, then fetch GET /api/mail/:uuid
  3. Extract content — OTP codes or links from the raw body
For automation, configure and use your own instance. Hosted browser access tokens are not a supported integration credential.

Python

tempinbox.py
usage.py

Node.js

Zero dependencies — uses the built-in fetch (Node 18+).
tempinbox.mjs
usage.mjs

Shell (cURL + jq)

For CI steps and quick one-offs:
tempinbox.sh

Polling guidelines

These apply to every client above: