Suppressions

Suppressions prevent emails from being sent to addresses that have previously bounced, complained, or unsubscribed. This protects your sender reputation and helps you comply with anti-spam regulations.

---

How suppressions work

When an email event occurs, Emitlo automatically adds the recipient to your suppression list:

Event	Action
Hard bounce	Address added with reason hard_bounce
Spam complaint	Address added with reason complaint
Unsubscribe click	Address added with reason unsubscribe

Any future send attempt to a suppressed address is silently skipped — the API returns 202 Accepted but the message is not delivered. In batch sends, suppressed addresses appear in the suppressed array of the response.

---

Viewing suppressions

Go to Dashboard → Suppressions to view and manage your suppression list.

Or use the Suppressions API.

---

Removing a suppression

Caution

Only remove a suppression if you have explicit confirmation that the recipient wants to receive emails again (e.g. they re-subscribed via a confirmed opt-in flow). Sending to hard-bounced or complaining addresses damages your sender reputation.

You can remove a suppression from the dashboard or via the API:

curl -X DELETE https://api.emitlo.com/api/v1/suppressions/1 \
  -H "Authorization: Bearer YOUR_API_KEY"

---

Manually adding suppressions

You can manually add addresses to the suppression list — useful for honoring opt-out requests received outside of Emitlo (e.g. via a support ticket):

curl -X POST https://api.emitlo.com/api/v1/suppressions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "email": "optout@example.com", "reason": "manual" }'

---

Suppression reasons

Reason	Description
hard_bounce	Permanent delivery failure (invalid address, domain doesn’t exist)
complaint	Recipient marked the email as spam
unsubscribe	Recipient clicked the unsubscribe link
manual	Manually added via dashboard or API