Hanzo
OpenapiPlatform

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

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; 403 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
200deployLogsok

200 body — 3 fields.

FieldInTypeAlwaysDescription
deploymentIdbodystringDeploymentID is the deployment these logs belong to.
logsbodystringLogs is the recorded status timeline followed by the streamed pod output, newline-separated.
sourcebodystringSource 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>

Platform API · All Hanzo APIs · Interactive reference

How is this guide?

On this page