---
title: "Remove a group suppression"
method: DELETE
path: "/email_unsubscribe_groups/{id}/suppressions/{email}"
tags: ["Email Unsubscribe Groups"]
---

# Remove a group suppression

`DELETE /email_unsubscribe_groups/{id}/suppressions/{email}`

Soft-deletes all active blocks for (account, group, normalized
email) — one `removed` audit event per block (`actor: manual`).
The `email` path segment is normalized (trim + lower-case) before
matching. Idempotent on already-removed rows (returns `404` since
they're no longer `active`).

Two distinct `404` cases: a missing/cross-account **group** returns
`10001 "The requested unsubscribe group was not found"`; a group that
exists but has **no active suppression** for that email returns
`10001 "The requested group suppression was not found"`.

## Response `204`

Removed.

## Other responses

- `401` — Missing or invalid gateway auth.
- `404` — Resource not found (cross-account lookups and malformed UUIDs also return 404 — no leak).
- `406` — Framework-rendered error (e.g. 406 Not Acceptable, 405 Method Not Allowed, 415 Unsupported Media Type). HTTP status matches the error and the body `code` carries that same status (e.g. `"406"`, not a hardcoded `"500"`). The explicit `500.json` clause still emits `code: "500"` for genuine 500s.
- `422` — Validation error (changeset or internal `Params`). One error object per field, `source.pointer /data/attributes/<field>`.

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/8f5f4e537994/schema)