Stream a session

The session stream (GET /sessions/{id}/events, text/event-stream) is a tail of the journal. Each SSE frame’s data: is one event envelope, and the SSE id: is the event’s UUIDv7 id - the journal key you resume with.

id: 0198c7a2-9f7e-7cc3-bde1-9d24f2c0e001
data: {"id":"…","seq":0,"type":"SESSION_CREATED","payload":{…}}

id: 0198c7a2-9f7e-7cc3-bde1-9d24f2c0e002
data: {"id":"…","seq":1,"type":"MESSAGE_DELTA","payload":{"delta":{"type":"text","text":"Let me"}}}

Every frame carries the full envelope: seq (per-session monotonic), type, payload, timestamps. Render chat from the MESSAGE_* types; everything else is lifecycle (inspect, audit, replay).
The stream replays the full journal from seq 0, then holds the tail open. A fresh client renders history itself, no separate read API.

Resumption — `Last-Event-ID`

Disconnect, then reconnect with the last frame’s id:

curl -N "https://api.sectr.dev/sessions/$SESSION_ID/events" \
  -H "Authorization: Bearer $SECTR_API_KEY" \
  -H "Last-Event-ID: 0198c7a2-9f7e-7cc3-bde1-9d24f2c0e002"

Replay restarts strictly after that event: exactly-once delivery, no gaps, no duplicates. First connect can pass the same value as the last_event_id query parameter instead of the header.

TypeScript