Update Support Notification Preferences
PUT/api/support/notification-preferences
Saves the signed-in user's support notification switches. All three fields are required — send the full set. Returns the saved preferences.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Request body
in_app(boolean, required) — in-app notifications on ticket replies, status changes and shipped fixesemail_replies(boolean, required) — email copies of agent repliesdigest(string, required) — one of:none,daily
Response fields (data)
in_app(boolean) — receive an in-app notification when an agent replies, when a ticket's status changes, or when a fix for one of your tickets ships. Default trueemail_replies(boolean) — receive an email copy of agent replies on tickets you raised or watch. Default truedigest(string) — one of:none,daily.dailysends one email a day summarising what changed on your organisation's tickets (nothing is sent on days with no changes). Defaultnone
Authentication: Bearer token with the support:write scope, or an authenticated session. Customer endpoints run in tenant context — send the X-Tenant-Id header or call from a tenant subdomain.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthorized
Response Headers
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 Content
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.