Notification Channels
PUT /v1/config/notifications/settings
Update the organization's default notification severity threshold
Sets the organization-wide default severity threshold. New channels created after this call use this value as their starting threshold (it remains overridable per channel).
For guidance on choosing a default, see Severity thresholds → Recommended starting point.
Authentication
API key with config:write permission.
Endpoint
PUT /v1/config/notifications/settingsRequest body
| Field | Type | Required | Notes |
|---|---|---|---|
defaultSeverityThreshold | 'critical' | 'high' | 'medium' | 'low' | ✓ | New default |
{
"defaultSeverityThreshold": "high"
}Response
200 OK
{
"success": true,
"data": {
"updated": true
}
}Error responses
| Status | error.code | When |
|---|---|---|
| 400 | VALIDATION_ERROR | defaultSeverityThreshold missing or not a recognized severity |
| 401 | UNAUTHORIZED | Missing or invalid API key |
| 403 | FORBIDDEN | Key lacks config:write |
Example
curl -X PUT https://api.sigsentry.com/v1/config/notifications/settings \
-H "Authorization: Bearer ss_secret_..." \
-H "Content-Type: application/json" \
-d '{ "defaultSeverityThreshold": "high" }'Scope
Changing the default does not retroactively change existing
channels' thresholds. Each channel keeps the threshold it was created
with until you update it via
PUT /v1/config/notifications/{id}.
