Live odds push vs REST polling

Answer: polling /v1/odds every N seconds misses in-between ticks and burns quota. A WebSocket sends each change once. Use Builder for push; Free REST is delayed 30 s; Hobby is real-time REST without WS.

Rule of thumb#

• Research dashboards / Sheets → REST may be enough.
• Steam, live trading, bots → WebSocket.

Keyword deep-dive: /odds-websocket-api.

Trial CTA#

Builder (€99/mo) for WebSocket and closing history. 3-day trial; card required, charged after day 3 unless cancelled. Free REST: signup. Related: answers hub, docs.

Related: Webhook vs WebSocket.

Questions people ask#

Is push always lower latency?#

We do not publish head-to-head latency vs named competitors. Measure tick → your handler.

Can I mix both?#

Yes — WS for live sports you trade, REST for closings and backfills.

Is this educational content for adults?#

Yes (18+).