Endpoint referenceLineups
/lineups/players
Predicted starters across upcoming fixtures, with position changes flagged.
Predicted starters across upcoming fixtures, with position changes flagged.
The position-change filter is applied in process rather than in SQL, because whether a listed position is a change depends on a per-player history that cannot be expressed in the same query. That means every candidate row is fetched before paging. The set is bounded by upcoming fixtures — roughly eleven starters a side for the games in the window — so it stays in the low thousands.
Query Parameters
games?array<>|null
page?integer
Format
int64pageSize?integer
Format
int64positionChangesOnly?string
uniqueTournamentIds?array<>|null
Response Body
application/json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/v2/lineups/players"{ "$schema": "https://example.com/schemas/LineupsPlayersOKBody.json", "data": [ { "awayTeamId": 0, "awayTeamName": "string", "categoryFlag": "string", "eventId": 0, "eventSlug": "string", "homeTeamId": 0, "homeTeamName": "string", "internalId": 0, "jerseyNumber": "string", "matchTime": 0, "playerFullName": "string", "playerId": 0, "playerInternalId": 0, "playerName": "string", "playerSlug": "string", "position": "string", "positionChange": { "currentPosition": "string", "gamesAnalyzed": 0, "isPositionChange": true, "rawHistory": [ "string" ], "usualPosition": "string" }, "predictedAt": "string", "predictionType": "string", "teamId": 0, "teamName": "string", "tournamentName": "string", "uniqueTournamentId": 0, "viewPriority": 0 } ], "events": [ { "awayTeamId": 0, "awayTeamName": "string", "homeTeamId": 0, "homeTeamName": "string", "id": 0, "internalId": 0, "lineupType": "string", "matchTime": 0, "tournamentName": "string", "uniqueTournamentId": 0 } ], "pagination": { "property1": null, "property2": null }, "positionChangeCount": 0}