AiOdds Feed Integration Demo

From initial odds sync to live WebSocket updates and Backup Safe Mode.

This demo follows the AiOdds documentation flow: HTTPS API for sports, fixtures, markets, bookmakers, and odds snapshots; MQTT over WebSocket for live match and odds updates; Monitoring for operator validation; Backup Safe Mode for raw bookmaker no-data protection.

HTTPS API api.aiodds.com

Realtime feed MQTT v5

Topics match / odds

Mode Primary

Load basic data

Sports, tournaments, fixtures, markets, bookmakers, and odds snapshots through HTTPS JSON APIs.

Map identifiers

Store AiOdds IDs against internal sportsbook models for events, markets, selections, and books.

Subscribe live

Use MQTT over WebSocket topics such as match/<user> and odds/<category>/<user>.

Validate operation

Compare feed behavior with Monitoring: odds movement, suspended markets, alerts, and bookmaker filters.

Bookmaker Odds

Live market board

MQTT streaming

topic: odds/1/operator category: In-play backup flag: 0 latency: 128ms

Transport health

HTTPS snapshots vs WebSocket feed

700ms tick

Initial sync

Data foundation

Sports50+

TournamentsMapped

Fixtures120k/mo

Markets2,000+

BookmakersFiltered

SnapshotsRecoverable

Developer proof

Payloads should prove both feed coverage and continuity state.

Operators need the standard sports betting model first: sport, tournament, fixture, bookmaker, market, selection, odds, status, and timestamp. Continuity fields then show whether the market is primary, protected, or running on managed fallback, with AiOdds `backup` semantics marking alternative odds when raw bookmaker data is unavailable.

Backend-only credentials IP allowlist ready Retry + reconnect Resubscribe topics Stale data alerts