PUT /api/me — update the user profile and return the refreshed profile.
const url = 'https://example.com/api/me';const options = { method: 'PUT', headers: {'Content-Type': 'application/json'}, body: '{"avatar_color":"example","avatar_image_data":"example","display_name":"example","locale":"example","ui_preferences":{"font_size":"small","tour_seen":true}}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PUT \ --url https://example.com/api/me \ --header 'Content-Type: application/json' \ --data '{ "avatar_color": "example", "avatar_image_data": "example", "display_name": "example", "locale": "example", "ui_preferences": { "font_size": "small", "tour_seen": true } }'Request Bodyrequired
Section titled “Request Bodyrequired”The PUT /api/me body — a PATCH: an OMITTED field is left alone, a field sent as
null is cleared.
The three text fields are Option<Option<String>> so that distinction survives
deserialization. It is load-bearing: every one of them used to be overwritten with
NULL by any request that did not carry it, so changing your language (web sidebar,
web CLI language, or /language de in Telegram/Discord — all locale-only requests)
silently WIPED your display name and avatar. #[schema(value_type = Option<String>)]
pins the rendered OpenAPI to exactly what it was, so the wire contract is unchanged;
only the server’s reading of an ABSENT field is fixed.
object
A sparse patch over the account’s roaming UI preferences (#838). Omitted keys are left untouched — the bag is MERGED, not replaced, so setting the font size never clears the tour flag.
object
true once the user has completed or dismissed the first-run tour on ANY
device. Absent means “never seen it” — so a brand-new account still gets the
tour, while a second device for an existing account does not replay it.
Responses
Section titled “Responses”The updated user profile
The current user’s profile + session-bootstrap flags — the body of both
GET /api/me and PUT /api/me. Faithful to the JSON [me_response] builds.
object
The user’s stored default live-feed verbosity (#583 / ADR 0049): the raw
persisted label "reduced" | "chatty", or null when no default is set
(the feed then falls back to the built-in reduced). The web CLI’s
density command reads this to show / change the current setting.
The authenticated email; null for an identity without a stored email.
The account’s ROAMING UI preferences (#838, migration 355) — a sparse bag, so a key is present only once the user has actually chosen it. An absent key means “never chosen”: the client keeps its browser-local value (and still shows the first-run tour). Theme is deliberately NOT here — dark/light stays per-device.
object
true once the user has completed or dismissed the first-run tour on ANY
device. Absent means “never seen it” — so a brand-new account still gets the
tour, while a second device for an existing account does not replay it.
Example
{ "active_org_role": "owner", "active_workspace_role": "owner", "ui_preferences": { "font_size": "small" }}Structured client error
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Authentication required
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Structured server error
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}