FixturesEndpoint 6 of 116
Lineups
GET
https://api.datasportsapi.com/
- Plan
- All plans
- Auth
Bearer dsa_live_…- Parameters
- 1 required · 0 optional
- Returns
Lineups
Team lineups and formations plus unavailable players, with every player carrying a match rating and statistics.
Worth knowing
- How much you get depends on the fixture: top leagues come with lineups plus per-player ratings and statistics, while many youth, amateur and friendly matches never receive any.
- Player statistics reuse the team-statistics keys wherever the meaning matches (passes, accuratePasses, shotsOnGoal, tackles, …; bigChancesCreated counts big chances the player set up for a teammate).
- Each …Percentage field is a share from 0 to 100, with one exception: basketball’s trueShootingPercentage can exceed 100 (for example a handful of free throws plus a three).
- Players who did not take part have rating and statistics set to null; avgRating (football) holds the player’s season average and is filled mainly before and around kick-off.
- The profile fields heightCm, dateOfBirth, country and marketValue mirror the player’s profile (/v2/players/{id}) and are null when the source has no value — common in predicted lineups — with marketValue largely limited to football.
- Preferred foot is missing because the lineups we receive lack it; the profile and the squad have it.
- position is a sport-dependent word (G means goalkeeper in football, goalie in ice hockey and guard in basketball), while positionCode retains the source’s letter.
- A fixture without lineups (so far) answers 200 with confirmed: false and both sides empty; only an unknown id gets 404.
- While a match is live, the data is refreshed roughly every 30 seconds.
01Parameters
idpathRequiredfixture id issued by DataSportsAPI, a positive integer
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/fixtures/{id}/lineups"03Response
The top-level keys of the JSON body. Each object links to its full shape in the data reference.
dataLineups
ObjectsLineups
Example response
11 lines
{ "data": { "confirmed": true,
"home": { "formation": "4-2-3-1", "players": [
{ "player": { "id": 3772, "name": "David Raya", "slug": "david-raya", "shortName": "D. Raya", "image": "…" },
"position": "goalkeeper", "positionCode": "G", "jerseyNumber": "1", "substitute": false, "captain": false,
"heightCm": 187, "dateOfBirth": "1995-09-15", "country": { "code": "ES", "name": "Spain", "flag": "…" },
"marketValue": { "amount": 25000000, "currency": "EUR" },
"rating": 7.1, "avgRating": 6.94, "ratingVersions": { "original": 7.1, "alternative": 7.3 }, "star": null, "battingOrder": null,
"statistics": { "minutesPlayed": 90, "passes": 34, "accuratePasses": 29, "saves": 2, "touches": 41, … } }, … ],
"missing": [ { "player": { … }, "availability": "out", "reason": "injury", "description": "Knee Injury",
"expectedReturnAt": "2026-11-02T00:00:00.000Z" } ] },
"away": { … } } }04Errors
Nothing specific to this endpoint: only the account-wide errors below apply.
Any key can also meet401
unauthorized429rate_limited429quota_exceeded500internal_errorEvery error code