Update another user's profile field values

Upserts profile (EAV) field values for an existing user. This is the endpoint to use for ongoing profile sync; POST /users only creates the account and cannot write profile fields. It is a POST rather than a PATCH because it is an upsert keyed by field: omitted keys are left untouched, and a key may produce an approval request instead of a write. Admins and super-admins write directly; a personal assistant is held to the same per-field permissions as the profile owner. A 201 does not guarantee every value was stored — check skipped, needsApproval and unknown in the response.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
number
required

User ID

Body Params

Profile field values keyed by UserField.key — snake_case (birthday), NOT the camelCase property names POST /users takes. Keys are per-company: the global fields plus any company-specific ones. email, first_name and last_name are columns on the user record rather than profile fields — set them with POST /users or POST /users/bulk-import; sent here they match no field and come back in unknown. Call GET /user-fields to discover every key callable for your company, along with each field’s type and permission level. entity takes the numeric id of an entity in your company (from GET /entities), never its name; send null or "" to unlink. Any other value is rejected with a 400 and nothing in the request is written.

Responses

400

entity must be the id of an entity in this company — the entity value is not the id of an entity in the target user’s company. Nothing in the request is written.

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json