Server-sent events stream of org changes, scoped to projects the caller can see; each SSE message data field is one JSON event, resumable via Last-Event-ID
const url = 'https://example.com/events/orgs/example';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/events/orgs/example \ --header 'Authorization: Bearer <token>'Auth: authenticated
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Resume after this event id (Redis stream id); the Last-Event-ID header takes precedence
Resume after this event id (Redis stream id); the Last-Event-ID header takes precedence
Responses
Section titled “Responses”OK
The JSON-decoded data field of one SSE message on the org event stream
object
The changed entity id (deployment, database, job, run, environment, …); the affected user id for membership.changed
Event-specific payload: structured for jobrun.changed, deployment.metrics, audit.created and build.changed, informer-derived data for pod.changed and database.changed, absent otherwise
Payload for jobrun.changed events
object
Payload for deployment.metrics events, keyed by pod name
object
object
object
Total CPU usage across pods, millicores
Total memory usage across pods, bytes
Payload for audit.created events; id on the envelope is the audit log row id
object
Payload for build.changed events when the write carried a build status; absent for other build writes
object
Emit time, Unix epoch milliseconds
Keepalive sent every 25s so proxies do not kill the stream
object
Example
{ "type": "deployment.changed"}