Email suppressions API

Email Suppressions API That Protects Sender Reputation

NoticeAPI suppressions stop known-bad recipients before another send can hurt your domain. Hard bounces, complaints, provider blocks, manual opt-outs, and broadcast unsubscribes feed the same safety layer.

Start free Read suppressions docs

Pricing Features Docs

Manage suppressions over REST

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

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" }'

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

Automatic bounce protection

Hard bounces and spam complaints suppress the recipient automatically across future sends.

Full REST control

List suppressions, add pre-emptive blocks, or remove a suppression when a recipient fixes their mailbox.

Fail-fast sends

Suppressed recipients return recipient_suppressed instead of creating another provider send.

Shared with broadcasts

Unsubscribes and suppressions are respected by broadcast and automation sends.

How it works

From test send to production traffic.

Let events auto-suppress

Bounces and complaints from provider events become suppressions without manual cleanup.

Add manual blocks

Use POST /api/v1/suppressions for legal requests, deleted users, or addresses you should never contact.

Check before retrying

A suppressed recipient fails fast with recipient_suppressed, making retry behavior predictable.

Unsuppress carefully

Remove a suppression only when you know the recipient is safe to contact again.

Trust

Suppressions are a safety system, not a growth loophole

NoticeAPI does not provide a bypass for suppressions or unsubscribes. The API exists so your product can respect recipient state and keep sender reputation intact.

Implementation links

Build with the shipped docs.

Suppressions docsList, add, and remove suppressed recipients.Broadcast docsSee how unsubscribe and suppression state affects sends.WebhooksReceive the events that create suppressions.Acceptable useConsent and abuse rules for the platform.

FAQ

Questions developers ask before switching email.

Can I bypass a suppression for a transactional send?

No. Suppressions are enforced before sending so known-bad recipients do not keep hurting your sender reputation.

Are simulated bounces suppressed?

No. Simulator bounces are repeatable test outcomes and do not suppress the simulator address.

When should I remove a suppression?

Only when you have a clear reason, such as a recipient fixing their mailbox or asking to receive email again.

Start free. Send production after your domain is ready.

Free includes 3,000 production emails per month, a 100/day production cap, and one verified sending domain.

Create your account Compare plans