Skip to content

Search documentation

Search pages and sections

API reference

Suppressions

The addresses Hulaki will not send to — bounces, complaints, unsubscribes and manual entries — and how to manage them.

How suppression works

Before every send, each recipient is checked against your workspace’s suppression list. Suppressed recipients are skipped and the email is recorded with status suppressed (an email.suppressed webhook fires). Addresses are added automatically:

ReasonAdded when
bounceA hard (permanent) bounce — the mailbox doesn’t exist or the domain rejects mail
complaintThe recipient marks your email as spam
unsubscribeThe recipient unsubscribes from a campaign or via List-Unsubscribe
manualYou add the address in the dashboard or via the API

Soft bounces (full mailbox, temporary errors) are retried and do not suppress the address.

List suppressions

GET/api/v1/suppressionsscope: contacts:read

Query parameters

reasonstring
bounce, complaint, unsubscribe or manual.
emailstring
Find a specific address.
page / per_pageinteger
Pagination.
{
  "data": [
    { "id": "sup_01JD…", "email": "[email protected]", "reason": "bounce", "created_at": "2026-11-14T09:30:14Z" }
  ],
  "meta": { "current_page": 1, "last_page": 1, "per_page": 25, "total": 1 }
}

Add a suppression

POST/api/v1/suppressionsscope: contacts:write
emailstringrequired
The address to stop sending to.
reasonstring
Defaults to manual.

Remove a suppression

DELETE/api/v1/suppressions/{email_or_id}scope: contacts:write

Only remove an address if you are sure the problem is fixed — for example, the recipient asked to be re-subscribed or a typo was corrected. Re-mailing complainers damages your reputation, and removing complaint entries may be restricted.

Something unclear or missing? Tell us.