Skip to main content1) Invalid apiKey / can’t login
Symptoms:
- server replies with
{ "type": "error", ... }
- immediate disconnect after connect
Fix:
- verify key format (32 hex chars)
- verify environment variable / secrets are loaded correctly
2) “I’m connected but receive nothing”
Most common causes:
sportIds / tournamentIds filters too narrow- you subscribed to channels you don’t have access to (server will intersect)
- you’re expecting live but your feed is pregame-only (or vice versa)
Fix:
- try a minimal login (no filters) and confirm you receive any UPDATE frames
- then add filters incrementally
3) Odds/bookmakers channels not received (bookmaker gating)
Symptoms:
- you receive
fixtures / scores but not odds / bookmakers
Cause:
odds, oddsFutures, bookmakers, bookmakersFutures are bookmaker-gated
Fix:
- include
bookmakers in login OR ensure your apiKey has allowed bookmakers
- confirm requested bookmakers intersect what the server is sending
4) Binary decoding issues (receiveType: "binary")
Symptoms:
- unreadable frames
- JSON parse errors on UPDATE frames
Fix:
- set
receiveType: "json" first
- if using
binary, decode MessagePack for UPDATE frames
- control frames may still arrive as JSON bytes depending on your server behavior
5) Disconnects under load (backpressure / queue full)
Symptoms:
- periodic disconnects during peak update bursts
Fix:
- process messages faster (avoid blocking handlers)
- buffer to a queue and batch work
- scale consumers / shard across multiple connections (respect the max connections per apiKey)