Notifications

A channel is a configured destination for incident alerts — an email address, a Slack webhook, a customer HTTP endpoint, a PagerDuty routing key, or an Opsgenie integration. Attach one or more channels to a monitor (directly, or through a notification policy) and WireWatch sends to all of them when an incident opens, escalates or resolves.

WireWatch sends through five channel types: email, slack, webhook, pagerduty, opsgenie. See Channels for each type’s configuration and what a read gives back.

Channels are managed in the dashboard

Channels are created, edited and deleted from the Channels page in the sidebar (/channels), not through Settings. There is no /v1 endpoint for them: the public API is a frozen contract for monitors, services and results, and channel management has never been part of it. If you are looking for a channel endpoint in the API reference, it is not there because it was never added, not because it is hidden.

What triggers a send

Three event types can produce a notification, matching an incident’s lifecycle:

• opened — the monitor just went down.
• severity_changed — the incident’s scope changed, for example from one region down to a full outage.
• resolved — the monitor recovered.

Every channel receives the same three event types. What the body of each looks like, and which fields you can rely on, is in Payload. Webhook deliveries are signed; the wire contract and a verification sample are in Webhooks.