AsyncAPI channel · OddsJam
· OddsJam (OpticOdds) Streaming API
/api/v3/stream/odds/{sport}
Server-Sent Events stream of odds changes, suspensions, and (optional) fixture status updates for a sport. Filterable by sportsbook (required, up to 5 per connection), league, fixture_id, market, is_main, is_live, and odds_format. Up to 10 leagues per connection is recommended.
sport — Sport slug (e.g. basketball, football, baseball, soccer, tennis, golf, politics). Path parameter; not exhaustively enumerated in the public docs.
Operations
subscribe
streamOdds
Receive odds, locked-odds, ping, connected, and fixture-status events.
Messages
connected
Confirms successful SSE stream initialization.
Content-Type: text/event-stream
ping
Periodic keepalive (approximately every 5 seconds) carrying a server timestamp for drift detection.
Content-Type: text/event-stream
odds
Fires when an odd is posted or unsuspended.
Content-Type: text/event-stream
locked-odds
Fires when odds are suspended or removed; payload uses the same Odd schema.
Content-Type: text/event-stream
fixture-status
Notifies of game status or start time changes. Requires the `include_fixture_updates=true` query parameter.
Content-Type: text/event-stream
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.