---
title: "Update Notification Preference"
method: PUT
path: "/profile/notification-preferences"
tags: ["Profile"]
---

# Update Notification Preference

`PUT /profile/notification-preferences`

## Request

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

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.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- ProfileNotificationPreferenceUpdateRequest: 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).
  - `event_type` string, required: The event to configure, as listed by `GET /profile/notification-preferences`. An unknown one is refused with the valid list.
  - `enabled` boolean, nullable
  - `copilot_proactive` boolean, nullable
  - `copilot_bridge` boolean, nullable
  - `bridge_whatsapp` boolean, nullable
  - `bridge_slack` boolean, nullable
  - `bridge_roam` boolean, nullable
  - `bridge_imessage` boolean, nullable
  - `bridge_email` boolean, nullable
  - `routing` 'conversation' | 'notify_only' | 'off', nullable
  - `urgency` 'interrupt_now' | 'fold_into_brief', nullable
  - `hot_override` boolean, nullable

## Response `200`

Successful Response

- ApiResponseOrgPayload
  - `data` OrgPayload, 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".
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)