OpenapiPlatform
List cd
Answers every Application the delivery plane holds.
GET /v1/platform/cd
| Address | https://api.hanzo.ai/v1/platform/cd |
| Method | GET |
| Operation | get_platform_cd |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Answers every Application the delivery plane holds.
Scoped to the namespaces the caller's own validated org owns: the ROLE admits the caller and the tenant boundary is applied inside, so an admin of one org never observes another's.
Request
GET /v1/platform/cd takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | cdResp | ok |
200 body — 14 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
applications | body | CDApp[] | — | |
applications[].automated | body | boolean | — | Automated is whether CD applies git without being asked. |
applications[].health | body | string | — | Health is the workload's verdict: Healthy, Progressing, Degraded, Missing. |
applications[].message | body | string | — | Message is why, when Health is not Healthy. |
applications[].name | body | string | — | Name is the Application name the generator mints: <namespace>-<app>. |
applications[].namespace | body | string | — | Namespace is the DESTINATION namespace as the CR declares it — where the workload lands. |
applications[].operationMessage | body | string | — | |
applications[].path | body | string | — | Path is the values file CD renders against, relative to the chart source. |
applications[].phase | body | string | — | Phase is the last sync operation's phase (Running, Succeeded, Failed) and OperationMessage is its message. |
applications[].project | body | string | — | Project is the AppProject fence the sync is admitted under. |
applications[].reconciledAt | body | string | — | ReconciledAt is when CD last compared this Application. |
applications[].revision | body | string | — | Revision is the universe commit CD last applied. |
applications[].selfHeal | body | boolean | — | SelfHeal is whether CD also corrects drift the cluster introduced. |
applications[].sync | body | string | — | Sync is CD's verdict on git-versus-cluster: Synced, OutOfSync, or Unknown. |
Failure carries the platform error shape — see Errors.
Examples
hanzo platform cdimport { Configuration, PlatformApi } from 'hanzoai';
const api = new PlatformApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPlatformCd();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_cd()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.PlatformAPI.GetPlatformCd(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_cd(&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).getPlatformCd();curl https://api.hanzo.ai/v1/platform/cd \
-H "Authorization: Bearer $HANZO_API_KEY"Tool platform, op get_platform_cd — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "platform",
"arguments": {
"op": "get_platform_cd",
"input": {}
}
}
}'How is this guide?