Odds · Pro and up
Betting odds API, kept apart from match data
The DataSportsAPI betting odds API serves pre-match and in-play sports odds from one bookmaker: every market on a fixture at /v2/fixtures/{id}/odds, and the headline market for a whole day of a sport at /v2/odds. It comes with Pro and every plan above it, and from Business up each price move is pushed live over WebSocket as well.
- Pre-match + in-play
- Opening and current prices
- Decimal and fractional
- Live moves from Business up
Football
Tennis
BasketballThe data
What an odds response holds
For each market you get its kind, period and line, whether it is in play or suspended, and its selections. Every selection carries an opening and a current price in both decimal and fractional form, the direction of the latest change and, once the match is over, whether it won.
Each market has a key that stays fixed for the whole fixture, built from the kind plus the period, line and live flag: result, result:half1, totalGoals:2.5, asianHandicap:-1.25, winner:live. Store prices under that key and every update, over REST or the stream, lands in the right place.
Markets you will see
- Result (1X2)Full time and by half
- Double chanceTwo outcomes of three
- Draw no betStake back on a draw
- WinnerSports without draws
- Both teams to scoreYes or no
- First to scoreWhich side opens the scoring
- Asian handicapQuarter lines included
- Handicap / point spreadLine on the home side
- TotalsGoals, cards, corners, points
- Next goalIn play only
- Toss winner, most sixesCricket
- A hundred or a fiftyCricket, in the match
Which markets a fixture has depends on the sport and on what the bookmaker offers for that match.
The odds endpoints
- GET
/v2/fixtures/{id}/oddsFixture oddsEvery market on one fixture: opening and current prices, suspension, settlement and who settled it.Pro and up - GET
/v2/oddsOdds by dayThe headline market for every fixture of a sport on one day, in a single request.Pro and up - GET
/v2/fixtures/{id}/odds/winningWinning oddsEach side's price against how often sides priced like that have really won.Pro and up - GET
/v2/fixtures/{id}FixtureKick-off time and status, to place each priced fixture on the right day.All plans - GET
/v2/fixtures/{id}/win-probabilityWin probabilityOur own win-probability model: a separate product from the prices.Pro and up
In code
A day of odds, then one match in depth
Start with /v2/odds?sport= to fill an odds column across a day's fixtures in one request, then call the fixture endpoint for the full market list when someone opens a match. Add date=YYYY-MM-DD for another day.
The day follows the bookmaker's own list, which can start or end a few hours away from midnight UTC. To place a fixture, take its startTime from the fixture itself rather than from the odds list.
# The headline market for every football fixture priced today
curl "https://api.datasportsapi.com/v2/odds?sport=football" \
-H "Authorization: Bearer $DATASPORTSAPI_API_KEY"
# Every market on one fixture, pre-match and in play
curl "https://api.datasportsapi.com/v2/fixtures/701210/odds" \
-H "Authorization: Bearer $DATASPORTSAPI_API_KEY"{
"data": {
"fixtureId": 701210,
"updatedAt": "2026-11-04T17:20:00.000Z",
"markets": [
{ "key": "result", "kind": "result", "name": "Full time", "period": "match",
"line": null, "live": false, "suspended": false,
"choices": [
{ "name": "1", "outcome": "home", "decimal": 1.95, "fractional": "19/20",
"openingDecimal": 2.1, "openingFractional": "11/10", "change": "down", "winning": null },
{ "name": "X", "outcome": "draw", "decimal": 4.33, "fractional": "10/3",
"openingDecimal": 3.5, "openingFractional": "5/2", "change": "up", "winning": null },
{ "name": "2", "outcome": "away", "decimal": 3.2, "fractional": "11/5",
"openingDecimal": 3.2, "openingFractional": "11/5", "change": "none", "winning": null }
],
"settledBy": null }
// … totalGoals:2.5, asianHandicap:-0.5 and the rest
]
},
"meta": { "count": 14 }
}Freshness
How fresh the prices are
Worst cases with a healthy source. Prices move fastest in play, so that is where the stream earns its place.
- Pre-match, REST
- ≤ 13 minAbout 2 minutes while anyone is following the fixture's odds:{id} channel.
- In play, REST
- ≈ 30 sNever more than 90 seconds behind while the match runs.
- In play, odds:{id}
- ≈ 1 sBusiness and Enterprise: each price change is pushed as it happens, one whole market per change.
- A day's odds
- ≤ 13 min/v2/odds for today and the days ahead. Past days can be up to 30 hours old.
- Settlement
- MinutesA few minutes after full time for the markets the source settles; up to a day for the ones we settle ourselves (settledBy "computed").
- Winning odds
- ≈ 30 sIn play. Up to 13 minutes before kick-off and up to a day after the match.
Design choice
Why odds live on their own endpoints
Prices never leak into the rest of the API. Fixtures, schedules, live scores, team and player data and every other stream channel carry no betting field at all: odds appear only on the three odds endpoints and on the odds:{id} channel. If your product must not show gambling content in some markets, or simply does not want it, your match data is odds-free by default and there is nothing to strip out.
It also keeps two very different rhythms apart. A live score changes a few times a match; an in-play price can change every few seconds. Separate endpoints let you poll or subscribe to each at its own pace, and pay for odds only on the plans and the fixtures where you need them.
Choosing
Which odds call for which screen
| Topic | /v2/odds | /v2/fixtures/{id}/odds | odds:{id} channel | …/odds/winning |
|---|---|---|---|---|
| Scope | Every priced fixture of one sport on one day | One fixture | One fixture, pushed | One fixture, both sides |
| Markets | The headline one: three-way result where draws exist, otherwise the winner | Every market the bookmaker offers | Each changed market whole, plus the keys withdrawn | Implied against actual win percentage |
| Freshness | ≤ 13 min today and ahead | ≈ 30 s in play | ≈ 1 s | ≈ 30 s in play |
| Plans | Pro and up | Pro and up | Business and up | Pro and up |
| Use it for | An odds column on a fixture list | A match page's markets tab | Live price boards | Showing where price and record disagree |
Reading prices correctly
Merge by market key
Keys stay the same for the whole fixture, so they are the safe way to match a stream frame or a fresh REST read to the market you already show.
A new line is a new market
line is the total, or the handicap of the home side. When the bookmaker moves it, the market gets a new key; drop the old one when it is withdrawn.
Decimal is 1 + fractional
Rounded to two places: 19/20 is 1.95. Show whichever format your audience reads.
Implied odds include the margin
Roughly 100 divided by the decimal price, so 1.95 implies about 51%. The outcomes of one market add up to more than 100%.
Pre-match and in-play side by side
During play the in-play market (live: true) sits next to the closed pre-match one, which keeps its final prices from before kick-off.
Empty is an answer
An empty markets list with updatedAt set to null means nothing is offered on that fixture, not that the call failed.
Check who settled it
settledBy is "source" when the bookmaker's own flags decided the market, "computed" when we settled it from the final result, and null while it is still open.
Plans
Odds come with Pro and up
Odds are premium data. Free and Starter keep all the match data; Pro adds the prices over REST, and Business and Enterprise push them as they move.
Free
Not included$0 a month
- 1,000 requests / day
- 10 requests a minute
- Last 7 days of history
No odds. The calls answer 403 endpoint_not_in_plan, which costs nothing.
Free plan detailsStarter
Not included$49 a month
- 250,000 requests / month
- 120 requests a minute
- Last 30 days of history
No odds, and the same free-of-charge refusal. Every other match endpoint answers.
Starter plan detailsPro
Included$199 a month
- 1,000,000 requests / month
- 600 requests a minute
- Last 6 months of history
All three odds endpoints over REST: every market per fixture, a day's main market and winning odds.
Pro plan detailsBusiness
Included$1,500 a month
- 5,000,000 requests / month
- 3,000 requests a minute
- Last 12 months of history
Everything on Pro, plus every price change pushed on the odds:{id} channel.
Business plan detailsEnterprise
Included$2,500 a month
- 10,000,000 requests / month
- 6,000 requests a minute
- Full history
The same prices and the same odds:{id} pushes as Business, with the highest volume and the most live connections.
Enterprise plan details
The prices come from a third party and are provided for information only. They are neither betting advice nor an invitation to place a bet.
Questions
Betting odds API, answered
Anything else? The full FAQ covers quota, plans and the data in general.
Which bookmaker do the odds come from?
A single bookmaker, the same for every fixture, supplied through our data source, with an opening and a current price for every selection. Since 2026-11-13 the responses no longer name it: the bookmaker object was removed and the prices carry no provider identity. Prices from different books are never blended, so every number in a market comes from one place.
Does the odds API include live, in-play prices?
Yes. Once a match starts, the in-play version of a market appears with live: true and a key ending in :live, next to the closed pre-match market, which keeps its last prices from before kick-off. Over REST, in-play prices are about 30 seconds old; on Business and Enterprise the odds:{id} channel pushes each change within about a second.
Are betting odds included on the free plan?
No. The three odds endpoints come with Pro, Business and Enterprise. On Free and Starter they answer 403 endpoint_not_in_plan, and that refusal is not counted against your quota.
Which sports and markets are covered?
Any sport the bookmaker prices: pass its slug to /v2/odds?sport=. The markets follow the sport, so football has the three-way result and Asian handicaps, basketball point spreads and points totals, cricket the toss and most sixes. A fixture the bookmaker does not price, which is typical of minor leagues and matches far ahead, returns an empty markets list.
How are markets settled in the data?
winning stays null until a market is settled and then marks the winning selections; settledBy on every market says who did it. Most markets are settled by the source a few minutes after the final whistle (settledBy: "source"). Football Asian handicaps and card totals are two it always leaves open, so since 2026-11-12 we settle them ourselves wherever the final result decides them beyond doubt (half-line handicaps, judged on the score after regular time; half-line card totals, when every card shown was a yellow), marked "computed" and never over a flag the source has set. Any other market the source leaves open keeps winning: null for good.
Are the odds betting tips or predictions?
No. The prices come from a third party and are shown for information only. They are not betting advice, a prediction or an offer to place a bet. Our own view of a match is the win-probability model, from Pro up, a separate endpoint that never mixes with prices.
Keep reading
More of the sports data API
Other ways in
- Live scores APIEvery match in play in one call, with score, status and clock current to the second.Read more
- Real-time sports APIA WebSocket with snapshots, deltas and replay, plus signed webhooks, from the Business plan up.Read more
- Free sports APIThe core match data for all 24 sports on the Free plan, with no card to sign up.Read more
- Historical sports dataFinished seasons over REST, back to 1920 on Enterprise, or as JSON, CSV and Parquet season files.Read more
- Sports statistics APIMatch stats by period, player and team season totals, xG, ratings and league leaderboards.Read more
Sport by sport
Prices where you want them, and nowhere else.
Build on the free match data today; odds switch on with Pro.







