Update the current user's profile.
Partial update — only the fields present in the request body are applied; omitted fields remain unchanged. Use this for first-name / last-name / avatar changes triggered from the in-app profile settings. The caller can only mutate their own profile; identity is taken from the Firebase ID token, not from any path parameter.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
The fields to update.
Response Body
curl -X PATCH "https://api.fruxon.com/v1/users/me" \ -H "Content-Type: application/json" \ -d '{}'{
"id": "string",
"username": "string",
"email": "string",
"firstName": "string",
"lastName": "string",
"avatarFileId": "string",
"status": "INVITED",
"role": "ADMIN",
"effectiveScopes": [
"string"
],
"canCreateWorkspace": false,
"canChooseCell": false,
"solutionPartners": [
{
"id": "00000000-0000-0000-0000-000000000000",
"displayName": "string",
"role": "ADMIN",
"status": "APPLIED",
"canProvision": false
}
],
"createdAt": 0,
"modifiedAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Get the current user's profile.
Returns the global Fruxon profile of the authenticated caller — name, avatar, and other cross-tenant identity fields. The user is identified implicitly by the Firebase ID token; there is no path parameter. A profile row is created on first access (lazy provisioning), so this endpoint always returns 200 for any authenticated caller. For workspace-scoped membership data (role within a specific tenant), use `GET /v1/tenants/{tenant}/users/{user}` instead.
Update a user.
Updates the specified user's properties. Only admins can perform this operation.