Returns the brand blueprint's version history — every stored version's number…
Returns the brand blueprint's version history — every stored version's number and edit time, newest first — which is the point-in-time-recovery and audit…
GET /v1/guide/blueprint/versions
| Address | https://api.hanzo.ai/v1/guide/blueprint/versions |
| Method | GET |
| Operation | get_guide_blueprint_versions |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns the brand blueprint's version history — every stored version's number and edit time, newest first — which is the point-in-time-recovery and audit trail behind the authoring plane. Metadata only: the documents are not returned. SuperAdmin only, like the rest of this plane. The history is listable even when the current stored document no longer parses, so a schema-drifted row can still be diagnosed.
Request
GET /v1/guide/blueprint/versions takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | blueprintVersionsView | ok |
200 body — 5 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
brand | body | string | — | Brand is the blueprint key the history belongs to — this deployment's brand, or "" (the base blueprint) when the brand has no row of its own. |
versions | body | VersionMeta[] | — | Versions are the stored versions, newest first: metadata only, never the documents. |
versions[].brand | body | string | — | Brand is the white-label key this revision was authored under; empty is the shared base playbook. |
versions[].updatedAt | body | integer | — | UpdatedAt is when this revision was written, as Unix seconds — the "who changed the playbook, and when" half of the audit trail. |
versions[].version | body | integer | — | Version is the store's own revision counter for that brand, starting at 1 for the seeded playbook and incrementing on every edit. |
Failure carries the platform error shape — see Errors.
Examples
hanzo guide blueprint versionsimport { Configuration, GuideApi } from 'hanzoai';
const api = new GuideApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getGuideBlueprintVersions();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import GuideApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = GuideApi(client).get_guide_blueprint_versions()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.GuideAPI.GetGuideBlueprintVersions(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, guide_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = guide_api::get_guide_blueprint_versions(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.GuideApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new GuideApi(client).getGuideBlueprintVersions();curl https://api.hanzo.ai/v1/guide/blueprint/versions \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches guide through the guide tool, which names its 19 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": "get_guide"
}
}
}'How is this guide?