Skip to main content

How suppressions work

When a recipient’s mail server permanently rejects an email (hard bounce) or the recipient marks your email as spam, their address is automatically added to your suppression list. Future sends to suppressed addresses are automatically skipped — the API returns 422 recipient_suppressed instead of queueing the email. This protects your sender reputation and ensures compliance.

Suppression reasons

Only manual and unsubscribe suppressions can be removed via the API. Bounce and complaint suppressions are permanent to protect your reputation.

List suppressions

Query parameters

Response


Check if an address is suppressed

Check a specific email address before sending:

Response (suppressed)

Response (not suppressed)


Add a manual suppression

Manually suppress an address (e.g. a customer requests to stop receiving emails):

Response — 201 Created


Remove a suppression

Remove a manual or unsubscribe suppression by email address:
The email address in the URL must be URL-encoded (e.g. @ becomes %40).

Response — 200 OK

You cannot remove hard_bounce, soft_bounce, spam_complaint, or blocklist suppressions. Attempting to do so returns 422.