Hanzo
OpenapiO11y

Renames one org member and may move their legacy role, answering with the…

Renames one org member and may move their legacy role, answering with the updated record.

PUT /v1/o11y/user/{id}

Addresshttps://api.hanzo.ai/v1/o11y/user/{id}
MethodPUT
OperationUpdateUserDeprecated
AuthAuthorization: Bearer $HANZO_API_KEY

Renames one org member and may move their legacy role, answering with the updated record. Admins may update anyone; a non-admin only themselves (the runtime's self-access gate).

Request

3 fields, body application/json (required).

FieldInTypeRequiredDescription
idpathstringyes
displayNamebodystringDisplayName is the new display name; empty leaves it unchanged.
rolebodystringRole is the legacy role to move to — ADMIN, EDITOR or VIEWER; empty leaves it unchanged.

Response

StatusBodyMeaning
200o11y.O11yDeprecatedUserOutok

200 body — 11 fields.

FieldInTypeAlwaysDescription
databodyo11y.O11yDeprecatedUser
data.createdAtbodystring (date-time)CreatedAt is when they joined.
data.displayNamebodystringDisplayName is what the console shows for them.
data.emailbodystringEmail is their address.
data.idbodystringID is the user id.
data.isRootbodybooleanIsRoot marks the org's root user.
data.orgIdbodystringOrgID is the org they belong to.
data.rolebodystringRole is their legacy role — ADMIN, EDITOR or VIEWER.
data.statusbodystringStatus is their lifecycle state — active, pending_invite or deleted.
data.updatedAtbodystring (date-time)UpdatedAt is when their record last changed.
statusbodystringStatus is "success".

Failure carries the platform error shape — see Errors.

Examples

hanzo o11y user set <id>

O11y API · All Hanzo APIs · Interactive reference

How is this guide?

On this page