Suppressions

The suppression list holds every address the workspace will not email: no campaign, sequence, automation or one-off send reaches it. Reading needs the read:suppressions scope; adding and removing need write:suppressions (or * for both).

The Suppression object

GET /api/v1/suppressions

Newest first, cursor-paginated.

{
  "suppressions": [
    { "id": "cmq8supp0alk34567890", "email": "ann@example.com", "reason": "UNSUBSCRIBE", "removable": true, "createdAt": "2026-09-27T14:02:00.000Z" }
  ],
  "nextCursor": null
}

POST /api/v1/suppressions

Records a manual opt-out and marks any contact with that address as opted out.

POST /api/v1/suppressions HTTP/1.1
Host: agentlyleads.com
Authorization: Bearer alk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Content-Type: application/json

{ "email": "ann@example.com" }

Returns 201 with { "suppression": { ... }, "created": true }. Sending an address that is already listed is safe: it returns 200 with "created": false, and the entry keeps its original reason, so a bounce stays a bounce.

DELETE /api/v1/suppressions/{id}

Removes the entry and makes the address contactable again, clearing the opt-out flags on matching contacts.

{ "deleted": 1, "id": "cmq8supp0alk34567890", "email": "ann@example.com" }

A hard bounce or spam complaint can't be removed through the API. Those come from the receiving mail server or the recipient, and mailing them again hurts your sending reputation. The API returns 409:

{ "error": "b@example.com is suppressed because of a hard bounce. That can only be removed by a person in Settings, Suppressions." }

Errors