Hanzo
OpenapiPlatform

Returns the versions that actually reached the cluster.

Returns the versions that actually reached the cluster.

GET /v1/platform/releases

Addresshttps://api.hanzo.ai/v1/platform/releases
MethodGET
Operationget_platform_releases
AuthAuthorization: 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

StatusBodyMeaning
200releaseBoardok

200 body — 7 fields.

FieldInTypeAlwaysDescription
releasesbodyreleaseRow[]Releases are the deployments that genuinely reached the cluster.
releases[].environmentbodystringEnvironment is the deploy target the application names.
releases[].idbodystringID is the deployment's id — a release IS a deployment that reached the cluster.
releases[].namebodystringName is the application the release belongs to.
releases[].releasedAtbodystringReleasedAt is when the deployment last changed, RFC3339 UTC.
releases[].statusbodystringStatus is deploying or live — the two states that mean released.
releases[].versionbodystringVersion 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.


Platform API · All Hanzo APIs · Interactive reference

How is this guide?

On this page