Tracking data

Tracking summary

GET/v2/fixtures/{id}/trackingEnterprise

What tracking data a fixture has: its sport and coordinate frame, whether the match is over (final) and its post-match data read (complete), how many ball frames, tracked events and timeline events there are, and whether it has player tracking (players: NBA games, since 2026-11-13). Enterprise plan only.

Football’s flow of play, set pieces, shots, goals, cards and substitutions arrive live (about 9 seconds after they happen, up to about 15), and so do the basketball, ice hockey and darts timelines (about 5 seconds; timelineEvent frames on the WebSocket); football’s passes and most details, and basketball’s events, come with the post-match read, minutes to an hour after the end (complete: true; a trackingStatus frame says so on the WebSocket) — re-read the events and the timeline then. The ball track is recorded live only: a frame the source did not record live is not added later.

Parameters

pathrequired

our numeric id (positive integer)

Response

data: TrackingSummary
errors: 403 endpoint_not_in_plan — every plan but Enterprise404 not_found — an id we never issued404 no_data — the source does not track this fixture (a sport or league it does not cover)

Every /v2 call can also answer the common errors.

Try it →

$ curl -H "Authorization: Bearer sk_live_…" \
    "https://api.sportsapi.app/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 } }