Skip to Content
Docs
Guides

Suppressions

The per-tenant do-not-send list — how sends get blocked, and how to manage the list.

If a recipient is on your suppression list, the send returns 200 with { "status": "suppressed" } and no message is sent — protecting your sender reputation and your bill. Suppression is checked after validation and before the queue, and the consumed quota unit is refunded.

How entries get there

SourceReasonWho sets it
Hard bounce eventhard_bounceevents pipeline (automatic)
Complaint (spam report)complaintevents pipeline (manual or automatic)
Unsubscribe / preference centreunsubscribeevents pipeline
Manual / APImanualyou

The events pipeline owns the verified reasons; anything added through the API is always stored as manual (a reason you send is accepted but ignored).

Managing the list

In the console: open Suppressions to see every blocked address with a count per reason. From there you can:

  • Check address — see instantly whether emitd will deliver to an address.
  • Suppress address — block one address until you remove it.
  • Import — paste addresses or upload a CSV (one per line, or comma-separated) to block many at once.
  • Export CSV — download the list.

The Suppressions page in the emitd console, with counts per reason and Check address, Import, and Suppress address buttons

Over the API:

EndpointPurpose
GET /v1/suppressionsList, newest first (?limit=, ?cursor=)
POST /v1/suppressionsAdd one (upsert on (tenant_id, email))
POST /v1/suppressions/bulkAdd up to 100 at once
DELETE /v1/suppressions/bulkRemove up to 100 at once
DELETE /v1/suppressions/{email}Remove one (always 200 { "deleted": true })
POST /v1/suppressions
{ "email": "ada@lovelace.io" }
201 Created
{ "email": "ada@lovelace.io", "reason": "manual" }

Suppressed ≠ error

A suppressed recipient is a 200, not a 4xx — your integration should treat it as a normal outcome. Batch sends report it per message as status: "suppressed".

Removing an entry

DELETE /v1/suppressions/{email} lifts the block. Do this only when the recipient asks to hear from you again — removing hard bounces and complaints without consent puts your domain reputation back at risk.

How recipients suppress themselves

Most entries arrive without an API call: a recipient clicking the unsubscribe link, or their mail client's one-click button, adds the address here directly. See Unsubscribe & tracking — including the hosted preference center, which lets someone opt out of one topic instead of everything.

On this page