Guides
Guides
Practical guides for sending email well: testing an integration without a sandbox, splitting marketing and transactional sending domains, and porting templates from another provider.
These answer tasks rather than endpoints. For the contract of a single call, read the API reference; for what a capability is and why it works the way it does, read the feature pages.
- GuideTesting your email integrationThere is no sandbox mode, so the honest answer is a set of addresses that exercise the real pipeline. That includes the branch most integrations never test: the one where we refuse to send.Read the guide
- DeliverabilitySeparate subdomains for marketing and transactional mailAt real volume, marketing and transactional mail want separate subdomains so that receivers score them separately. At low volume, splitting makes both worse. Here is where the line sits and how to cross it safely.Read the guide
- MigrationBringing templates over from another providerMost template HTML ports across unchanged. The parts that do not are the parts the old provider was quietly adding or rewriting for you, and they fail in ways that look like your template is fine.Read the guide
Private beta
The guides assume an account, and accounts are invite-only
Join the list and your onboarding email carries a scoped API key, so the recipes here run rather than read.