Prerequisites
Before you begin, you need:- A Dugble account and team
- A team token with the
email:sendpermission - A configured and verified sender domain, or a configured default sender
curlor another HTTP client
Keep team tokens on your server. Never expose them in browser or mobile application code.
1. Store your team token
2. Send an email
Use a unique idempotency key for every logical send. Reusing the same key for a retry prevents the same logical request from being processed twice.202 Accepted with the Dugble message ID:
202 Accepted means Dugble accepted the message for asynchronous delivery. It does not mean the recipient’s mail server has delivered it.
3. Check delivery status
Use the returned message ID:last_event. The lifecycle can include queued, processing, submitted, delivered, delayed, bounced, complained, rejected, failed, or canceled.
Next steps
Learn about recipients, content, scheduling, batches, headers, and delivery status.
Authentication
Learn how team tokens and permissions protect API requests.
SMS
Send transactional SMS using the same team-token model.
Sender domains
Configure and authenticate the domains used for outbound email.