--- search: tags: - sessions - GET seo: description: >- The same log as a live tail, framed as server-sent… Reference for the GET /v1/sessions/{session_id}/events/stream endpoint in the Subako Public API API. sidebar: label: Stream session events badge: GET title: Stream session events type: openapi-operation --- The same log as a live tail, framed as server-sent events: one event per row, `id` the seq, `event` the wire `type`, and `data` the same `SessionEventBody` the paged read renders. The stream stays open across idle stretches -- a keep-alive comment holds the connection while nothing happens -- so one connection spans a session's whole life rather than a single run. With no position named it starts at the live head, fixed before the response begins; a client that wants history pages the events route newest-first and deduplicates on seq against what the tail delivers.