API: sse
GET /api/v1/sse/all
Section titled “GET /api/v1/sse/all”Sse All
Subscribe to every event channel.
| Parameter | In | Required | Type |
|---|---|---|---|
access_token | query | no | object |
GET /api/v1/sse/integrations
Section titled “GET /api/v1/sse/integrations”Sse Integrations
SPEC-015 §3.5 — connection status-change events.
The integrations health-checker emits integration.status whenever a
connection’s credential or health status changes.
| Parameter | In | Required | Type |
|---|---|---|---|
access_token | query | no | object |
GET /api/v1/sse/lifecycle
Section titled “GET /api/v1/sse/lifecycle”Sse Lifecycle
SPEC-007 §14.1 / §14.2 — lifecycle SSE channel.
Emits: lifecycle.transitioned, lifecycle.autorun.completed, lifecycle.message, lifecycle.batch.completed. Source of truth — LifecycleEngine, which publishes only after session.commit() (SPEC-007 §14.3). Multi-worker note: in-memory bus is MVP; Redis-backed migration is SPEC-007 §14.4 (same pattern as runs:sse §5.8.3).
| Parameter | In | Required | Type |
|---|---|---|---|
access_token | query | no | object |
GET /api/v1/sse/publish
Section titled “GET /api/v1/sse/publish”Sse Publish
Subscribe to publish/deploy progress events.
| Parameter | In | Required | Type |
|---|---|---|---|
access_token | query | no | object |
GET /api/v1/sse/runs
Section titled “GET /api/v1/sse/runs”Sse Runs
Subscribe to pipeline-run events — Redis-backed, multi-worker (§5.8.3).
| Parameter | In | Required | Type |
|---|---|---|---|
access_token | query | no | object |
GET /api/v1/sse/workspace
Section titled “GET /api/v1/sse/workspace”Sse Workspace
SPEC-001 §7.3 — Workspace channel.
Emits: spec., issue., defect., comment., agent_action.* events.
| Parameter | In | Required | Type |
|---|---|---|---|
access_token | query | no | object |