Bulk Update Alert Preferences
PUT/api/alert-preferences
Updates multiple alert preferences at once (company-wide).
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Authentication: Requires Bearer token.
Requires the alert_preferences.update permission.
Each row: alert_type (required), enabled, email_enabled, slack_enabled (required booleans), notification_frequency (instant|daily_digest|weekly_digest), priority (nullable), email_recipients (required, at least one valid email, when email_enabled is true), slack_webhook_id (required, an existing Slack webhook, when slack_enabled is true).
A row with Slack on and no webhook would never send anything, so it is refused with 422 on that row's preferences.N.slack_webhook_id — "Pick a Slack webhook for this alert, or turn Slack off." — and nothing is saved.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.