---
title: "Suppress an email address"
method: POST
path: "/v1/email-suppressions"
tags: ["Email Suppressions"]
---

# Suppress an email address

`POST /v1/email-suppressions`

## Request

- Base URL: `https://api.honkio.ca`
- URL: `https://api.honkio.ca/v1/email-suppressions`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Adds the address to the suppression list with the reason `manual`. A send to a suppressed address is refused with `EMAIL_SUPPRESSED`. Live keys only: the list has no test mode.

Requires `email_suppressions:w`.

## Request body

- object: The address to block.
  - `email_address` string, email, required: The address. No email is sent to it again until you remove it.
  - `reason` 'manual', required: Always manual: bounces, complaints and unsubscribes are added automatically.

## Response `201`

The suppressed address, lowercased.

- object: The suppressed address, lowercased.
  - `email_address` string, required
  - `reason` 'manual', required

## Other responses

- `401`: Missing, invalid, revoked or expired API key.
- `402`: The account has no balance, or a LIVE key was used before the first top-up.
- `403`: LIVE_KEY_REQUIRED: the suppression list has no test mode and live sends are checked against it, so a test key can read it but not change it. Also FORBIDDEN when the key lacks the permission this operation requires, or the account is suspended or closed.
- `422`: VALIDATION_ERROR: the request failed validation; details names the fields.
- `429`: Rate limit reached: 100 requests per second per account, or a route-specific limit (Retry-After set where one applies).
- `500`: Unexpected server error.

---

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