Suppressions API

Suppressions are account-level recipient state. When a provider reports a hard bounce, spam complaint, quarantine, or provider suppression, NoticeAPI stores a suppression record; future sends to that address fail fast with 409 recipient_suppressed before provider handoff.

Use the API to list records, add a manual block, or remove a suppression after support review.

For the product overview, read the email suppressions API guide.

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 another send reaches the provider, including deleted users, support requests, and addresses your product should not contact.

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 or clearly asked to receive email again. Removing a complaint-based suppression should be a deliberate support decision.

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