---
title: "Your notification channel (Slack / Discord / webhook)"
method: GET
path: "/api/v1/notification-channel"
---

# Your notification channel (Slack / Discord / webhook)

`GET /api/v1/notification-channel`

## Request

- Base URL: `https://offnadir-delta.com`
- URL: `https://offnadir-delta.com/api/v1/notification-channel`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Free. The channel your watch notifications are delivered to besides the app and email (one per account), or null when none is connected: provider (`slack`, `discord` or `webhook`), channel and workspace names (the host for a webhook), when it was connected, when it last received a message, how many deliveries in a row have failed, and — if it stopped accepting messages (the webhook was removed, the app uninstalled, or deliveries kept failing) — when and why. The URL and the webhook signing secret are never returned. A Slack or Discord channel is connected in the app, because it goes through Slack’s or Discord’s own consent screen; a webhook is registered with POST /api/v1/notification-channel/webhook. Which watches deliver there is `notify_chat` on each watch.

## Response `200`

The connected channel (or null) and the providers that can be connected.

- object
  - `channel` object, nullable
  - `available_providers` string[]

## Other responses

- `401`: Error response with a stable machine-readable code.
- `403`: Error response with a stable machine-readable code.
- `429`: Error response with a stable machine-readable code.

---

[API](https://skmtc.dev/offnadir-delta/apis/off-nadir-delta-api.md) · [All operations](https://skmtc.dev/offnadir-delta/apis/off-nadir-delta-api/llms.txt) · [OpenAPI document](https://skmtc.dev/offnadir-delta/apis/off-nadir-delta-api/revisions/5cf3f2bed5a2?raw)