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
| 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; 403 without one.
Request
GET /v1/platform/pipelines takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | pipelineBoard | ok |
200 body — 7 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
pipelines | body | 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
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.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 := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.PlatformAPI.GetPlatformPipelines(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_pipelines(&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).getPlatformPipelines();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/pipelines \
-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?