Suppressions prevent you from emailing addresses that bounced, complained, or opted out.
How suppressions are created
| Source | Trigger |
|---|---|
| Automatic | Hard bounce or spam complaint from the delivery stack |
| Manual | Dashboard or API add |
| Unsubscribe | Recipient clicks one-click unsubscribe (Unsubscribe link) |
Step-by-step
1. Check before bulk sends
If you maintain a local copy of suppressions, sync via webhooks on bounce/complaint/unsubscribe events.
2. Attempted send to suppressed address
POST /emails to a suppressed recipient is rejected before queueing—you get an error instead of wasting quota.
3. Manage the list
Use the dashboard or REST API to list and remove suppressions. See the full Suppressions guide for API scopes and endpoints.
4. Do not remove complaint suppressions lightly
Removing complaint suppressions without explicit user consent can harm deliverability and violate provider policies.