Hanzo
OpenapiPlatform

Returns one build-and-deploy pipeline per app, with its latest run.

Returns one build-and-deploy pipeline per app, with its latest run.

GET /v1/platform/pipelines

Addresshttps://api.hanzo.ai/v1/platform/pipelines
MethodGET
Operationget_platform_pipelines
AuthAuthorization: Bearer $HANZO_API_KEY

Returns one build-and-deploy pipeline per app, with its latest run.

It returns one pipeline per application in the caller's org — its repo or image source, its current status, and when its most recent deployment ran and how long it took. A pipeline is a PROJECTION of an app plus its newest deployment, not a separate record: it comes into existence with the app and is triggered only through /deploy, never here. Requires a validated principal; 403 without one.

Request

GET /v1/platform/pipelines takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200pipelineBoardok

200 body — 7 fields.

FieldInTypeAlwaysDescription
pipelinesbodypipelineRow[]Pipelines are one per application in the caller's org.
pipelines[].durationbodystringDuration is how long that run took; empty while it is still queued or building.
pipelines[].idbodystringID is the application id — one pipeline is one application.
pipelines[].lastRunbodystringLastRun is when the most recent deployment started, RFC3339 UTC.
pipelines[].namebodystringName is the application's name.
pipelines[].repobodystringRepo is the git repo or image the pipeline builds from.
pipelines[].statusbodystringStatus is the latest deployment's status, or the app's when it has 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