Transactional Email Best Practices
Foundational decisions for authentication, suppression, and content quality.
Read guideStep 1
Configure SPF and DKIM records once. After verification, your domain is ready for sending.
Step 2
Call POST /api/v1/message with your API key and message payload from any backend stack.
Step 3
Receive delivery, bounce, and engagement webhooks to keep user state and suppression lists accurate.
Create a domain and API key, then start sending transactional emails in minutes.
Built with queueing, retries, and event visibility so critical messages continue flowing.
Process delivery, bounce, and open events with signed payloads for safer automation.
Infrastructure optimized for worldwide delivery to major mailbox providers.
Inspect message outcomes and monitor delivery performance as usage grows.
Predictable pricing with clear limits and no hidden platform fees.
Password resets, magic links, and one-time login codes.
Order confirmations, invoices, shipping updates, and receipts.
Account alerts, security warnings, and workflow status updates.
You'll be billed at the overuse rate for your tier. You can also disable overages per domain and sending will pause when the limit is reached.
No. Quotas reset each month. You can upgrade anytime if your usage increases.
Yes. Plan changes are immediate and your domains, keys, and event history stay available.
Yes. See the API docs for field formats and size limits.
No. Sendwich manages the underlying infrastructure so you can focus on application logic.
Use your API key as a Bearer token in the Authorization header. See the API docs for examples.
Foundational decisions for authentication, suppression, and content quality.
Read guideA practical list for launch readiness and ongoing account health.
Read guideFollow practical send examples for Laravel, PHP, Node.js, and Ruby.
Read guidesCreate your account and start sending transactional emails.