Live Odds API — Power Real-Time Betting With One Integration.
Stream pre-match and in-play odds straight into your front-end. Sub-400ms latency, WebSocket-first, 100+ sports, 10 markets per match — all from the same engine powering the WS Gaming sportsbook platform trusted across Asia. Integrate once with our odds feed solution and ship in days, not quarters.
const ws = new WebSocket(‘wss://api.wsgaming.com/v1/odds/stream’);
ws.on(‘message’, (event) => {
const odd = JSON.parse(event.data);
// {
// match_id: “epl_4821”,
// market: “1X2”,
// odds: { home: 1.85, draw: 3.40, away: 4.20 },
// ts: 1715847291842
// }
updatePrice(odd);
});
What is the Live Odds API?
The Live Odds API is a RESTful + WebSocket interface that delivers real-time betting odds, scores, and event data into any platform. Operators use it to power in-play betting, live ticker feeds, second-screen apps, and trader dashboards — all from a single integration with WS Gaming’s sportsbook infrastructure.
Unlike pull-based feeds where your server polls for updates, our WebSocket layer pushes new prices the moment they change. That’s the difference between odds that move with the match and odds that lag the action — exposing your book to arbitrage. The API runs on the same engine as our sportsbook real-time odds product, so you get the same sub-400ms latency every operator on our platform benefits from.
This page covers the architecture, key endpoints, and what separates a tier-1 odds API from the dozens of slower providers in the market.
Everything your platform needs — in one stream.
Six capabilities that distinguish a serious live betting API from a glorified data dump. Each is standard on every WS Gaming integration.
Sub-400ms Latency
Tier-1 data capture, AI pricing, risk approval, and publish — all within 400ms end-to-end. Built into every endpoint of our odds feed solution.
WebSocket First
Persistent connection, server-push updates, automatic reconnect with backfill. REST endpoints available for snapshots, history, and settlement queries.
100+ Sports
Football, basketball, tennis, cricket, esports, table tennis, badminton, MMA, F1 — every major league and most niche markets covered globally.
Risk-Aware Pricing
Every price ships with risk flags, suspension states, and confidence scores. Build smarter trader dashboards and auto-suspend on the client side.
10 Markets / Event
Match winner, handicap, totals, BTTS, correct score, half/full-time, Asian handicap — all from one event subscription. Standard on our sports betting software.
Multi-Format Odds
Decimal, fractional, American, Hong Kong, Malay, Indonesian, Euro — switch on a per-client basis. No conversion logic on your end.
Key endpoints.
A minimal example of what’s available. Full reference is shared with operators after onboarding.
/v1/odds/stream
Subscribe to real-time odds updates for any combination of sport, league, or match.
/v1/events/live
Snapshot of all currently in-play events with active markets and current prices.
/v1/events/upcoming
Pre-match events with kickoff times, opening lines, and movement history.
/v1/events/{id}/markets
All markets available for a specific event, including specials and player props.
/v1/bets/place
Submit a bet ticket with price-change acceptance rules and auto-settlement enabled.
/v1/settlements/{bet_id}
Retrieve final settlement details, payout, and result verification data.
Questions about the Live Odds API.
What operators and developers ask most often before integrating.
How fast does the API push odds updates? +
End-to-end target is under 400ms — from real-world event to your client receiving the new price. We hit this consistently because we control the full stack: data capture, AI pricing, risk approval, and publish. See the full architecture on our real-time odds page.
What’s the difference between this and the Odds Feed Solution? +
The Live Odds API is the technical interface; the Odds Feed Solution is the productized package — including SLAs, support, and the back-office tools that go with it. Same engine, different layer of abstraction.
Can I use REST instead of WebSocket? +
Yes, but it’s not recommended for live odds. REST polling has minimum 1-2s latency just from network round-trips, which is too slow for in-play. Use REST for snapshots, settings, and reports; use WebSocket for live price streams.
What authentication does the API use? +
API keys with HMAC signing for REST, JWT tokens for WebSocket connections. Operator-specific IP whitelisting and rate limits are configured per environment. Full security spec shared during onboarding via our team.
Does the API include settlement and bet placement? +
Yes. The full Sportsbook API covers the lifecycle: odds streaming, bet validation, ticket placement, settlement, and payout. Operators running on our white label sportsbook get all of this without lifting a finger.
How are different odds formats handled? +
The API supports decimal, fractional, American, Hong Kong, Malay, Indonesian, and Euro formats. Set the default at the API key level or override per request. No conversion math on your end.
What if a market gets suspended mid-stream? +
Suspended markets push a status update with the suspension reason (penalty kick, VAR review, injury, manual). The market resumes with a fresh price once the situation clears. Build your UI to greyscale or hide suspended markets accordingly.
How do I get started with integration? +
Reach out via our contact page. Standard onboarding includes a sandbox environment, full API docs, sample code in JS/Python/PHP, and 1-on-1 integration support from WS Gaming engineers.
One API. Every match, every market.
Plug into the same odds engine powering operators across Malaysia, Vietnam, Thailand, and beyond. Sandbox access in 24 hours.