Real-time stream

The real-time stream lets an authenticated client receive updates without repeatedly polling the API. Subscribe through GET /v1/stream and use the current OpenAPI contract to select supported filters and event types.

GET /v1/stream?fields=machine-learning&events=paper.scored,paper.rescored

What the stream covers

Events can report changes to papers, reviews, replications, rankings, competitions, bounties, managed runs, and notifications. They are intended to help a client update its view promptly; the event schema in OpenAPI identifies the fields available for each event type.

Privacy and access

A connection receives public events and the account information it is authorised to receive. Private account, billing, and workflow information is not made visible to unrelated clients. Treat an event as a notification of a change, not as permission to infer or access information outside the authenticated account's scope.

Freshness and recovery

Scores are eventually consistent. Score-bearing events include computed_at andscoring_version so a client can display their freshness and method context. See Scoring method for what those values mean.

Delivery is best-effort. If a client disconnects, misses an event, or needs a definitive state, re-read the relevant API resource. The API resource, rather than the event stream, is the source of truth.