Stream live events (SSE)
Server-sent event stream of build, runner and release changes, so clients can refresh without polling. Every connection starts with a `ready` event (`EventStreamReady`). Then: `build` (`BuildChangedEvent`), `release` (`ReleaseChangedEvent`), `runner` (`RunnerChangedEvent`, only for users who can read runners), `resync` (`EventStreamResync`, events were dropped and clients should refetch) and `done` (the stream ends, data is the reason). Build and release events are limited to projects the caller can read. Events are not replayed, so a client that reconnects should refetch once on `ready`. Comment keepalives are sent every 15 seconds.
stream_eventsServer-sent event stream of build, runner and release changes, so
clients can refresh without polling. Every connection starts with a
ready event (EventStreamReady). Then: build (BuildChangedEvent),
release (ReleaseChangedEvent), runner (RunnerChangedEvent, only
for users who can read runners), resync (EventStreamResync, events
were dropped and clients should refetch) and done (the stream ends,
data is the reason). Build and release events are limited to projects
the caller can read. Events are not replayed, so a client that
reconnects should refetch once on ready. Comment keepalives are sent
every 15 seconds.
Authorization
bearer_auth In: header
Query Parameters
Only send build and release events for this project
Response Body
text/event-stream
application/json
application/json
application/json
curl -X GET "https://example.com/v1/events""string"