Hanzo
OpenapiDeploy

Live application fleet updates as Server-Sent Events

Holds the connection open as text/event-stream and pushes one watch event per application change.

GET /v1/deploy/stream/applications

Addresshttps://api.hanzo.ai/v1/deploy/stream/applications
MethodGET
Operationget_deploy_stream_applications
AuthAuthorization: Bearer $HANZO_API_KEY

Holds the connection open as text/event-stream and pushes one watch event per application change. It opens with an ADDED frame for every application currently present — the same projection the applications list serves, so a client renders a complete fleet from the stream alone — and then forwards ADDED, MODIFIED and DELETED as they happen, with a keep-alive every 25 seconds that is also how a vanished client is noticed and its watch torn down.

Read-only and TENANT-SCOPED, fail-closed: a platform SuperAdmin streams the whole fleet, a validated org member streams only its own org's applications, anyone else gets 403 and no stream. No cluster client configured is 503. If the deployment is not granted the watch verb the stream degrades to keep-alives only — the initial state still renders, it simply stops updating — rather than failing the connection.

Request

GET /v1/deploy/stream/applications takes no parameters and no body — the credential is the whole request.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo deploy stream applications list

Deploy API · All Hanzo APIs · Interactive reference

How is this guide?

On this page