FruxonDocs
UsersCore

Update a user.

Updates the specified user's properties. Only admins can perform this operation.

PATCH
/v1/tenants/{tenant}/users/{user}

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

user*string

The unique identifier of the user.

tenant*string

The tenant identifier

Request Body

The fields to update.

role?string

The new role to assign to the user.

Value in"UNSPECIFIED" | "ADMIN" | "MEMBER" | "OWNER" | "DEVELOPER" | "OPERATOR" | "VIEWER"
[key: string]?never

Response Body

curl -X PATCH "https://api.fruxon.com/v1/tenants/string/users/string" \  -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
}
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

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.

Gets the current status of a long-running operation.

Returns the current lifecycle state of an async job (ingestion, refresh, deletion, etc). Clients should poll this endpoint until `status` reaches a terminal state (`DONE` or `FAILED`); intermediate states are `PENDING` and `RUNNING`. On success, `resourceName` points to the affected resource and `metadata` may carry provider-specific progress info — treat any progress signal as advisory and not strictly monotonic. On failure, `error` contains a human-readable reason. The operation id is the same value returned in the `name` field of the resource that started the job. Polling intervals of 1–5 seconds are reasonable; do not poll faster than once per second.