---
title: "Remove stale recipient bounce suppression"
method: DELETE
path: "/suppressions/{email}"
tags: ["Suppressions"]
---

# Remove stale recipient bounce suppression

`DELETE /suppressions/{email}`

Removes stale bounce suppression for one company-associated recipient from Amazon SES and Sequenzy's local bounce table, then reactivates a bounced company subscriber. Complaint and unsubscribe protections are never removed.

## Path parameters

- `email` string, email, required

## Query parameters

- `region` string

## Response `200`

Suppression cleanup result

- object
  - `success` boolean
  - `email` string, email
  - `removed` boolean
  - `removedLocalBounce` boolean
  - `removedSesRegions` string[]
  - `reactivatedSubscriberIds` string[]
  - `remainingSuppression` object — Recipient suppression status after cleanup

## Other responses

- `400` — Invalid email address or AWS region
- `401` — Unauthorized
- `403` — No company selected
- `404` — Recipient is not associated with the selected company
- `409` — Complaint suppression is protected
- `500` — Internal server error

## Changes

- **2026-08-02** `36f92fc0caa2` — 6 breaking
  - the response property `success` became optional for the status `400`
  - the response property `success` became optional for the status `401`
  - the response property `success` became optional for the status `403`
  - the response property `success` became optional for the status `404`
  - …2 more
- **2026-07-16** `d7ea66dede72` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/sequenzy/apis/sequenzy-api/changes/suppressions/:email/delete.md)

---

[API](https://skmtc.dev/sequenzy/apis/sequenzy-api.md) · [All operations](https://skmtc.dev/sequenzy/apis/sequenzy-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/sequenzy/sequenzy-api/revisions/36f92fc0caa2/schema)