GET /v1/config/notifications

Returns every active notification channel that delivers for the current project. This includes channels scoped to the project plus any tenant-wide channels.

Authentication

API key with config:read permission. Project-scoped or tenant-scoped (with X-Project-Id).

Endpoint

GET /v1/config/notifications

No query parameters. The current project is implied by the API key (or X-Project-Id for tenant-scoped keys).

Response

200 OK

{
  "success": true,
  "data": [
    {
      "id": "9b7a3b2c-2e6e-4f1f-8c5a-1b2c3d4e5f6a",
      "type": "slack",
      "name": "#engineering-alerts",
      "severityThreshold": "high",
      "isActive": true
    },
    {
      "id": "1f0d2e3a-4b5c-6d7e-8f90-aabbccddeeff",
      "type": "webhook",
      "name": "internal-alerting",
      "severityThreshold": "medium",
      "isActive": true
    }
  ]
}

Field	Type	Notes
`id`	UUID	Channel id — use it to update or delete
`type`	`'slack' \| 'teams' \| 'discord' \| 'google_chat' \| 'webhook' \| 'email'`	Destination platform
`name`	string	The descriptive label you set when creating
`severityThreshold`	`'critical' \| 'high' \| 'medium' \| 'low'`	Lowest severity that fires this channel
`isActive`	boolean	Disabled channels still appear here are filtered out of delivery — but the list endpoint already filters to active only

Credentials (webhook URLs, HMAC secrets, recipient lists) are never returned by this endpoint. Use the dashboard to view or rotate them.

Error responses

Status	`error.code`	When
401	`UNAUTHORIZED`	Missing or invalid API key
403	`FORBIDDEN`	Key lacks `config:read`

Example

curl https://api.sigsentry.com/v1/config/notifications \
  -H "Authorization: Bearer ss_secret_..."