---
title: "Update alert channel information"
method: PUT
path: "/v1/enterprise/{enterprise_id}/alertchannels/{alert_id}"
tags: ["esper_cloud_api_Alerts"]
---

# Update alert channel information

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

Fully updates an existing alert channel identified by its integer alert_id. All writable fields should be included in the request body — this is a full replacement operation, not a partial update. To change only one field without affecting others, use PATCH /v1/enterprise/{enterprise_id}/alertchannels/{alert_id} instead.

Request body fields

name — Display name for the channel

type — Delivery format (e.g., email)

properties.to_address — The email address notifications are sent to

**Common use cases**

Updating the destination email address for a channel (e.g., when a team's distribution list changes)

Renaming a channel to better reflect its current purpose or recipients

Correcting a misconfigured channel after creation

**Best practices**

Retrieve the current channel state with GET /v1/enterprise/{enterprise_id}/alertchannels/{alert_id} before updating — since this is a full replacement, omitting fields may clear them unintentionally

Prefer PATCH over PUT when only a single field needs to change, to reduce the risk of accidental data loss

Note that alert_id is an integer, not a UUID — use GET /alertchannels/ to look it up if needed

Updating the destination address on a channel affects all alarm rules linked to it immediately — review linked_alerts on the channel before making changes that will affect notification routing

## Path parameters

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

## Request body

- EsperCloudApiUpdateAlertChannelsV1
  - `id` integer
  - `properties` object
    - `to_address` string, email
  - `name` string
  - `type` string — format of alert. e.g. email
  - `created_on` string, date-time
  - `updated_on` string, date-time
  - `enterprise` string, uuid

## Response `200`

successful operation

- EsperCloudApiAlertChannelsV1
  - `id` integer
  - `properties` object
    - `to_address` string, email
  - `name` string
  - `type` string — format of alert. e.g. email
  - `created_on` string, date-time
  - `updated_on` string, date-time
  - `enterprise` string, uuid
  - `linked_alerts` string[]

## Other responses

- `400` — Invalid request.
- `401` — Authorization information is missing or invalid.
- `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)