---
title: "Update user preferences"
method: PATCH
path: "/api/v1/user/preferences"
tags: ["/api/v1/user/preferences"]
---

# Update user preferences

`PATCH /api/v1/user/preferences`

Updates personalization preferences for the authenticated user, such as note verbosity and section format. Settings apply to future sessions for that user. Send only the fields you want to change.

## Headers

- `sdp_provider_id` string

## Request body

- ControllersPreference — Personalization settings to create or update for the authenticated user.
  - `personalization_preference` ControllersPersonalizationPreference — Personalization settings for content generation
    - `section_format` ControllersSectionFormat[] — Formatting preference per LOINC section. Each entry includes a `loinc` code and `style` (`NARRATIVE` or `BULLETED`).
      - `loinc` string — LOINC code identifying the clinical section
      - `style` 'NARRATIVE' | 'BULLETED' — Preferred formatting style for the section Possible values: NARRATIVE, BULLETED
    - `verbosity` 'CONCISE' | 'BALANCED' | 'DETAILED' — Controls detail level in generated notes. Accepted values: `CONCISE`, `BALANCED`, `DETAILED`.

## Response `200`

Request succeeded.

- ControllersUpdateUserPreferencesResponse — Response body for the /user/preferences endpoint
  - `preference` ControllersPreference — Personalization settings to create or update for the authenticated user.
    - `personalization_preference` ControllersPersonalizationPreference — Personalization settings for content generation
      - `section_format` ControllersSectionFormat[] — Formatting preference per LOINC section. Each entry includes a `loinc` code and `style` (`NARRATIVE` or `BULLETED`).
        - `loinc` string — LOINC code identifying the clinical section
        - `style` 'NARRATIVE' | 'BULLETED' — Preferred formatting style for the section Possible values: NARRATIVE, BULLETED
      - `verbosity` 'CONCISE' | 'BALANCED' | 'DETAILED' — Controls detail level in generated notes. Accepted values: `CONCISE`, `BALANCED`, `DETAILED`.

## Other responses

- `400` — Bad request. The request body or parameters failed validation.
- `401` — Unauthorized. The Suki access token is missing, expired, or invalid.
- `403` — Forbidden. The authenticated user cannot access this resource.
- `404` — Not found. The session, encounter, or resource ID does not exist.
- `500` — Internal server error.

---

[API](https://skmtc.dev/suki/apis/suki-developer-platform.md) · [All operations](https://skmtc.dev/suki/apis/suki-developer-platform/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/suki/suki-developer-platform/revisions/5f420a18fb68/schema)