--- search: tags: - sessions - GET seo: description: >- A separate operation rather than an Accept on the paged… Reference for the GET /v1/sessions/{session_id}/events/stream endpoint in the Subako Public API API. sidebar: label: |- The same log as a live tail, framed as SSE: one event per row, `id` the seq, `event` the wire `type`, `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 `/events` newest-first and deduplicates on seq against what the tail delivers. An initial id-only frame establishes the reconnect cursor without dispatching a message. Continuity before that frame is received requires an explicit `after_seq`. badge: GET title: |- The same log as a live tail, framed as SSE: one event per row, `id` the seq, `event` the wire `type`, `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 `/events` newest-first and deduplicates on seq against what the tail delivers. An initial id-only frame establishes the reconnect cursor without dispatching a message. Continuity before that frame is received requires an explicit `after_seq`. type: openapi-operation --- A separate operation rather than an `Accept` on the paged read: an OpenAPI operation carries one response body per status, so negotiating two on one path leaves a generated client able to reach only whichever media type its generator picked.