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

Defines the access level a user has within a tenant.

Value in"UNSPECIFIED" | "ADMIN" | "MEMBER"
[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",
  "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
}

Invites a user to join the current tenant.

Creates an outstanding invitation for the given email and sends an invitation email with an accept link. If an invitation already exists for this email in the current tenant it is replaced. If the email is already an active member, returns 400.

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.