How the Email product works
Understand sender identity, acceptance, delivery events, and operational responsibilities.
Email product provides email sending. Enterprise setup begins with sender domains and identity verification, then uses API, SMTP, or console campaigns. Send records and events provide the final outcome.
Acceptance and delivery are separate
Before you begin
- Verify a sender domain and sender address in the console.
- Prepare an API Key, authorized outbound IP, and server-side secret storage.
- Choose marketing or transactional use and define unsubscribe and suppression requirements.
Sending lifecycle
| Stage | What to check |
|---|---|
| Identity | Sender domain, DNS records, sender address, and API Key are ready. |
| Acceptance | Check the version-specific success status; keep the same idempotency key and body for retries. |
| Processing | Templates, routing, quota, suppressions, and channels can affect the result. |
| Outcome | Look up the full Message ID in send records; receive timely events through Webhooks. |
Operations and recovery
Store the idempotency key, request identifier, and Message ID for each business task. Reconcile the original task after a timeout or 5xx; do not resend with a new key. Webhook events are currently attempted once, with no automatic retry or replay. Persist events before processing, deduplicate by eventId, and reconcile against send records. Customers do not currently have a Webhook delivery log or replay control in the console.
FAQ
Why can an accepted request still fail?
Acceptance starts downstream processing. Templates, sender authorization, suppressions, channels, or recipient systems can still cause failure or bounce.
Where should I start?
Use Get started for quick setup, Guides for workflows, and API Reference for exact fields and interactive requests.
Related resources
Last updated on