Replace audit logs

Corrects an audit entry.

PUT /v1/iam/audit-logs/{owner}/{name}

Addresshttps://api.hanzo.ai/v1/iam/audit-logs/{owner}/{name}
MethodPUT
Operationput_iam_audit-logs_by_owner_by_name
AuthAuthorization: Bearer $HANZO_API_KEY

Corrects an audit entry. The trail is append-only in normal operation and nothing in the Hanzo Cloud rewrites it — this exists for an administrator to correct an entry their own systems recorded wrongly.

Request

16 fields, body application/json (required).

FieldInTypeRequiredDescription
ownerpathstringyes
namepathstringyes
actionbodystring—
clientIpbodystring—
createdTimebodystring—
isTriggeredbodyboolean—
languagebodystring—
methodbodystring—
namebodystring—
objectbodystring—
organizationbodystring—
ownerbodystring—
requestUribodystring—
responsebodystring—
statusCodebodyinteger (int64)—
userbodystring—

Response

StatusBodyMeaning
200iam.AuditLogok
202Approvalheld for approval
defaultproblem-detailsrefused

200 body — 18 fields.

FieldInTypeAlwaysDescription
actionbodystring—
clientIpbodystring—
createdAtbodystring (date-time)—
createdTimebodystring—
deletedbodyboolean—
idbodystring—
isTriggeredbodyboolean—
languagebodystring—
methodbodystring—
namebodystring—
objectbodystring—
organizationbodystring—
ownerbodystring—
requestUribodystring—
responsebodystring—
statusCodebodyinteger (int64)—
updatedAtbodystring (date-time)—
userbodystring—

Failure carries the platform error shape — see Errors.

Examples

hanzo iam audit-logs owner set <owner> <name>
import { Configuration, IamApi } from 'hanzoai';

const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.putIamAudit-logsByOwnerByName({ owner: 'owner', name: 'name', action: "<action>", clientIp: "<clientIp>" });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IamApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IamApi(client).put_iam_audit-logs_by_owner_by_name(owner='owner', name='name', action="<action>", client_ip="<clientIp>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.IamAPI.PutIamAudit-logsByOwnerByName(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, iam_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = iam_api::put_iam_audit-logs_by_owner_by_name(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IamApi;

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

var result = new IamApi(client).putIamAudit-logsByOwnerByName();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl -X PUT https://api.hanzo.ai/v1/iam/audit-logs/<owner>/<name> \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "action": "<action>",
       "clientIp": "<clientIp>"
     }'

MCP reaches iam through the iam tool, which names its 44 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_iam_applications"
         }
       }
     }'

IAM API · All Hanzo APIs · Interactive reference

Was this page useful?