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}
| Address | https://api.hanzo.ai/v1/o11y/user/{id} |
| Method | PUT |
| Operation | UpdateUserDeprecated |
| Auth | Authorization: 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).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
id | path | string | yes | |
displayName | body | string | — | DisplayName is the new display name; empty leaves it unchanged. |
role | body | string | — | Role is the legacy role to move to — ADMIN, EDITOR or VIEWER; empty leaves it unchanged. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | o11y.O11yDeprecatedUserOut | ok |
200 body — 11 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | o11y.O11yDeprecatedUser | — | |
data.createdAt | body | string (date-time) | — | CreatedAt is when they joined. |
data.displayName | body | string | — | DisplayName is what the console shows for them. |
data.email | body | string | — | Email is their address. |
data.id | body | string | — | ID is the user id. |
data.isRoot | body | boolean | — | IsRoot marks the org's root user. |
data.orgId | body | string | — | OrgID is the org they belong to. |
data.role | body | string | — | Role is their legacy role — ADMIN, EDITOR or VIEWER. |
data.status | body | string | — | Status is their lifecycle state — active, pending_invite or deleted. |
data.updatedAt | body | string (date-time) | — | UpdatedAt is when their record last changed. |
status | body | string | — | Status is "success". |
Failure carries the platform error shape — see Errors.
Examples
hanzo o11y user set <id>import { Configuration, O11yApi } from 'hanzoai';
const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.updateUserDeprecated({ id: 'id', displayName: "<displayName>", role: "<role>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import O11yApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = O11yApi(client).update_user_deprecated(id='id', display_name="<displayName>", role="<role>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.O11yAPI.UpdateUserDeprecated(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, o11y_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = o11y_api::update_user_deprecated(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.O11yApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new O11yApi(client).updateUserDeprecated();curl -X PUT https://api.hanzo.ai/v1/o11y/user/<id> \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"displayName": "<displayName>",
"role": "<role>"
}'The door reaches o11y through the o11y tool, which names its 340 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "get_o11y_alert_last"
}
}
}'How is this guide?