Use cases
The transactional emails every app sends
In short
Transactional emails are triggered by something a user did - asking for a code, forgetting a password, placing an order, being billed. Each has its own rules for security and delivery. These guides cover what each email must contain and how to send it reliably with one API call.OTP emails
To send an OTP by email, generate a short random code on your server, store only its hash with an expiry of 5 to 10 minutes, and send it with one API call from a verified domain.
Password reset emails
A password reset email carries a single-use link with a long random token that expires in 15 to 60 minutes.
Order confirmation emails
Send the order confirmation from your payment webhook or order job - not the checkout page - with an Idempotency-Key set to the order id, so retries and duplicate payment events never send two receipts.
Invoice emails
To email an invoice, generate the PDF on your server, base64-encode it and send it as an attachment with content_type application/pdf, alongside a short HTML body with the invoice number, amount and due date.
Send your first email in minutes
6,000 emails a month (up to 200 a day), free forever. No card needed.