Temp Mail API Early Access
TempMy is evaluating API access for development and QA teams that need temporary inbox workflows. Public API access is not generally available from this page today, but you can register interest and describe your use case.
Who this is for
- QA teams testing account verification and transactional email flows
- Developers who need repeatable temporary inboxes during staging tests
- Product teams validating onboarding emails without using personal addresses
Current status
This is an early-access funnel, not a public API launch. Access, limits, pricing, and endpoint behavior may change while the workflow is evaluated.
Good-fit use cases
- Manual or semi-automated QA in staging environments
- Checking whether signup and passwordless login emails render correctly
- Keeping disposable test signups separate from team inboxes
Not for sensitive workflows
Do not use temporary inboxes for banking, government, medical, legal, production customer data, paid accounts, crypto, or any account that needs durable recovery.
Related pages
FAQ
Is the TempMy API publicly available?
Not from this page today. This page collects early-access interest for development and QA use cases.
Can I use it for production customer data?
No. Temporary inbox workflows are best kept to low-risk testing and QA.
How do I request access?
Use the contact link and describe your testing workflow, expected volume, and whether the use case is staging or production.
Will API access make delivery certain?
No. Email delivery depends on the sending service and mail routing, and some services block disposable domains.