Docs
Alerts

Create a notification channel

POST
/v1/notification-channels

Adds a place your org's notifications go: a Slack incoming webhook (type: slack, a https://hooks.slack.com/ URL) or a webhook of your own (type: webhook, any https:// URL on port 443). Requires alerts:write. A webhook channel's signing secret is returned once, in this response and its replays; POST /v1/notification-channels/{id}/rotate-secret makes a new one. An org may have 20 channels. Nothing is sent until a subscription names the channel; POST /v1/notification-channels/{id}/test sends one notification now.

Authorization

headerAuthorizationBearer <cc_...>

An API key of your org, sent as Authorization: Bearer cc_.... Keys start with cc_ and are otherwise opaque. Treat a key as a password: anyone holding it can act with its scopes until it expires or is revoked. Each operation's security requirement lists the scopes it needs; an empty list means any valid key. The MCP server at /mcp accepts agent keys and no other kind.

Scope: alerts:write

Header Parameters

Idempotency-Key*string

A unique key for this intent, such as a UUID. Reuse it for every retry of the same request. A missing key returns 400 idempotency_key_required. See Idempotency above.

Match^[!-~]+$
Length1 <= length <= 255
Api-Version*string

The API version the request is written against. This document describes 2026-10-15. A missing header returns 400 api_version_required, and a version the API does not serve returns 400 unsupported_api_version.

X-Correlation-ID?string

An id of your own for this request, or for a group of requests, to find them in our logs and yours. Logged with the request and returned unchanged in X-Correlation-ID. The request id itself is always the API's own, in X-Request-ID.

Match^[A-Za-z0-9._:-]+$
Length1 <= length <= 128
Org-Context?string

Admin keys only: the id of the org to act in. Required with an admin key, together with Access-Reason; with any other credential it returns 400 invalid_request. Every request that carries it is recorded in that org's operator-access log.

Match^org-[a-z0-9]([-a-z0-9]*[a-z0-9])?$
Length5 <= length <= 63
Access-Reason?string

Admin keys only: why the operator is acting in the org, such as a support ticket. Required with Org-Context. Recorded, verbatim, in the org's operator-access log.

Match^[^\x00-\x1F\x7F]+$
Length10 <= length <= 500

Request Body

application/json
  1. body
name*string
Match\S
Length1 <= length <= 100
type*string
Match^(slack|webhook)$
url*string

For slack, a https://hooks.slack.com/ URL. For webhook, an https:// URL on port 443 whose host has a public address.

Match^https://
Length12 <= length <= 2048

Response Body

The channel, with a webhook channel's signing secret the first time.

application/json
  1. response
channel*

Where your org's notifications go. Its URL and signing secret are never returned; host and urlEnding say which it is.

signingSecret?string

A webhook channel's signing secret. Each delivery carries Cloud-Signature: t=<unix seconds>,v1=<hex>, the HMAC-SHA256 with this secret of <t>.<body>. Absent for Slack.

curl -X POST 'https://api.cloud.confidential.ai/v1/notification-channels' \  -H 'Idempotency-Key: 0b9d6c1e-5f8a-4c2e-9a51-2f7e0c3d4b18' \  -H 'Api-Version: 2026-10-15' \  -H 'X-Correlation-ID: rollout-2026-10-22' \  -H 'Access-Reason: Support ticket 4821: customer asked why i-6d3f9h2k8mzr failed' \  -H 'Content-Type: application/json' \  -d '{  "name": "ops-slack",  "type": "slack",  "url": "https://hooks.slack.com/services/T0000/B0000/XXXXXXXXXXXXXXXXXXXXXXXX"}'
Example Response
{  "channel": {    "id": "nc-abcdefghijklmnopqrstuvwxyz",    "name": "pager",    "type": "webhook",    "host": "alerts.example.com",    "urlEnding": "loud",    "status": "active",    "createdAt": "2026-10-23T03:00:00Z"  },  "signingSecret": "whsec_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}