Temp Mail Ace
Temporary email API for developers
Test incoming email from systems you control with an authorized temporary inbox. Review the developer guide and your eligible API access before connecting a test workflow.
Built around the way you receive email
Test actual incoming messages
Send a test message from your own application to an authorized inbox. Check whether it arrived before validating content, codes or links.
Access with a defined scope
Use the documented endpoints and the permissions granted to your key. Confirm inbox eligibility, key expiry and current limits in the developer workspace.
Handle delivery and expiry separately
An expired inbox, denied request and delayed message are different outcomes. Design your checks around the documented responses and avoid logging keys or message secrets.
Temp Mail Ace
From choosing a source to receiving a message
Read the developer guide, then sign in to check API availability, key scopes and eligible inbox access.
Trigger a message from your own test system to an authorized inbox using the documented workflow.
Check the response and message arrival, handling access expiry and delivery delays separately.
Read the practical guides
Questions before you start
Where are the API instructions and access settings?
Start with the developer guide for the documented workflow. The developer workspace requires appropriate account access and shows the API capabilities available to you.
Does this API send emails or provide unrestricted mailbox access?
The service supports receiving workflows within the permissions granted to your account and key. Use authorized test inboxes and the documented operations.
Temporary email API for developers
Use your own authorized test systems and follow current key scopes, permissions and limits.