Subscribe to the real-time event stream

Server-Sent Events (text/event-stream) feed of newly indexed events. Each message's data is the fully decoded event as JSON and its id is the monotonic events.id. Reconnecting clients resume from Last-Event-ID (or the last_event_id query param) without gaps. A cursor beyond the current tip (e.g. one stored before an event-log reset) is clamped to the tip and the stream resumes live. objects (comma-separated ids, at most 100) delivers only the events whose payload names one of them. While kinds or objects passes events over, the stream sends its position as an id: line with no data:, so a reconnect resumes past them.

The stream opens with a retry: directive; honour it. The response is ended deliberately whenever the backlog cannot be replayed, and a client that reconnects immediately instead will spend an outage in a connect/close loop and can exhaust its events:read rate limit. A 429 is fatal to EventSource — per the HTML spec it stops reconnecting for good — so size that scope's limit above your expected subscriber count.

The response also ends after at most 10 minutes, and when the API key expires; reconnecting with Last-Event-ID resumes where it stopped, and re-checks the key. A key may hold 10 streams open at once; another is refused with 429. When the server is at capacity a stream is refused with 503 and a Retry-After. EventSource treats both as final too.

Required API-key scope: events:read.