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.

Provider: OddsJam AsyncAPI: v2.6.0 Spec: OddsJam (OpticOdds) Streaming API Operations: 1 Messages: 5

Channel address

/api/v3/stream/odds/{sport}

Parameters

Operations

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.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.