TempMailGrab Integrations

Use TempMailGrab as a manual disposable inbox, or plug it into a developer workflow. This hub connects every integration path that helps teams test signup, OTP, password reset, and email verification flows.

Developer integration map

Integration	Best for	Canonical guide
OpenAPI / Postman	Exploring endpoints and sharing API collections.	Postman import guide
Playwright	Browser tests that create accounts and verify OTPs.	Playwright API guide
Cypress	End-to-end specs with polling and CI secrets.	Cypress API guide
Webhooks	Push-based email delivery instead of polling.	API docs
Private domains	Team-owned disposable inbox domains for QA.	Private domains
JavaScript SDK	Typed inboxes, OTP waiters, retries, and fixtures.	SDK section

Recommended CI pattern

Create a TempMailGrab API key from the dashboard.
Store it as a CI secret named TMG_API_KEY.
Create one inbox per test or per parallel worker.
Submit the generated address inside the signup or reset flow.
Read extracted_otp or extracted_links from the API response.
Delete the inbox in teardown when tests generate heavy mail or attachments.

Manual workflow integrations

Chrome extension for toolbar access and autofill.
Firefox add-on for privacy-focused desktop browsing.
Android app for phone-first OTP handling.
iPhone web app for Safari/Home Screen use.

Last verified: August 2026. Integration examples are intentionally narrow: one inbox per test, structured OTP fields, and clear teardown behavior.

Frequently Asked Questions

What is the best TempMailGrab integration for developers?

Start with the OpenAPI spec or Postman import guide, then use the Playwright or Cypress guide if your workflow is browser-based.

Should tests share one temporary inbox?

No. Create one inbox per test or per parallel worker so OTPs and verification links do not cross between runs.

Can webhooks replace polling?

Yes. Register a webhook to receive parsed message payloads, including extracted OTP and links, when mail arrives.