docs(api)!: drop game_state from EV/arb/low-hold reference#195
Merged
Conversation
Live game state (scores, period, clock) is exclusive to /api/v1/gamestate and the gamestate stream channel. Remove the game_state row from sample payloads + schema tables on the EV, arbitrage, and low-hold reference pages, and add a breaking-change callout pointing readers at gamestate. BREAKING CHANGE: clients that read game_state off opportunity rows must fetch /api/v1/gamestate (or subscribe to /api/v1/stream/gamestate) and join by event_id. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4 tasks
Mlaz-code
added a commit
that referenced
this pull request
May 2, 2026
New page at /en/streaming/single-connection covering how to cover multiple sports, leagues, books, markets, events, and odds + every opportunity type on a single SSE or WebSocket connection — instead of opening parallel sockets per filter. Frames the guidance against the new 1-stream-per-key cap (newer-wins displacement on second connect) and points fleet/multi-process users to the per-key `maxStreams` Unkey override for Enterprise. Five concrete patterns: multi-sport via comma-joined leagues, `channel=all` for odds + opportunities, N-event tracking via comma-joined event IDs, per-book/market splits, dynamic re-subscription on WebSocket. Ends with a server-side cost rationale and migration checklist for users moving off a multi-stream architecture. Page was drafted in a parked tdev session (8-day-old branch docs/remove-game-state-from-opportunities, already merged via #195) and reviewed clean — cross-links resolve, Nextra components match the rest of the streaming/ section.
4 tasks
Mlaz-code
added a commit
that referenced
this pull request
May 7, 2026
Live game state (scores, period, clock) is exclusive to /api/v1/gamestate and the gamestate stream channel. Remove the game_state row from sample payloads + schema tables on the EV, arbitrage, and low-hold reference pages, and add a breaking-change callout pointing readers at gamestate. BREAKING CHANGE: clients that read game_state off opportunity rows must fetch /api/v1/gamestate (or subscribe to /api/v1/stream/gamestate) and join by event_id. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Mlaz-code
added a commit
that referenced
this pull request
May 7, 2026
New page at /en/streaming/single-connection covering how to cover multiple sports, leagues, books, markets, events, and odds + every opportunity type on a single SSE or WebSocket connection — instead of opening parallel sockets per filter. Frames the guidance against the new 1-stream-per-key cap (newer-wins displacement on second connect) and points fleet/multi-process users to the per-key `maxStreams` Unkey override for Enterprise. Five concrete patterns: multi-sport via comma-joined leagues, `channel=all` for odds + opportunities, N-event tracking via comma-joined event IDs, per-book/market splits, dynamic re-subscription on WebSocket. Ends with a server-side cost rationale and migration checklist for users moving off a multi-stream architecture. Page was drafted in a parked tdev session (8-day-old branch docs/remove-game-state-from-opportunities, already merged via #195) and reviewed clean — cross-links resolve, Nextra components match the rest of the streaming/ section.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
game_staterow from sample payloads + schema tables on the EV, arbitrage, and low-hold reference pages./api/v1/gamestateand thegamestatestream channel.Why
The server is dropping the
game_stateobject from/api/v1/opportunities/{ev,arbitrage,low_hold}— see Mlaz-code/sharp-api-go#61. Live state is exclusive to the gamestate endpoint going forward.Test plan
/en/api-reference/opportunities-ev,/opportunities-arbitrage,/opportunities-low-holdThis should land before the server PR so users see the warning before the field disappears.
🤖 Generated with Claude Code