Delete defs
Removes one flag definition by key and records the deletion in the change log.
DELETE /v1/flag/defs/{key}
| Address | https://api.hanzo.ai/v1/flag/defs/{key} |
| Method | DELETE |
| Operation | delete_flag_defs_by_key |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Removes one flag definition by key and records the deletion in the change log. A key the caller's store does not hold is a 404.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
key | path | string | yes | Key is the flag key to act on, from the path. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | flag.deletedOut | ok |
default | problem-details | refused |
200 body — 1 field.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
deleted | body | string | — | Deleted is the key that no longer exists. |
Failure carries the platform error shape — see Errors.
Examples
hanzo flag defs rm <key>import { Configuration, FlagApi } from 'hanzoai';
const api = new FlagApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteFlagDefsByKey({ key: 'key' });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).delete_flag_defs_by_key(key='key')cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.FlagAPI.DeleteFlagDefsByKey(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::delete_flag_defs_by_key(&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).deleteFlagDefsByKey();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 -X DELETE https://api.hanzo.ai/v1/flag/defs/<key> \
-H "Authorization: Bearer $HANZO_API_KEY"MCP reaches flag through the flags tool, which names its 8 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": "get_flag_activity"
}
}
}'How is this guide?