Suppressions
Recipients that should never be sent to. Auto-populated by bounces and complaints. Per-tenant.
Suppression reasons
bounce— recipient mailbox doesn't exist or rejected hard.complaint— recipient marked the email as spam.unsubscribe— recipient clicked the List-Unsubscribe link or unsubscribed in-app.manual— you added them via the API or admin tool.
List suppressed addresses
GET /api/suppressions
Scopes: events:read
Add to suppression list
POST /api/suppressions
{
"email": "user@example.com",
"reason": "manual"
}Remove from suppression list
DELETE /api/suppressions/:email
How suppressions affect sends
The send path consults suppressions before contacting SES. If any recipient is suppressed it's silently dropped; if all recipients are suppressed the response is:
{
"success": true,
"data": {
"messageId": "suppressed",
"status": "suppressed",
"to": ["user@example.com"]
}
}No SES call is made, so suppressed sends don't count toward your bill.