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

# Partially updates alert channel information

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

Partially updates one or more fields of an existing alert channel identified by its integer alert_id. Only the fields included in the request body are modified — omitted fields retain their current values. Use this endpoint instead of PUT when making a targeted change to a single field without needing to resend the full channel object.

**Request body fields (all optional)**

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 only the destination email address without affecting the channel name or type

Renaming a channel without modifying its delivery configuration

Making a quick correction to a single field after creation

**Best practices**

Prefer this endpoint over PUT for single-field changes — it reduces payload size and eliminates the risk of accidentally clearing fields that are not included in the body

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

Changes to properties.to_address take effect immediately and affect all alarm rules currently linked to this channel — review linked_alerts via GET /alertchannels/{alert_id} before updating the destination if multiple rules depend on it

## 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.
- `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)