LIVE ODDS API · WEBSOCKET + REST

Live Odds API for Real-Time Sportsbook Data

Connect your sportsbook to real-time betting odds, scores, market status and event updates through WSGaming’s Live Odds API. Use WebSocket for continuously changing in-play data and REST for snapshots and supporting event information across Asian and international sports markets. Need the complete wagering lifecycle? Our Sportsbook API extends the integration to sportsbook transaction and operational workflows.

// Live odds stream example
// Connect once and process incoming odds updates
const ws = new WebSocket( ‘wss://api.wsgaming.com/v1/odds/stream’ );

ws.on( ‘message’, (event) => {
  const update = JSON.parse(event.data);

  // Process the latest market update
  updatePrice(update);
});
The API

What Is the Live Odds API ?

The Live Odds API is a technical interface for delivering continuously updated betting prices, scores, market status and event data into sportsbooks, trading dashboards and betting applications.

For rapidly changing in-play markets, WebSocket can maintain a persistent connection and push new market information as updates occur. REST endpoints are better suited to event discovery, snapshots and supporting reference data.

This technical data layer supports our sportsbook real-time odds product. Operators that also need bet validation, ticket placement, settlement, wallet connectivity and broader sportsbook workflows should use the WSGaming Sportsbook API .

Integration Flow

How the Live Odds API Works

The API is designed to move structured market updates from WSGaming’s sportsbook infrastructure to the operator’s betting interface with as little unnecessary polling as possible.

01

Event Data

Match, score and market information enters the sportsbook data infrastructure for processing.

02

Data Validation

Event and market information is checked before updated betting data is distributed to clients.

03

Market Update

New prices, market states and suspension information are prepared for delivery.

04

WebSocket Push

Relevant updates are pushed through a persistent connection instead of waiting for another polling cycle.

05

Sportsbook Display

The operator’s frontend can refresh the affected market, event view or betting interface.

Core Capabilities

Built for Real-Time Betting Data Delivery

The Live Odds API focuses on the technical data layer: real-time market updates, event information, market states and regional odds formats. Broader sportsbook operations remain within the Sportsbook API .

Fast Market Updates

Designed for time-sensitive sportsbook environments where new prices, event changes and market states need to reach the betting interface quickly and consistently.

WebSocket + REST

Use persistent WebSocket connections for changing in-play markets and REST endpoints for event snapshots, discovery and supporting reference information.

Broad Sports Coverage

Support sportsbook interfaces across football, basketball, tennis, cricket, esports, badminton, table tennis and other available sports and competitions.

Market Status Updates

Deliver changing market states alongside pricing data so operator interfaces can react appropriately when a market becomes unavailable or resumes.

Up to 10 Markets per Event

Available market types can include match winner, handicap, totals, BTTS, correct score, half/full-time and Asian Handicap depending on sport and event coverage.

Regional Odds Formats

Support common sportsbook formats including Decimal, American, Hong Kong, Malay and Indonesian presentation formats where available.

Delivery Methods

WebSocket vs REST for Live Odds

Both methods have a role in sportsbook integrations. WebSocket is suited to rapidly changing live markets, while REST is useful for information that can be requested when needed.

Integration
WebSocket
REST
Connection
Persistent
Request based
Update Model
Server push
Client request
Best Use
Live / in-play odds
Snapshots & reference data
Repeated Polling
Not required
Required for refreshed data
Typical Sportsbook Use
Price & market updates
Events, schedules & snapshots
API Surface

Live Odds API Endpoints

The examples below illustrate the type of real-time betting and event data available through the integration. Final endpoint definitions and technical documentation are provided during onboarding.

WSS /v1/odds/stream Subscribe to real-time odds and market updates for supported events and competitions.
GET /v1/events/live Retrieve currently in-play events with available market and event information.
GET /v1/events/upcoming Retrieve upcoming events and available pre-match market information.
GET /v1/events/{id}/markets Retrieve available markets for a selected event.
GET /v1/events/{id}/status Retrieve event state, score changes, suspension status and market availability.
GET /v1/results/{event_id} Retrieve event results and supported outcome data after the event is completed.

Need bet placement, ticket validation, settlement, wallet connectivity or broader sportsbook operations? Those functions belong to the complete WSGaming Sportsbook API .

Regional Integration

Live Odds API Built for Asian Sportsbooks

WSGaming’s sportsbook technology supports the market structures and odds presentation requirements commonly used by operators serving Asian and Southeast Asian audiences.

Markets

Asian Handicap

Deliver Asian Handicap and other supported sportsbook markets through structured event and market data.

Formats

Regional Odds Formats

Support presentation formats such as Malay, Hong Kong and Indonesian odds alongside international formats.

Sports

Regional Sports Demand

Support betting products across football, basketball, badminton, table tennis, esports and other available sports.

Integration

Multi-Market Architecture

Use one technical integration to support sportsbook frontends targeting multiple Asian or Southeast Asian markets.

Integration Security

API Authentication & Access Control

Production integrations require controlled access, authenticated connections and operator-specific configuration. Final security requirements are supplied with the technical documentation during onboarding.

API Authentication

Authorized credentials control access to operator integration environments.

Request Validation

REST requests can be validated using the authentication method defined for the operator environment.

WebSocket Access

Persistent live-data connections use authenticated operator access before streaming begins.

Operator Controls

Access policies and environment-level controls can be configured according to the operator’s integration requirements.

Choose the Right API

Live Odds API vs Sportsbook API

The Live Odds API focuses on real-time sportsbook data. The Sportsbook API extends beyond data delivery into the wider betting lifecycle.

Capability
Live Odds API
Sportsbook API
Live odds streaming
Yes
Yes
Pre-match market data
Yes
Yes
Scores & event data
Yes
Yes
Bet placement
No
Yes
Settlement workflow
No
Yes
Wallet integration
No
Yes
Broader sportsbook workflow
Data layer
Full integration
Frequently Asked

Questions About the Live Odds API

Common technical and product questions from sportsbook operators and integration teams.

How quickly does the Live Odds API deliver updates? +

The API is designed for time-sensitive in-play sportsbook environments where market and event updates need to be delivered quickly. Exact performance can depend on the integration environment, connection location and the type of data being delivered. For the commercial real-time odds product, see our Sportsbook Real-Time Odds page.

What’s the difference between the Live Odds API and Odds Feed Solution? +

The Live Odds API focuses on the technical interface used to receive real-time betting and event data. The Odds Feed Solution is the broader commercial odds-data product for operators that need an ongoing feed solution, integration support and service configuration.

Should I use WebSocket or REST for live odds? +

WebSocket is better suited to rapidly changing in-play prices because the connection remains open and updates can be pushed as they occur. REST is useful for event discovery, snapshots and data that does not require continuous server-push updates.

How is access to the API authenticated? +

Production access is provided through authenticated operator credentials and environment-specific security controls. Exact authentication requirements are included in the technical documentation provided during onboarding. Contact our integration team for the current specification.

What’s the difference between the Live Odds API and Sportsbook API? +

The Live Odds API focuses on delivering betting prices, scores, market status and event updates. The Sportsbook API extends beyond data delivery into betting operations such as bet validation, ticket placement, settlement, wallet connectivity and broader sportsbook workflows.

Which odds formats can the integration support? +

WSGaming supports sportsbook environments that use international and Asian odds formats, including Decimal, Hong Kong, Malay, Indonesian and other supported presentation formats depending on the operator configuration.

What happens when a live market is suspended? +

Market-status information can be used by the operator interface to temporarily disable or hide affected markets. When the market becomes available again, the sportsbook frontend can process the refreshed market state and price.

How do I start a Live Odds API integration? +

Contact WSGaming to discuss your sportsbook, required sports and markets, target regions and technical environment. The integration team can then provide the relevant technical documentation and onboarding requirements.

Integrate Live Odds in Real Time

Connect your sportsbook or betting application to live odds, scores, market status and event data through a technical integration built for modern sportsbook environments.