Lineups - AnySport

Given a match_id, returns the formation, starters, and substitutes for both the home and away sides (predicted indicates whether this is a pre-match predicted lineup — the semantics differ slightly before vs. after the match). Typically used for the “Lineups” section of a match details page, where formation can be combined with player positions to render a formation diagram. Note that this endpoint returns 404 when no lineup data is available, which differs from the “200 + empty object/array” convention used by most other endpoints in this documentation when no data exists — the client needs to handle this error case separately.

Endpoint

GET /v1/soccer/lineups

Parameters

Parameter	Type	Required	Description
`match_id`	string	Yes	Match ID (`as_` prefix, consistent across all endpoints)
`lang`	string	No	`en` / `zh-CN`; invalid values silently fall back to the default language — see `GET /languages` (19) for available values

Returns 404 (NOT_FOUND) when no lineup data exists for this match.

Response fields (data: object)

Field	Type	Description
`match_id`	string	Match ID (`as_` prefix, consistent across all endpoints)
`home`	object	Home team lineup, structure below
`away`	object	Away team lineup, same structure as home

home / away object structure:

Field	Type	Description
`team_id`	string	Team ID (`ast_`)
`team_name`	string	Team name
`formation`	string	Formation (e.g. `4-1-3-2`)
`predicted`	boolean	Whether this is a predicted lineup
`starters`	array	List of starting players, element structure below
`substitutes`	array	List of substitute players, same element structure as starters

starters[] / substitutes[] element structure:

Field	Type	Description
`player_id`	string	Player ID (`asp_`)
`name`	string	Player name
`number`	string	Shirt number
`position`	string	Player position enum, see “Enum reference” below
`position_label`	string	Localized text for `position` (returned per `lang`, e.g. “Goalkeeper” for `lang=zh-CN` would be `守门员`); the original `position` code is unchanged; sent when `lang` is a non-default language and localized text exists for that value; not every value has localized text, and when there is no corresponding text this field is omitted, so clients must handle that gracefully

*_label convention: position always retains its original code value, and a parallel localized label position_label is returned with the localized text for that value (per lang); not every value has localized text, and when there is no corresponding text this label is omitted, so clients must handle that gracefully.

Enum reference

position (player position)

Value	Meaning
`G`	Goalkeeper
`D`	Defender
`M`	Midfielder
`F`	Forward

The above are the common values; occasional matches may show other notations.

Request example

GET /v1/soccer/lineups?match_id=as_3b37c382f39a4235aa93705f053b2da4&lang=en

Response example

Lineups response example, HTTP 200, a completed match (excerpt)

{
  "success": true,
  "data": {
    "match_id": "as_3b37c382f39a4235aa93705f053b2da4",
    "home": {
      "team_name": "Argentina",
      "formation": "4-1-3-2",
      "starters": [
        {
          "player_id": "asp_6f890f89feb54c82b38c46ddd89b8a1e",
          "name": "Emiliano Martínez",
          "number": "23",
          "position": "G"
        },
        {
          "player_id": "asp_0628f0c4282348cfaeadf206f652f65b",
          "name": "Nahuel Molina",
          "number": "26",
          "position": "D"
        }
      ],
      "substitutes": "…(omitted)"
    },
    "away": "…(same structure as home, omitted)"
  }
}

​Endpoint

​Parameters

​Response fields (data: object)

​Enum reference

​Request example

​Response example

Endpoint

Parameters

Response fields (data: object)

Enum reference

Request example

Response example