Returns the versions that actually reached the cluster.
Returns the versions that actually reached the cluster.
GET /v1/platform/releases
| Address | https://api.hanzo.ai/v1/platform/releases |
| Method | GET |
| Operation | get_platform_releases |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns the versions that actually reached the cluster.
It lists the org's releases: the deployments that were genuinely applied to the cluster, with the app they belong to, their version, environment, status and when they were released. A deployment that failed or is still building is NOT a release and is excluded — reaching the cluster is what makes one. Requires a validated principal; 403 without one.
Request
GET /v1/platform/releases takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | releaseBoard | ok |
200 body — 7 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
releases | body | releaseRow[] | — | Releases are the deployments that genuinely reached the cluster. |
releases[].environment | body | string | — | Environment is the deploy target the application names. |
releases[].id | body | string | — | ID is the deployment's id — a release IS a deployment that reached the cluster. |
releases[].name | body | string | — | Name is the application the release belongs to. |
releases[].releasedAt | body | string | — | ReleasedAt is when the deployment last changed, RFC3339 UTC. |
releases[].status | body | string | — | Status is deploying or live — the two states that mean released. |
releases[].version | body | string | — | Version is the released image tag, or v<n> when the image carries none. |
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, PlatformApi } from 'hanzoai';
const api = new PlatformApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPlatformReleases();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import PlatformApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = PlatformApi(client).get_platform_releases()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.PlatformAPI.GetPlatformReleases(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, platform_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = platform_api::get_platform_releases(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.PlatformApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new PlatformApi(client).getPlatformReleases();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/platform/releases \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches platform through the platform tool, which names its 39 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": "list_builds"
}
}
}'How is this guide?