Skip to content

Livematches in play

Demo: Matchboard, opens in a new tab
Docs v2

Tracking data

Tracked events

GET

/v2/fixtures/{id}/tracking/events

Enterprise

View as MarkdownTry in Playground →

Every tracked event with its position, in the order of play, on Enterprise only — football passes from start to end point, set pieces, shots, cards, fouls, substitutions and the attacking flow; tennis serves, faults and points (each with the game score after it), plus where the ball and the players were; basketball shots and where they were taken, rebounds, fouls and turnovers. Up to 1,000 per page, optionally narrowed to one type or to events after an instant.

key never changes, and trackedEvent frames use the identical key for the same event. The clock fields depend on the sport — minute and second for football, set and game for tennis, period for basketball. player, assist, playerIn and playerOut stay null if the source gives no name or the squad list lacks that player. Clock housekeeping entries are left out. During a live football match you receive flowAttack / flowDangerousAttack / flowBallSafe (side is the team in possession and position is where the ball is; read together they give the current state of play), possessionChange (without a side), goal, attemptAtGoal, corner, freeKick, throwIn, goalKick, yellowCard, redCard, substitution, possibleGoal / possibleCorner and more, around 18 a minute; passes are added by the post-match read. Ice hockey has no tracked events (use the timeline instead), and most basketball matches have none until the post-match read.

Parameters

id

pathrequired

fixture id issued by DataSportsAPI, a positive integer

type

query

return only this event type, written in camelCase (pass, attemptAtGoal, goal, serve, point, ballSituation, threePointer, …)

since

query

return only events after this instant (ISO-8601 with any offset; the instant itself is excluded)

page

query

zero-based page of the filtered list, 0–999 (defaults to 0)

Response

meta
page, count, total (after filtering), hasNextPage
errors
400 bad_request — a malformed type, since or page403 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/events"
Example
{ "data": [
    { "key": "5f0c2a9e41d7b3c8", "type": "pass", "at": "2026-11-11T21:04:09.568Z", "side": "home", "minute": 79, "second": 4785,
      "period": null, "set": null, "game": null, "position": { "x": 42, "y": 2, "z": null }, "endPosition": { "x": 58, "y": 15, "z": null },
      "player": { "name": "John Doe", "shirtNumber": 8, "side": "home" }, "assist": null, "playerIn": null, "playerOut": null,
      "outcome": "complete", "goalType": null, "serving": null, "gameScore": null, "pointOutcome": null, "shots": null }, … ],
  "meta": { "page": 0, "count": 1000, "total": 2215, "hasNextPage": true } }