Transactional email.
Send email from your backend and see what became of each one. Once you go live, it leaves from a domain you verify.
What you get.
From your own domain.
Once you go live, your app’s email leaves from a domain you verify, not from ours.
Every message followed.
The console lists the mail your app sent, each with where it got to: queued, delivered or bounced.
Bounces and spam reports stop mail.
Stop mail to any address. One that reports your mail as spam joins the list on its own.
One email, start to finish.
Open a message for its timeline, with the time of each step. A delivery webhook tells your backend the same, without polling.
To helena.brandt@example.com · from noreply@acme.example
- QueuedOct 23, 02:18 PM
- AcceptedOct 23, 02:18 PM
- DeliveredOct 23, 02:18 PM
Questions.
Can I send before I go live?
Yes, to the members of your workspace: build mode sends up to 10 a day and 50 in total, from a separate build sender. Once you go live, your app’s email leaves from a domain you verify, to anyone.
Does Sandbox send real email?
Once you go live, yes: Sandbox sends as Production does, so a Sandbox send reaches a real inbox. Test with addresses you own.
Can an email be sent twice?
No. The same idempotency key sent again answers the same message and sends nothing twice.