Odds API latency — honest approach

Answer: we do not claim lower latency than any named competitor — it has not been measured as a published SLA. Instrument your own client: stamp receive time on each WS delta and compare to event clocks you trust.

Practical measurement#

1. Open Builder WebSocket; log Date.now() on every delta.
2. Optionally correlate with /v1/odds polls from the same region.
3. Watch for 4008 slow_consumer if your handler blocks.
4. Treat vendor marketing latency numbers as unverified unless you reproduce them.

Reconnect/stale guidance: stale reconnect.

Trial CTA#

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

Questions people ask#

Do you publish a latency SLA?#

No public competitor-relative SLA. Plan limits and transports are documented; timings vary by region and filters.

Does compression help?#

It can reduce payload size — compression — but it is not a latency guarantee.

Is this educational content for adults?#

Yes (18+).