List logs

Returns real logs for a deployment — the build's, then the app's.

GET /v1/platform/projects/{project}/apps/{app}/deployments/{id}/logs

Addresshttps://api.hanzo.ai/v1/platform/projects/{project}/apps/{app}/deployments/{id}/logs
MethodGET
Operationget_platform_projects_by_project_apps_by_app_deployments_by_id_logs
AuthAuthorization: Bearer $HANZO_API_KEY

Returns real logs for a deployment — the build's, then the app's.

It returns the deployment's recorded status timeline together with LIVE pod logs pulled from the cluster: the build pod's output while a git build is running, and the running app's output once it is deployed. The source field says which of the two the body is — build, app or none — so a console can label the pane honestly.

It never fabricates log content. When no pod exists yet, or the cluster is unreachable, it degrades to the recorded timeline and says so. Every cluster read is confined to the caller org's own namespaces and time-boxed. Requires a validated principal; 401 without one.

Request

3 fields.

FieldInTypeRequiredDescription
projectpathstringyesProject is the project the application lives under, from the path.
apppathstringyesApp is the application's slug, from the path.
idpathstringyesID is the deployment's id, from the path.

Response

StatusBodyMeaning
200platform.deployLogsok
defaultproblem-detailsrefused

200 body — 3 fields.

FieldInTypeAlwaysDescription
deploymentIdbodystring—DeploymentID is the deployment these logs belong to.
logsbodystring—Logs is the recorded status timeline followed by the streamed pod output, newline-separated.
sourcebodystring—Source says which pod the log body carries — build, app, or none when neither pod was reachable — so a console can label the pane honestly.

Failure carries the platform error shape — see Errors.

Examples

hanzo platform projects apps deployments logs <project> <app> <id>
import { Configuration, PlatformApi } from 'hanzoai';

const api = new PlatformApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPlatformProjectsByProjectAppsByAppDeploymentsByIdLogs({ project: 'project', app: 'app', id: 'id' });
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_projects_by_project_apps_by_app_deployments_by_id_logs(project='project', app='app', id='id')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.PlatformAPI.GetPlatformProjectsByProjectAppsByAppDeploymentsByIdLogs(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_projects_by_project_apps_by_app_deployments_by_id_logs(&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).getPlatformProjectsByProjectAppsByAppDeploymentsByIdLogs();
curl https://api.hanzo.ai/v1/platform/projects/<project>/apps/<app>/deployments/<id>/logs \
  -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?