Update a user
PATCH /users/{user_id}
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”User id
Example
42Request Body
Section titled “Request Body ”object
New work email. Same validation as create; must not belong to another active user when changed.
Example
Given name. Omit for no change; null clears when supported.
Example
AdaFamily name. Omit for no change; null clears when supported.
Example
LovelaceContact phone; spaces are removed. Omit for no change; null clears when supported.
Example
+33123456789Omit for no change; null clears when supported.
Example
FRNew password: only a non-empty string updates the login password (hashed server-side). Omit for no change; null does not clear an existing password.
Example
hunter2Preferred UI language. Omit for no change; null clears when supported.
Example
frJob title. Omit for no change; null clears when supported.
Example
Software engineerEmployment start. Omit for no change; null clears when supported.
Example
2024-01-15Employment end. Omit for no change; null clears when supported.
Example
2026-12-31Date of birth. Omit for no change; null clears when supported.
Example
1990-05-21City of birth. Omit for no change; null clears when supported.
Example
ParisCountry of birth. Omit for no change; null clears when supported.
Example
FREMPLOYEE: standard company user. ADMIN: can manage company configuration and users in Fleet. On create, defaults to EMPLOYEE when omitted.
Example
EMPLOYEEResponses
Section titled “ Responses ”Updated user
object
object
EMPLOYEE: standard company user. ADMIN: can manage company configuration and users in Fleet. On create, defaults to EMPLOYEE when omitted.
Example
EMPLOYEE