Event-driven channels

OddsJam

OddsJam's Sports Betting API offers real-time betting odds from 100+ sportsbooks including player props, alternate markets, injury data, schedules, rankings, and scores for sports betting applications.

6 channels across 1 AsyncAPI spec · Provider profile

Channels

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

Server-Sent Events stream of copilot odds (new/modified), locked copilot odds, settled copilot odds, and optional fixture status changes. Same filtering knobs as the standard odds stream.

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_m

OddsJam (OpticOdds) Streaming API
/api/v3/stream/results/{sport}

Server-Sent Events stream of live scores, game outcomes, and player performance data. OpticOdds recommends a separate connection per league rather than passing multiple leagues per request.

OddsJam (OpticOdds) Streaming API
copilot-queue

RabbitMQ queue delivering copilot odds updates. The queue name is returned by the REST control endpoint `POST /api/v3/copilot/queue/start`. Lifecycle is also managed by `POST /api/v3/copilot/queue/sto

OddsJam (OpticOdds) Streaming API
copilot-results-queue

RabbitMQ queue delivering copilot results updates. Queue name is issued by `POST /api/v3/copilot/results/queue/start`; lifecycle is managed via `POST /api/v3/copilot/results/queue/stop` and `GET /api/

OddsJam (OpticOdds) Streaming API
fixtures-results-queue

RabbitMQ queue delivering fixture results updates. Queue name is issued by `POST /api/v3/fixtures/results/queue/start`; lifecycle is managed via `POST /api/v3/fixtures/results/queue/stop` and `GET /ap

OddsJam (OpticOdds) Streaming API