Read a game's change stream
The same changes the WebSocket stream game:<id> carries, after a seq, oldest first.
Poll it with the last seq you applied. A game’s stream stays readable for at least 7 days
after the game ends; after that, or when after_seq is older than what is retained,
it returns 410 with code resync_required, and the client fetches the game again.
Authentication
An API key, sent as Authorization: Bearer <key>.
Path parameters
Query parameters
Response headers
Your plan’s allowance: q requests per period of w seconds. See
Rate limits.
Requests left this period after this response (r) and seconds until it resets (t). See
Rate limits.
Response
game:<game id> carries one game: the game, its live state, game roster, play groups, plays
and stats. league:<alias> carries the league’s shared data: teams, players, venues,
seasons and weeks, plus rosters, injuries, transactions and depth charts.
The stream’s last seq visible to this plan. Fewer changes than limit and the last one at head_seq means caught up.