Update Topic Overrides Endpoint

PUT/api/v1/preferences/notifications/topics

Replace the per-topic channel override map for the current user.

Validation is permissive: unknown topics or unknown channels are silently dropped by extract_topic_overrides rather than rejected, so a forward-compatible client (e.g. one that knows about a topic the server hasn't deployed yet) won't break the save.

Operation ID: update_topic_overrides_endpoint·View as markdown·OpenAPI slice

Authentication

Bearer token authentication. Pass your DayZero API token in the Authorization header and the target business UUID in x-business-id.

Request body

Schema: TopicChannelOverridesUpdate

overridesobject

Responses

200Successful Response

Schema: SuccessEnvelope_TopicChannelOverridesResponse_

successboolean
messagestring
codestring
dataTopicChannelOverridesResponse

422Validation Error

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

Code samples

PUT/api/v1/preferences/notifications/topics

bash

curl -X PUT 'https://api.ondayzero.com/api/v1/preferences/notifications/topics' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "overrides": {}
}'