---
title: "Delete an unsubscribe group"
method: DELETE
path: "/email_unsubscribe_groups/{id}"
tags: ["Email Unsubscribe Groups"]
---

# Delete an unsubscribe group

`DELETE /email_unsubscribe_groups/{id}`

If the group has 0 active suppressions, hard-deletes the row. With
`force=true`, soft-deletes all active suppressions first (status →
`removed`, `group_id` cleared, `removed` audit event per block) in a
single transaction, then hard-deletes the group. Without `force`
and active suppressions present → `409`. Audit trail is preserved.
`force` only accepts the string `"true"` or boolean `true`; all other
values are false.

## Query parameters

- `force` union
  - 'true' | 'false'
  - boolean

## Response `204`

Deleted.

## 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.
- `409` — Group has active suppressions and `force` is false.
- `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/versions/8f5f4e537994/schema)