Replace keys

Renames an API key or moves its expiry.

PUT /v1/o11y/service_accounts/{id}/keys/{fid}

O11y → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/o11y/service_accounts/{id}/keys/{fid}`
Method	`PUT`
Operation	`UpdateServiceAccountKey`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Renames an API key or moves its expiry.

Request

4 fields, body application/json (required).

Field	In	Type	Required	Description
`id`	path	string	yes
`fid`	path	string	yes
`expiresAt`	body	integer (uint64)	—	ExpiresAt is when the key stops working, as a unix timestamp in seconds.
`name`	body	string	—	Name is the key's new name, under the same rules it was created with.

Response

Status	Body	Meaning
`202`	Approval	held for approval
`204`	—	no content
`default`	problem-details	refused

202 body — 3 fields.

Field	In	Type	Always
`clause`	body	string	—
`reason`	body	string	—
`status`	body	string	—

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo o11y service_accounts keys set <id> <fid>

.ts

.py

.go

.rs

.java

import { Configuration, O11yApi } from 'hanzoai';

const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.updateServiceAccountKey({ id: 'id', fid: 'fid', expiresAt: 0, name: "<name>" });

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_service_account_key(id='id', fid='fid', expires_at=0, name="<name>")

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.O11yAPI.UpdateServiceAccountKey(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::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_service_account_key(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.O11yApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new O11yApi(client).updateServiceAccountKey();

curl -X PUT https://api.hanzo.ai/v1/o11y/service_accounts/<id>/keys/<fid> \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "expiresAt": 0,
       "name": "<name>"
     }'

MCP reaches o11y through the o11y tool, which names its 307 operations with its own verbs — this one among them, under a name only MCP 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": "list_o11y_autocomplete_aggregate_attributes"
         }
       }
     }'

O11y API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousReplace service accounts NextUpdate span mappers