®
Transactional Email Journey
This path is for teams sending password resets, receipts, verification emails, login links, order confirmations, and required account notices.
Goal
By the end, your application can send necessary account emails through Bento without exposing API keys, sending duplicates, or hurting deliverability.
Do not use transactional email for marketing campaigns. Use broadcasts, workflows, and consent-aware marketing paths instead.
Recommended Path
- Read Transactional Email Operations.
- Set up sender authentication with DNS Setup.
- Pick an SDK or use the Emails API.
- Confirm your
fromaddress is an author in Bento. - Implement sends server-side only.
- Rate limit every user-facing action that can send an email.
- Test with real inboxes and inspect the profile activity timeline.
If you are unsure which SDK fits your stack, start with All SDKs, then read that SDK's GitHub README before implementation.
Production Checklist
- API keys are stored server-side.
- Sender authentication is valid.
- Password reset, login, invite, and signup endpoints are rate limited.
- Retries cannot send duplicate messages.
- Templates avoid user-controlled HTML and URL shorteners.
- Support knows how to inspect bounces and failed sends.