List pipelines

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

GET /v1/platform/pipelines

Platform → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/platform/pipelines`
Method	`GET`
Operation	`get_platform_pipelines`
Auth	`Authorization: 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; 401 without one.

Request

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

Response

Status	Body	Meaning
`200`	platform.pipelineBoard	ok
`default`	problem-details	refused

200 body — 7 fields.

Field	In	Type	Always	Description
`pipelines`	body	platform.pipelineRow[]	—	Pipelines are one per application in the caller's org.
`pipelines[].duration`	body	string	—	Duration is how long that run took; empty while it is still queued or building.
`pipelines[].id`	body	string	—	ID is the application id — one pipeline is one application.
`pipelines[].lastRun`	body	string	—	LastRun is when the most recent deployment started, RFC3339 UTC.
`pipelines[].name`	body	string	—	Name is the application's name.
`pipelines[].repo`	body	string	—	Repo is the git repo or image the pipeline builds from.
`pipelines[].status`	body	string	—	Status is the latest deployment's status, or the app's when it has none.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo platform pipelines

.ts

.py

.go

.rs

.java

import { Configuration, PlatformApi } from 'hanzoai';

const api = new PlatformApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPlatformPipelines();

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_pipelines()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.PlatformAPI.GetPlatformPipelines(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::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_pipelines(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.PlatformApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new PlatformApi(client).getPlatformPipelines();

curl https://api.hanzo.ai/v1/platform/pipelines \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches platform through the platform tool, which names its 38 operations with its own verbs — this one among them, under a name only MCP 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_build"
         }
       }
     }'

Platform API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList health NextList logs