PlayersEndpoint 55 of 116
Player fixtures
https://api.datasportsapi.com/
- Plan
- All plans
- Auth
Bearer dsa_live_…- Parameters
- 1 required · 1 optional
- Returns
PlayerFixture[]
One page of the player’s most recent fixtures, across every team they appeared for; since 2026-10-24 each page lists the newest first.
Page 0 opens with any fixtures not yet started, soonest first (since 2026-10-27; earlier, a player with two matches ahead saw the later one first), then continues with the rest newest first.
Every fixture includes playerMatch: the side the player was on, whether they remained on the bench, their rating, their match statistics (minutes in football; box scores in basketball and ice hockey) and their goals, assists and cards.
Worth knowing
A known player with no fixtures at the source gets 200 and an empty array. playerMatch.statistics shares its per-player keys with the lineups.
01Parameters
idpathRequiredDataSportsAPI player id, a positive integer
pagequeryOptionalzero-based page number, a whole number from 0 to 50; the default 0 holds the most recent fixtures
02Request
The same call from the command line and each SDK. The SDK lines assume a client created with your key; left out, it is read from DATASPORTSAPI_API_KEY. Installing a client: SDKs & CLI.
curl -H "Authorization: Bearer dsa_live_…" \
"https://api.datasportsapi.com/v2/players/{id}/fixtures"03Response
The top-level keys of the JSON body. Each object links to its full shape in the data reference.
dataPlayerFixture[]meta- page, count, hasNextPage
{ "data": [ { "id": 201324, "status": { "type": "finished", … }, "home": { … }, "away": { … }, …,
"playerMatch": { "side": "away", "onBench": false, "rating": 8.1, "statistics": { "minutesPlayed": 90 },
"incidents": { "goals": 1, "penaltyGoals": 1 } } }, … ],
"meta": { "page": 0, "count": 30, "hasNextPage": true } }04Errors
- 400
bad_requestpage is not a whole number between 0 and 50
unauthorized429rate_limited429quota_exceeded500internal_errorEvery error code