History returns one key's retained revisions, oldest first — every put and…
History returns one key's retained revisions, oldest first — every put and every delete marker up to the bucket's History depth.
GET /v1/kv/{bucket}/{key}/history
| Address | https://api.hanzo.ai/v1/kv/{bucket}/{key}/history |
| Method | GET |
| Operation | get_kv_by_bucket_by_key_history |
| Auth | Authorization: Bearer $HANZO_API_KEY |
History returns one key's retained revisions, oldest first — every put and every delete marker up to the bucket's History depth. 404 when the bucket does not exist or the key was never written.
Request
2 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
bucket | path | string | yes | Bucket is the bucket, from the path. |
key | path | string | yes | Key is the key, from the path. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | kvPage | ok |
200 body — 6 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | kvEntry[] | — | Data are the key's retained revisions. |
data[].created | body | string | — | Created is when this revision was written, RFC3339. |
data[].key | body | string | — | Key is the entry's key. |
data[].operation | body | string | — | Operation is what wrote the revision: put, del or purge. |
data[].revision | body | integer | — | Revision is the entry's revision in the bucket. |
data[].value | body | string | — | Value is the value as UTF-8 text; empty for delete and purge markers. |
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, KvApi } from 'hanzoai';
const api = new KvApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getKvByBucketByKeyHistory({ bucket: 'bucket', key: 'key' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import KvApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = KvApi(client).get_kv_by_bucket_by_key_history(bucket='bucket', key='key')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.KvAPI.GetKvByBucketByKeyHistory(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, kv_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = kv_api::get_kv_by_bucket_by_key_history(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.KvApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new KvApi(client).getKvByBucketByKeyHistory();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/kv/<bucket>/<key>/history \
-H "Authorization: Bearer $HANZO_API_KEY"The door declares no tool for kv — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?