What suppressions are
Suppressions are rules that block delivery. Common uses:
- Manual blocks (support requests)
- Unsubscribes
- Bounce/complaint-based suppression
Use webhooks to keep suppressions up-to-date
Many teams ingest bounce/complaint webhooks and automatically suppress recipients to protect reputation.
Endpoints
POST Request
Bearer
POST
/v1/suppressionsUpsert suppression entries (JSON) or bulk import (multipart).
GET Request
Bearer
GET
/v1/suppressionsList suppressions (cursor pagination + filters).
GET Request
Bearer
GET
/v1/suppressions/{id}Fetch a single suppression entry.
DELETE Request
Bearer
DELETE
/v1/suppressions/{id}Delete a suppression entry.
Authentication
- Required scope:
manage:suppressions
Upsert (JSON) example
bash
curl -sS -X POST https://api.sendlib.com/v1/suppressions \
-H "Authorization: Bearer $SENDLIB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"items": [
{"identifier":"bounced@example.com","type":"email","reason_category":"manual"}
]
}'List example
bash
curl -sS "https://api.sendlib.com/v1/suppressions?limit=100&type=email" \
-H "Authorization: Bearer $SENDLIB_API_KEY"Next
- Reliable event ingestion: Webhooks
- Pagination patterns: Pagination