Tracking summary
GET
/
View as MarkdownTry in Playground →
Which tracking data a fixture holds (Enterprise only): its sport and coordinate frame, a final flag once the match is over, a complete flag once the post-match read is in, the counts of ball frames, tracked events and timeline events, and whether the players were tracked too (players, NBA games, since 2026-11-13).
Arriving live: football’s goals, shots, cards, substitutions, set pieces and flow of play, about 9 seconds after they happen (roughly 15 at most), and the timelines of basketball, ice hockey and darts, about 5 seconds behind (timelineEvent frames on the WebSocket). Football’s passes and most event details, and the basketball events, wait for the post-match read, which lands between a few minutes and an hour after the end: complete turns true then, a trackingStatus frame announces it on the WebSocket, and that is the moment to fetch the events and the timeline again. The ball track exists only as recorded during play — a frame the source did not capture live is never filled in later.
Parameters
idpathrequired
fixture id issued by DataSportsAPI, a positive integer
Response
- data
TrackingSummary- errors
- 403
endpoint_not_in_plan— returned on every plan except Enterprise404not_found— DataSportsAPI never issued this id404no_data— this fixture is not followed by the source (its sport or league has no tracking)
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}/tracking"Example
{ "data": { "fixtureId": 701240, "sport": "football", "coordinates": "pitch", "final": true, "complete": true,
"startedAt": "2026-11-11T19:44:12.000Z", "ballFrames": 1384, "events": 2215, "timelineEvents": 0, "players": false } }