Hanzo
OpenapiKv

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

Addresshttps://api.hanzo.ai/v1/kv/{bucket}/{key}/history
MethodGET
Operationget_kv_by_bucket_by_key_history
AuthAuthorization: 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.

FieldInTypeRequiredDescription
bucketpathstringyesBucket is the bucket, from the path.
keypathstringyesKey is the key, from the path.

Response

StatusBodyMeaning
200kvPageok

200 body — 6 fields.

FieldInTypeAlwaysDescription
databodykvEntry[]Data are the key's retained revisions.
data[].createdbodystringCreated is when this revision was written, RFC3339.
data[].keybodystringKey is the entry's key.
data[].operationbodystringOperation is what wrote the revision: put, del or purge.
data[].revisionbodyintegerRevision is the entry's revision in the bucket.
data[].valuebodystringValue 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.


KV API · All Hanzo APIs · Interactive reference

How is this guide?

On this page