List builds

Returns real build records for your org.

GET /v1/platform/builds

Platform → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/platform/builds`
Method	`GET`
Operation	`get_platform_builds`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns real build records for your org.

It lists the org's BuildKit build records — the git build step behind a deploy — each with the repo it built, the short commit, its status, when it started and how long it took, followed by its site builds: a project in the org's own code workspace built from its repository in a sandbox, newest first. These are real records or an honest empty list; a build appears here because one ran, never because a page needed a row. Requires a validated principal; 401 without one.

Request

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

Response

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

200 body — 7 fields.

Field	In	Type	Always	Description
`builds`	body	platform.buildRow[]	—	Builds are the org's real BuildKit build records, newest first.
`builds[].commit`	body	string	—	Commit is the short git ref the build pinned.
`builds[].duration`	body	string	—	Duration is the wall time of a TERMINAL build; empty while it still runs.
`builds[].id`	body	string	—	ID is the build record's id.
`builds[].repo`	body	string	—	Repo is the repo the build built, or the image it produced.
`builds[].startedAt`	body	string	—	StartedAt is when the build was recorded, RFC3339 UTC.
`builds[].status`	body	string	—	Status is the build's real state: queued, building, succeeded or failed.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo platform builds

.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.getPlatformBuilds();

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

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

resp, _, err := client.PlatformAPI.GetPlatformBuilds(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_builds(&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).getPlatformBuilds();

curl https://api.hanzo.ai/v1/platform/builds \
  -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 apps — GET /v1/platform/apps NextList cd — GET /v1/platform/cd