Overview
Markets are the core data model in V2. Each market represents a type of bet (moneyline, spread, total, player props, etc.) with participants, lines, and prices from each sportsbook.Default Market IDs
When you call event endpoints without specifyingmarket_ids, the API defaults to 1,2,3:
To get player props, team totals, or other market types, you must explicitly pass their IDs. For example,
market_ids=29 for Player Points or market_ids=94 for Team Totals. See the full Market IDs reference.For a visual breakdown of how markets, participants, lines, and prices nest together, see the Data Model. For the complete list of market IDs and sport availability, see Market IDs. For delta-based polling of market prices, see the Efficient Polling guide.
Endpoints
GET /api/v2/markets — List all market definitions
GET /api/v2/markets — List all market definitions
Returns every canonical market definition with its ID, name, period info, and whether the line value represents a participant name.This is a reference endpoint — it returns the market catalog, not live prices. Use it to build a mapping of market IDs to display names.
Response fields
Example Response
GET /api/v2/markets/delta — Market price delta feed
GET /api/v2/markets/delta — Market price delta feed
GET /api/v2/markets/history — Price history by market line price IDs
GET /api/v2/markets/history — Price history by market line price IDs
GET /api/v2/markets/participants — Get market participants
GET /api/v2/markets/participants — Get market participants
GET /api/v2/events/{eventID}/markets — Available markets for an event
GET /api/v2/events/{eventID}/markets — Available markets for an event
GET /api/v2/events/{eventID}/markets/history — Market history for an event
GET /api/v2/events/{eventID}/markets/history — Market history for an event
GET /api/v2/events/{eventID}/markets/{marketID}/history — Line chart data for a specific market
GET /api/v2/events/{eventID}/markets/{marketID}/history — Line chart data for a specific market
Returns time-series price data suitable for charting line movement on a single market. More granular than the general history endpoint.
Parameters
Example Response
The chart-optimized response groups data points intoseries keyed by affiliate ID. Each point uses shorthand fields: t (timestamp), p (price), and c (closed_at, empty string if still active).Available Markets by Sport and Date
You can also discover which markets are available for a sport on a given date:Market Data Model
Each market in an event response follows this structure:prices object is keyed by affiliate_id (sportsbook). A price value of 0.0001 indicates the line is off the board.