SigSentrySigSentry
Notification Channels

Notification Channels

Configure where analysis results are delivered — Slack, Teams, Discord, Google Chat, generic webhooks, and email

A notification channel is a destination for analysis results. When an analysis completes and its severity meets the channel's threshold, the diagnosis is delivered to that channel. Use these endpoints to manage channels and the project-level default severity.

For a conceptual walkthrough and per-platform setup guides, see Notification Channels.

Endpoints

Method + pathPurpose
GET /v1/config/notificationsList channels for the project
POST /v1/config/notificationsCreate a channel
PUT /v1/config/notifications/{id}Update a channel
DELETE /v1/config/notifications/{id}Delete a channel
GET /v1/config/notifications/settingsRead project default severity
PUT /v1/config/notifications/settingsUpdate project default severity

Per-user notification preferences (mute, severity floor, snooze) are managed in the dashboard at Settings → Notifications — they belong to a signed-in user, not a machine identity.

Channel types

typeDestination
slackA Slack channel via incoming webhook
teamsA Microsoft Teams channel via connector webhook
discordA Discord channel via webhook
google_chatA Google Chat space via webhook
webhookAny HTTPS endpoint, optionally HMAC-signed
emailA list of recipients delivered via email

The shape of credentials depends on type. See Create a channel for the per-type credential fields.

Severity threshold

Every channel has a severityThreshold. The channel fires only for analyses whose severity is at or above that threshold. The threshold ordering is critical > high > medium > low.

For routing patterns and how thresholds work, see Severity thresholds.

See also