identity

PATCH /v1/me

Set this person's language and display currency.

Todos los endpoints de identity

Autenticación

Envía una clave de API como token de portador. Este endpoint no especifica un permiso concreto en la especificación, así que otorga a tu clave los mínimos privilegios necesarios y comprueba la respuesta en lugar de dar por sentado.

Este endpoint no requiere ningún id de organización. Su clave ya identifica la organización a la que pertenece, y la respuesta está delimitada a ella.

Pruébalo

Reemplaza cualquier elemento entre corchetes angulares por tus propios valores, y el marcador de posición key con una clave de tu panel de control.

curl -X PATCH https://api.zinndigital.com/v1/me \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

¿Has iniciado sesión? La consola de la API en tu panel de control rellena el ID de tu organización real y tu propia clave, y ejecuta la solicitud contra la API en vivo para que puedas ver la respuesta real. Abre este endpoint en la consola de la API

Detalles

The write path that did not exist — twice, for the same reason, one product surface apart. `User.locale` has been read by the notification renderer since notifications were built, and until 2026-07-30 exactly one code path in the whole platform ever wrote it — the public guest checkout. Anyone who signed up any other way received every email, notice and notification in English for the lifetime of their account, with no endpoint, no screen and no way to change it, while a fully built 58-locale pipeline sat one field-read away. `User.currency` had the same shape until 2026-08-04 (#460). The dashboard's currency switcher wrote a cookie plus `localStorage` and made **no server call at all**, so a customer who chose GBP on their laptop saw USD on their phone, and USD again after clearing cookies. `Organization.default_currency` is not that field: it is the tenant's **billing** currency — what a converting trial is charged in — and it belongs to the org because an invoice is issued to an org, while what a person browses in belongs to the person. Requires only an authenticated user session: this is a person changing a fact about themselves, not an act on an organization, so it carries no permission key. Both fields are optional and independent — send the one that changed. Setting either marks it **chosen**, which is not cosmetic in either case. For language, an explicit choice outranks the `locale` claim the identity provider puts on every token. For currency, it outranks the geo/locale inference that runs on every request (docs/29 §3.1). Without that distinction the inference silently re-decides the value on the next request and the bug looks like "it does not save". `name` and `email` are deliberately NOT writable here. Both belong to Keycloak, and a second writable copy in the engine would drift from the identity the tokens are minted against.

Cuerpo de la solicitud

NombreTipoObligatorio¿Qué es esto?
localeLocaleCodeNoA code from the language registry. Case- and region-tolerant on the way in (`PT-BR` and `pt-BR` are the same choice), stored exactly as the catalogues are keyed. A code this pla…
currencyCurrencyCodeNoAn ISO-4217 code this platform can actually charge in — enabled in the currency registry, presentable by at least one payment gateway, and not policy-blocked. Anything else is R…
analytics_opted_outbooleanNoAsk not to have your use of the app measured, or ask to be measured again. ⚖️ Owner ruling 2026-08-24 — product analytics in the signed-in app runs on legitimate interest with t…

Respuesta

NombreTipoObligatorio¿Qué es esto?
userUser
capabilitiesobjectWhat this **deployment** is wired to do — not what this person is permitted to do. ⛔ The two fail differently: a missing permission means the control is correctly absent, while…
membershipsMembership[]The user's org memberships and roles (docs/02 §1).

Errores que este endpoint puede devolver

401 · 403 · 422 · 429