Profile

Update Preferences

Update preferences. Omitted fields are LEFT ALONE, not cleared.

whatsapp_number is validated against the messaging bridge before anything is written: claiming a number another person in the organisation already registered is refused rather than silently stealing their route.

put/profile/preferences

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/profile/preferences
  • Auth: HTTP bearer

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

notifications_emailboolean nullable
notifications_slackboolean nullable
notifications_in_appboolean nullable
default_viewstring nullable
themestring nullable
timezonestring nullable
localestring nullable
mcp_default_clientstring nullable
mcp_tool_groupstring nullable

An id from GET /profile/mcp/tools (a groups[].value or a toolboxes[].id). Anything else is a 422 that lists the valid ids.

mcp_widgets_enabledboolean nullable
whatsapp_numberstring nullable

Response

Successful Response

dataOrgPayload required

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".

Changes

No recorded changes to this operation across all 2 revisions of this API.