OpenapiFlag
List activity
Returns the caller's flag change log newest-first: every create, update and delete, with the actor and the time.
GET /v1/flag/activity
| Address | https://api.hanzo.ai/v1/flag/activity |
| Method | GET |
| Operation | get_flag_activity |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns the caller's flag change log newest-first: every create, update and delete, with the actor and the time.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
limit | query | integer | — | Limit caps the rows returned. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | flag.activityOut | ok |
default | problem-details | refused |
200 body — 7 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | flag.ActivityRow[] | — | Data is the change log newest-first: who created, updated or deleted which key, when. |
data[].action | body | string | — | Action is one of created, updated, deleted. |
data[].actor | body | string | — | Actor is the email of the principal who made the change. |
data[].at | body | string | — | At is when the change was made, RFC 3339 UTC. |
data[].detail | body | string | — | Detail is free-form context about the change. |
data[].id | body | integer (int64) | — | ID is the log's own sequence number, rising with each entry. |
data[].key | body | string | — | Key is the flag that changed. |
Failure carries the platform error shape — see Errors.
Examples
hanzo flag activityimport { Configuration, FlagApi } from 'hanzoai';
const api = new FlagApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getFlagActivity();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import FlagApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = FlagApi(client).get_flag_activity()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.FlagAPI.GetFlagActivity(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, flag_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = flag_api::get_flag_activity(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.FlagApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new FlagApi(client).getFlagActivity();The method above is the one at the current release of the document. [email protected] (npm) was 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/flag/activity \
-H "Authorization: Bearer $HANZO_API_KEY"Tool flags, op get_flag_activity — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "flags",
"arguments": {
"op": "get_flag_activity",
"input": {}
}
}
}'How is this guide?