# suppression.removed

Event triggered whenever an **email address is removed from your suppression
list**.

## Response Body Parameters

All webhook payloads follow a consistent top-level structure with
event-specific data nested within the `data` object.

- `type` (string) — The event type that triggered the webhook (e.g., `suppression.removed`).

- `created_at` (string) — ISO 8601 timestamp when the webhook event was created.

- `data` (object) — Event-specific data containing detailed information about the event. The data object for the `suppression.removed` event contains the following parameters:

  :::accordion{title="object parameters"}
  - `id` (string) — Unique identifier for the suppression

  - `email` (string) — The suppressed email address

  - `origin` (string) — How the address was suppressed: `bounce`, `complaint`, or `manual`

  - `source_id` (string | null) — ID of the email that triggered the suppression. For suppressions with a `manual` origin, `source_id` is `null`

  - `created_at` (string) — ISO 8601 timestamp when the suppression was created
  :::

:::code-group
```json
{
  "type": "suppression.removed",
  "created_at": "2026-11-17T19:32:22.980Z",
  "data": {
    "id": "e169aa45-1ecf-4183-9955-b1499d5701d3",
    "email": "steve.wozniak@gmail.com",
    "origin": "manual",
    "source_id": null,
    "created_at": "2026-11-15T08:12:45.120Z"
  }
}
```
:::

## Related pages

- [email.bounced](./learn-webhooks-emails-bounced.md)
- [email.clicked](./learn-webhooks-emails-clicked.md)
- [email.complained](./learn-webhooks-emails-complained.md)
- [email.delivered](./learn-webhooks-emails-delivered.md)
- [email.delivery_delayed](./learn-webhooks-emails-delivery-delayed.md)
- [email.failed](./learn-webhooks-emails-failed.md)
- [email.opened](./learn-webhooks-emails-opened.md)
- [email.received](./learn-webhooks-emails-received.md)
- [email.scheduled](./learn-webhooks-emails-scheduled.md)
- [email.sent](./learn-webhooks-emails-sent.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.