Optimize Response Speed and Latency

We balance making as much data available as possible with letting you fetch it quickly. This guide covers the parameters that keep responses small and fast.

Use the oddID parameter

• The most common cause of slow responses is fetching every market on many events at once.
• Use oddID on /events to fetch only the markets you need — a comma-separated list of oddIDs (see the markets browser).
• Set includeOpposingOdds=true to also include the other side of each oddID you list.
• Replace the playerID portion of any oddID with PLAYER_ID to fetch that market across all players.

Example: disposals-LACHIE_NEALE_1_AFL-game-ou-under is one player's disposals under. To fetch every player's disposals, both sides:

oddID=disposals-PLAYER_ID-game-ou-under&includeOpposingOdds=true

Use bookmakerID

bookmakerID=sportsbet,tab trims every byBookmaker block to the books you show.

One league at a time

A full-league page is a few hundred KB; a multi-league page is several. Page at 100 and cache by info.lastUpdatedAt — nothing changes between source refreshes (~2 min).

Leave alt lines off

includeAltLines=true can multiply the payload; ask only when you need them.

Don't poll faster than the source

A 429 is still a counted request. Poll every 2–5 minutes.