---
title: "Suppress an address"
method: POST
path: "/api/v1/suppression"
tags: ["Suppression"]
---

# Suppress an address

`POST /api/v1/suppression`

## Request

- Base URL: `https://mailcheer.com`
- URL: `https://mailcheer.com/api/v1/suppression`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Api-Key`

Permission required: `subscribers:write`. The matching subscriber, if there is one, moves to `unsubscribed` in the same operation. Without `reason`, the entry is `manual` and refuses everything, individual emails included; `unsubscribe` only refuses campaigns, automations and sends carrying `unsubscribe_url`. An entry already `bounce`, `complaint` or `manual` is never downgraded to `unsubscribe`.

**No endpoint removes an address from this list**, and that is deliberate: it is the one action that suspends a sending capability. It is done by hand, in your Mailcheer workspace.

## Request body

- object
  - `email` string, email, required
  - `reason` 'unsubscribe' | 'bounce' | 'complaint' | 'manual'

## Response `201`

Suppressed.

- Suppression
  - `object` 'suppression'
  - `email` string
  - `reason` 'unsubscribe' | 'bounce' | 'complaint' | 'manual'
  - `scope` 'organization' | 'platform'
  - `created_at` string, date-time

## Other responses

- `401`: Key missing, unknown or revoked.
- `403`: The key does not have the requested permission, or the workspace cannot send: `sending_blocked` (suspended, blocked or banned — nothing goes out, through any channel), `commitment_required` (the anti-spam commitment is not accepted), `reputation_blocked` (too many bounces or complaints).
- `422`: Malformed field, unverified domain, or recipient on the suppression list.

---

[API](https://skmtc.dev/mailcheer/apis/mailcheer-api.md) · [All operations](https://skmtc.dev/mailcheer/apis/mailcheer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mailcheer/apis/mailcheer-api/revisions/ba64b7ef2170?raw)