Update Notification Preference
PUT /profile/notification-preferences
Update ONE event type, named by event_type.
Singular on purpose, matching the app: a caller that sent the whole map would race with the person changing a different toggle in the browser and silently revert it.
Authorizations
Parameters
Header Parameters
Request Body required
Mirrors user_profile.NotificationPreferenceUpdateRequest.
Updates ONE event type per call - event_type is required and names it.
routing and urgency are closed to the app’s VALID_ROUTING /
VALID_URGENCY vocabulary (a parity test pins them).
object
The event to configure, as listed by GET /profile/notification-preferences. An unknown one is refused with the valid list.
Responses
200
Successful Response
object
An open envelope for a single role, team, member or account record.
Open on purpose. The app’s own response models on this surface grow with
the product - RoleResponse gained rep_limits and manages_role_slugs,
TeamResponse gained channel counts and a campaign count - and a pinned
mirror would SILENTLY DROP whatever it had not caught up on. A dropped
permission in a role read is the worst possible kind of stale: it reads as
“they do not have it”.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error