---
title: "Stream Deployment Progress"
method: GET
path: "/versions/{version_id}/deploy/events"
tags: ["Versions"]
---

# Stream Deployment Progress

`GET /versions/{version_id}/deploy/events`

SSE endpoint for real-time deployment progress events.

## Path parameters

- `version_id` string, required

## Response `200`

SSE stream of deployment events

- union — Union of all possible deploy stream SSE events. Use the 'type' field to discriminate between event types: - "connected": Stream connection established - "queued": Deployment queued - "helm_started": Helm deployment started - "helm_waiting": Waiting for pods to be ready - "ready": Deployment successful - "failed": Deployment failed - "rolling_back": Rolling back deployment - "complete": Stream complete, terminal state reached - "error": An error occurred in the stream
  - DeployStreamConnectedEvent — Sent when SSE deploy stream connection is established. Indicates the client is now subscribed and will receive deployment progress events.
    - `type` 'connected'
    - `version_id` string, required — Version ID this stream is subscribed to
  - DeployStreamQueuedEvent — Deployment has been queued for processing.
    - `message` string, nullable — Optional status message
    - `timestamp` string, required — ISO 8601 timestamp
    - `type` 'queued'
    - `version_id` string, required — Version ID being deployed
  - DeployStreamHelmStartedEvent — Helm deployment has started.
    - `message` string, nullable — Optional status message
    - `timestamp` string, required — ISO 8601 timestamp
    - `type` 'helm_started'
    - `version_id` string, required — Version ID being deployed
  - DeployStreamHelmWaitingEvent — Waiting for Helm deployment to complete (pods becoming ready).
    - `message` string, nullable — Optional status message
    - `timestamp` string, required — ISO 8601 timestamp
    - `type` 'helm_waiting'
    - `version_id` string, required — Version ID being deployed
  - DeployStreamReadyEvent — Deployment completed successfully.
    - `message` string, nullable — Optional status message
    - `timestamp` string, required — ISO 8601 timestamp
    - `type` 'ready'
    - `version_id` string, required — Version ID being deployed
  - DeployStreamFailedEvent — Deployment failed.
    - `failure_reason` string, nullable — Detailed failure reason
    - `message` string, nullable — Error message
    - `timestamp` string, required — ISO 8601 timestamp
    - `type` 'failed'
    - `version_id` string, required — Version ID being deployed
  - DeployStreamRollingBackEvent — Deployment is being rolled back.
    - `message` string, nullable — Optional status message
    - `timestamp` string, required — ISO 8601 timestamp
    - `type` 'rolling_back'
    - `version_id` string, required — Version ID being rolled back
  - DeployStreamCompleteEvent — Stream is complete - deployment has reached a terminal state. Sent by the SSE endpoint when the version status is terminal (ACTIVE, FAILED, etc.).
    - `status` string, required — Final version status (e.g., 'active', 'failed')
    - `type` 'complete'
  - DeployStreamErrorEvent — Sent when an error occurs in the deploy stream. After this event, the stream may close.
    - `message` string, required — Error description
    - `type` 'error'

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/terminaluse/apis/sb0-api.md) · [All operations](https://skmtc.net/terminaluse/apis/sb0-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/terminaluse/sb0-api/revisions/f24a474dc415/schema)