DocumentationSending domains
Sending domains
Why to verify your domain before production.
For ISPs to trust your mail, you must send from a verified domain with correct SPF, DKIM, and DMARC records.
Summary flow
POST /domains— add domain (e.g.yourdomain.com)GET /domains/:id/dns— get records to copy- Configure DNS at your provider (Cloudflare, Route53, etc.)
POST /domains/:id/verify— check propagation
Why it matters
| Without verification | With verification |
|---|---|
| Spam / rejection risk | Better reputation and delivery |
| Generic sender | fromEmail with your brand |
| No own DKIM signature | Messages signed with your domain |
Sender in the API
When sending, you can optionally set:
{
"fromEmail": "[email protected]",
"fromName": "Your Product",
"replyTo": "[email protected]"
}
The domain of fromEmail must be verified in the tenant.
Next steps
- Configure DNS — SPF, DKIM, DMARC records
- Verify domain — check status