Suppressions

When a recipient hard-bounces, complains, or is blocked by their provider, the address is suppressed automatically — future sends to it fail fast with 409 recipient_suppressed instead of damaging your reputation. Unlike Resend, the whole list is manageable over the API.

List

GET/api/v1/suppressions?email=

curl "https://www.noticeapi.com/api/v1/suppressions" \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx"

Add (pre-emptive block)

POST/api/v1/suppressions

Block an address before you ever send to it — deleted users, legal requests, known traps.

curl -X POST https://www.noticeapi.com/api/v1/suppressions \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{ "email": "[email protected]", "reason": "user requested" }'

Remove (unsuppress)

DELETE/api/v1/suppressions?email=

Use when a recipient fixed their mailbox. Removing a complaint-based suppression re-exposes you to their spam button — do it only when you're sure.

curl -X DELETE "https://www.noticeapi.com/api/v1/[email protected]" \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx"