Source win probability
GET
/
View as MarkdownTry in Playground →
In-game win probability as published by our data source (not DataSportsAPI’s model): home and away values for each minute of play. Limited to American football (NFL), the only sport for which the source provides it. Available on Pro, Business and Enterprise plans.
The model field always reads "source": the figure comes with the source’s match data, and we do not know how it is calculated. For our own model see /v2/fixtures/{id}/win-probability (football only, models v1 to v3). Treat it as an analytical indicator, not betting advice. minute counts playing time (15 per NFL quarter, with overtime continuing the sequence), at roughly one point per minute; individual minutes may be absent and the curve may begin at 1. The last point is just the source’s final estimate; it is not forced to 1 / 0 when the game ends. Ties are not modelled, so home + away = 1. Any other sport, or a game without source data, returns 200 with an empty series and the period figures set to null. There is no WebSocket frame for it; over REST, polling about every 30 seconds during play is enough.
Parameters
idpathrequired
fixture id issued by DataSportsAPI, a positive integer
Response
- meta
- count (number of points in series)
- errors
- 403
endpoint_not_in_plan— returned to keys on the Free and Starter plans403history_not_in_plan— the fixture predates the history your plan covers404not_found— no fixture exists with that id
Any /v2 call can also come back with one of the common errors.
curl -H "Authorization: Bearer sk_live_…" \
"https://api.datasportsapi.com/v2/fixtures/{id}/win-probability/source"Example
{ "data": { "fixtureId": 218455, "model": "source", "periodLengthMinutes": 15, "periodCount": 4, "overtimeLengthMinutes": 10,
"series": [ { "minute": 1, "home": 0.63, "away": 0.37 }, { "minute": 2, "home": 0.65, "away": 0.35 }, …,
{ "minute": 48, "home": 0.99, "away": 0.01 } ] },
"meta": { "count": 48 } }