Returns your organization's audit trail, newest first — who did what, when, and…
Returns your organization's audit trail, newest first — who did what, when, and from where.
GET /v1/iam/audit-logs
| Address | https://api.hanzo.ai/v1/iam/audit-logs |
| Method | GET |
| Operation | get_iam_audit-logs |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns your organization's audit trail, newest first — who did what, when, and from where. It is the record you reach for during a security review or an incident.
You see your own organization's audit trail and no one else's; which organization that is comes from your credentials, not from the request.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
owner | query | string | — |
Response
| Status | Body | Meaning |
|---|---|---|
200 | iam.ListOutput | ok |
200 body — 20 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
auditLogs | body | iam.AuditLog[] | — | |
auditLogs[].action | body | string | — | |
auditLogs[].clientIp | body | string | — | |
auditLogs[].createdAt | body | string (date-time) | — | |
auditLogs[].createdTime | body | string | — | |
auditLogs[].deleted | body | boolean | — | |
auditLogs[].id | body | string | — | |
auditLogs[].isTriggered | body | boolean | — | |
auditLogs[].language | body | string | — | |
auditLogs[].method | body | string | — | |
auditLogs[].name | body | string | — | |
auditLogs[].object | body | string | — | |
auditLogs[].organization | body | string | — | |
auditLogs[].owner | body | string | — | |
auditLogs[].requestUri | body | string | — | |
auditLogs[].response | body | string | — | |
auditLogs[].statusCode | body | integer | — | |
auditLogs[].updatedAt | body | string (date-time) | — | |
auditLogs[].user | body | string | — | |
total | body | integer | — |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, IamApi } from 'hanzoai';
const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getIamAudit-logs();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).get_iam_audit-logs()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IamAPI.GetIamAudit-logs(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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::get_iam_audit-logs(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IamApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new IamApi(client).getIamAudit-logs();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 https://api.hanzo.ai/v1/iam/audit-logs \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches iam through the iam tool, which names its 75 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": "list__well_known_jwks"
}
}
}'How is this guide?