alertChannelIds when creating or updating a monitor.
List alert channels
Response
Example
Create an alert channel
admin or owner role. Returns 402 if your organization has no active subscription, and 422 with "upgrade": true if you have reached your alert channel limit.
Request body
string
required
Display name for the channel.
string
required
Channel type. One of
SLACK, DISCORD, TEAMS, EMAIL, WEBHOOK.object
required
Type-specific configuration. See Config by channel type below.
boolean
Whether the channel should fire alerts. Defaults to
true.Config by channel type
WEBHOOK channels, the optional secret is used to sign outgoing payloads with an HMAC signature so your endpoint can verify requests came from Overwatch.
Response
Returns201 Created with the new channel object.
Example
Get an alert channel
Path parameters
string
required
The alert channel ID.
Response
Example
Update an alert channel
admin or owner role.
Path parameters
string
required
The alert channel ID.
Request body
string
New display name.
object
Updated type-specific configuration. Must match the channel’s existing type.
boolean
Set to
false to silence alerts from this channel without deleting it.Response
Returns the updated channel object with200 OK.
Example
Delete an alert channel
admin or owner role.
Path parameters
string
required
The alert channel ID.
Response
Example
Binding channels to monitors
Alert channels do not fire on their own — you must bind them to at least one monitor. You do this by passingalertChannelIds when creating or updating a monitor:
alertChannelIds in a PATCH replaces the full set of bindings. To remove all bindings, pass an empty array.