---
title: "Suppressions"
description: "Address-level send blocks — the hard \"never email this address\" list. Combines engine-written bounce/complaint entries, your own additions, and read-only Unitpost-wide blocks."
url: https://www.unitpost.com/docs/api/suppressions
section: API reference
updated: 2026-07-31
---
# Suppressions

## Suppressions

> Address-level send blocks — the hard "never email this address" list. Combines engine-written bounce/complaint entries, your own additions, and read-only Unitpost-wide blocks.

Full schemas: [OpenAPI 3.1](https://www.unitpost.com/api/v1/openapi.json). HTML reference: https://www.unitpost.com/docs/api/suppressions.

## Operations

### `GET /api/v1/suppressions`

List suppressed addresses

Retrieve a list of email addresses that are blocked from receiving your mail, newest-first and cursor-paginated. The list includes your workspace's own suppressions AND the read-only Unitpost-wide (`platform`) entries that would block a send — so it's the complete answer to "why isn't this address getting mail?". Pass `?scope=workspace` to hide platform rows. Add an address with [Suppress an address](#post-suppressions) or lift a block with [Un-suppress an address](#delete-suppressions-id). Requires the `suppressions:read` capability.

### `POST /api/v1/suppressions`

Suppress an address

Block one address (`{ email }`) or up to 1,000 at once (`{ emails: [...] }`) from receiving any future sends from your workspace. The operation is idempotent — re-suppressing an existing address returns `200` rather than a conflict. The bulk form returns an `{ object: "list", added, skipped, total }` summary. Suppression is the hard stop; to let recipients opt out of just one kind of email, use topics (see [Create a topic](#post-email-topics)). Undo with [Un-suppress an address](#delete-suppressions-id). Requires the `suppressions:write` capability.

### `GET /api/v1/suppressions/{id}`

Retrieve a suppressed address

Retrieve one suppression by id (`supp_…`) or by the email address itself. Returns your own workspace row, or a read-only `platform` row when the address is blocked Unitpost-wide. Lift a workspace block with [Un-suppress an address](#delete-suppressions-id). Requires the `suppressions:read` capability.

### `DELETE /api/v1/suppressions/{id}`

Un-suppress an address

Remove a workspace suppression by id or email so the address can receive your mail again. The email form is idempotent — removing an address that isn't suppressed still returns `204`. Unitpost-wide (`platform`) entries can't be removed here (`403`) — contact support. Check what's blocking an address first with [Retrieve a suppressed address](#get-suppressions-id). Requires the `suppressions:write` capability.

## Related

- [Usage](https://www.unitpost.com/docs/api/usage): Your workspace's current billing-period usage: emails sent, and on paid plans the dollar sending wallet (monthly allowance, spend, purchased credit, overage) in integer USD cents.
- [Emails](https://www.unitpost.com/docs/api/emails): Send, schedule, retrieve, and cancel transactional email. Send one email or a batch of up to 100, track each message's delivery lifecycle, and pull aggregate deliverability stats for your workspace.
- [Inbound emails](https://www.unitpost.com/docs/api/inbound-emails): Read email your receiving-enabled domains have received — list messages, retrieve full bodies, and download attachments via short-lived signed URLs.