---
title: "List suppressed addresses"
description: "The addresses this workspace will not send to, newest first."
url: "https://openemail.uk/docs/api/suppressions/list"
area: "API"
category: "Mailbox"
---

# List suppressed addresses

The addresses this workspace will not send to, newest first.

`GET /suppressions`

## GET /suppressions

The addresses this workspace will not send to, newest first.

## Example

Needs `settings:read`, the scope the Blocked addresses screen in Settings is gated on. `q` searches the address, the reason and the detail, `reason` keeps one kind, and `limit` and `cursor` page it.

**curl**

```
curl "$OE/suppressions?reason=complaint" -H "$AUTH"
```

**Response**

```
{
  "object": "list",
  "data": [{
      "object": "suppression",
      "id": "7b1e2c3d-4f5a-4b6c-8d7e-9f0a1b2c3d4e",
      "email": "ada@example.com",
      "reason": "complaint",
      "detail": "abuse",
      "removable": true,
      "createdAt": "2026-09-12T08:41:03.000Z"
    }],
  "hasMore": false,
  "nextCursor": null
}
```

> A send to a suppressed address is refused for that recipient before anything leaves, and a message whose recipients are all suppressed fails outright. A hard bounce or a complaint puts an address here on its own.

> The list belongs to the whole workspace, so a key limited to particular addresses or domains reads all of it. A row names the recipient and never which of your addresses sent to it.