PUT /v1/config/notifications/{id}

Update a notification channel's name, credentials, severity threshold, or active state

Updates one or more fields on an existing notification channel. Every field in the body is optional — only the fields you include are changed.

Common uses:

Rotate a webhook URL or HMAC secret after a leak
Change a channel's severity threshold to tune noise
Disable a channel temporarily without deleting it (isActive: false)
Rename a channel

Authentication

API key with config:write permission. The channel must belong to your tenant.

Endpoint

PUT /v1/config/notifications/{id}

Path parameters

Param	Type	Notes
`id`	UUID	The channel id

Request body

All fields are optional. Include only what you want to change.

Field	Type	Notes
`name`	string (1–255 chars)	Descriptive label
`credentials`	object	Replaces the entire credentials object — see create for the per-type shape
`severityThreshold`	`'critical' \| 'high' \| 'medium' \| 'low'`	Lowest severity that fires this channel
`isActive`	boolean	`false` disables delivery without deleting the channel

credentials is a full replacement — pass every field your channel type needs, not just the ones you want to change. For example, to add an HMAC secret to a webhook channel that already has a URL, include both url and hmacSecret in the new object.

{
  "severityThreshold": "critical",
  "isActive": false
}

Response

200 OK

{
  "success": true,
  "data": {
    "updated": true
  }
}

Error responses

Status	`error.code`	When
400	`VALIDATION_ERROR`	`id` is not a UUID, or the body has invalid fields
401	`UNAUTHORIZED`	Missing or invalid API key
403	`FORBIDDEN`	Key lacks `config:write`
404	`NOT_FOUND`	No channel with that id in your tenant

Example

curl -X PUT https://api.sigsentry.com/v1/config/notifications/9b7a3b2c-2e6e-4f1f-8c5a-1b2c3d4e5f6a \
  -H "Authorization: Bearer ss_secret_..." \
  -H "Content-Type: application/json" \
  -d '{ "severityThreshold": "critical" }'

PUT /v1/config/notifications/{id}

On this page