Skip to content

Livematches in play

Demo: Matchboard, opens in a new tab
Docs v2

Tracking data

Player tracking

GET

/v2/fixtures/{id}/tracking/players

Enterprise

View as MarkdownTry in Playground →

Player tracking for NBA games, since 2026-11-13 (Enterprise only): all ten players on court plus the ball, at five frames per second, ordered by frame — who holds the ball, the game clock and the shot clock, and for every player the name, shirt number, side and position. With no cursor you get the newest frames (the last 30 seconds unless you set limit); with a cursor, the page that follows it.

Only NBA games carry it — TrackingSummary.players tells you whether a fixture does — and the list is empty for every other fixture. Positions use the same court frame as the rest of the basketball data: x runs 0–100 along the court and y 0–100 across it, with the home side shooting towards x = 100 in all periods (the sides swap ends at half-time; the frame does not move). Which way each team plays is inferred each period from where its shots are taken, so a live frame from the first seconds of a game, before anyone has shot, can come out mirrored; read it again later and it is corrected. There are no frames during half-time. ball.height is in metres (the rim sits at 3.05). Frames reach us about 1–2 seconds behind play, five per second sharing one at, so play them back by frame, 0.2 s between each. Only games recorded live have frames. For the live feed, take the playerFrame frames on tracking:{id}.

Parameters

id

pathrequired

fixture id issued by DataSportsAPI, a positive integer

after

query

frames that come after this frame counter (PlayerFrame.frame; that counter excluded) — meta.next from the previous page

since

query

frames received after this instant (ISO-8601 with any offset; that instant excluded); ignored when after is sent

limit

query

frames per page, 1–3000 (150 if omitted, which is 30 seconds)

fps

query

5 for every frame (the default) or 1 for one frame per second

Response

meta
count, hasNextPage, next (the after value for the following page, or null)
errors
400 bad_request — after, since, limit or fps is malformed403 endpoint_not_in_plan — returned on every plan except Enterprise404 not_found — DataSportsAPI never issued this 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}/tracking/players"
Example
{ "data": [
    { "frame": 731569, "at": "2026-11-13T03:00:06.453Z", "period": 4, "clock": 541, "shotClock": 20, "running": true,
      "possession": { "side": "home", "player": { "name": "John Doe", "shirtNumber": 9, "side": "home" } },
      "ball": { "x": 44.45, "y": 86.75, "height": 0.9 },
      "players": [ { "side": "home", "name": "John Doe", "shirtNumber": 9, "x": 43.86, "y": 90.03 }, … ] }, … ],
  "meta": { "count": 150, "hasNextPage": false, "next": null } }