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.
GitHub Actions
Use the TempInbox API directly from shell steps or JavaScript test runners.Shell (cURL)
.github/workflows/e2e.yml
Node.js test runner
.github/workflows/playwright.yml
GitLab CI
.gitlab-ci.yml
Environment variable pattern
For test frameworks that need the address upfront (before the test runner starts):github-actions step
Rate limit considerations
In CI with many parallel jobs:- Each job should create its own inbox (parallel-safe by design)
- Add 2–3 second delays between poll attempts
- Use a timeout of 60 seconds for staging SMTP (external delivery is slower)
- Do not share inboxes across jobs — race conditions will cause flaky tests
Secrets
Hosted TempInbox is not a supported CI integration. For your own deployment, configure authentication and store required credentials in the CI secret manager. For self-hosted instances withPASSWORDS set, add the password as a CI secret:
Related reading
- Temp Email for Developers: API, CI, Testing — the full developer workflow overview
- Temporary Email for Deliverability Testing — testing what CI can’t catch
- Playwright guide — the test-runner side of these pipelines