---
title: "Delete an alert channel"
method: DELETE
path: "/v1/enterprise/{enterprise_id}/alertchannels/{alert_id}"
tags: ["esper_cloud_api_Alerts"]
---

# Delete an alert channel

`DELETE /v1/enterprise/{enterprise_id}/alertchannels/{alert_id}`

⚠️ Android only. 

Permanently deletes an alert channel identified by its integer alert_id. This action is irreversible. Any alarm rules that were linked to this channel will lose their association with it — verify the channel's linked_alerts before deleting to avoid silently disrupting alert delivery for active alarm rules.

**Common use cases**

Removing a channel whose destination email address is no longer valid or monitored

Cleaning up duplicate or test channels created during setup

Decommissioning a channel as part of a notification infrastructure reorganization

**Best practices**

Check linked_alerts by calling GET /v1/enterprise/{enterprise_id}/alertchannels/{alert_id} before deleting — if the channel is actively linked to alarm rules, update or delete those rules first, or reassign them to a different channel, to avoid broken alert delivery

Confirm the correct alert_id before issuing the delete — this action cannot be undone and alert_id is an integer, not a UUID

Use GET /v1/enterprise/{enterprise_id}/alertchannels/ with the name filter to locate the correct channel if the alert_id is not already known

## Path parameters

- `enterprise_id` string, uuid, required
- `alert_id` integer, required

## Response `204`

The resource was deleted successfully.

## Other responses

- `400` — Invalid request.
- `401` — Authorization information is missing or invalid.
- `403` — Forbidden, no permission to perform this action.
- `404` — Not Found.
- `500` — Internal server error

---

[API](https://skmtc.net/esper/apis/esper-api-reference.md) · [All operations](https://skmtc.net/esper/apis/esper-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/esper/esper-api-reference/revisions/e1f64cbb488e/schema)