Match Details - AnySport

Queries the complete basic information for a single match by match_id; the field structure is identical to a single record from the Matches (essentially a shortcut for an exact query by match_id), making it suitable for the basic info bar at the top of a match details page (matchup, score, status, league/season, venue). Note that when match_id doesn’t exist, the response is 200 with an empty array, not a 404 — the client must check whether the array is empty to detect “no such match.”

Endpoint

GET /v1/soccer/matches/{match_id}

Parameters

Parameter	Location	Required	Description
`match_id`	path	Yes	Match ID (`as_` prefix, consistent across all endpoints)
`lang`	query	No	Available values are authoritatively sourced from `GET /v1/soccer/languages` (19) (e.g. `en` / `zh-CN`); invalid values silently fall back to the default language

When match_id doesn’t exist, the response is 200 with data as an empty array (not a 404).

Response fields

Same single-record structure as the fixtures list (/matches); data is an array containing 1 element:

Field	Type	Description
`match_id`	string	Match ID (`as_` prefix, consistent across all endpoints)
`date`	string	Kickoff date `YYYY-MM-DD` (UTC, ISO)
`time`	string	Kickoff time `HH:mm` (UTC)
`status`	string	Three forms — see “Enum reference” below for the complete list
`status_label`	string	Localized text for the match status (e.g. `完场` under zh-CN); the original `status` value is unchanged, sent when `lang` is a non-default language and localized text exists for that value — when there is no corresponding text this field is omitted, so clients must handle that gracefully (`HH:MM`/plain numeric minute forms never have a label)
`league`	string	League name
`league_id`	string	League ID (`asl_`)
`season`	string	Season
`home`	object	Home team `{ name, team_id }`
`away`	object	Away team `{ name, team_id }`
`ht_score`	string	Half-time score
`ft_score`	string	Regular 90-minute score
`et_score`	string	Cumulative score at the end of extra time (= ft + the extra-time period; returned only for matches that went to extra time)
`penalty_score`	string	Penalty shootout score (returned only for matches decided by penalties)
`venue`	string	Venue (may be empty)

*_label convention: when lang is a non-default language, status retains its original value, and a parallel localized label status_label is added (only textual statuses may have localized text); not every value has localized text, and when there is no corresponding text this field is omitted, so clients must handle that gracefully. Team names/league names (home/away/league) are not yet localized by lang.

Enum reference

The status field takes one of three forms: 1). Textual status (categorized as follows):

Category	Value	Meaning
Not started	`Not Started`	Not yet begun
Not started	`TBA`	Time to be announced
Not started	“ (empty string)	Unscheduled/unmarked, treated as not started
In progress	`HT`	Half-time break
In progress	`ET`	Extra time in progress
In progress	`P`	Penalty shootout in progress
In progress	`Break Time`	Break between extra-time halves, or between extra time and the penalty shootout (included in the official value list)
Finished	`FT`	End of regulation time (Full Time, most common)
Finished	`AET`	Ended after extra time (After Extra Time)
Finished	`Pen.`	Decided by penalty shootout (Penalties)
Finished	`Awarded`	Awarded loss/win (technical loss — forfeiture, eligibility issues, or other administrative rulings)
Finished	`WO`	Forfeit/win by default (Walkover)
Postponed	`Postp.`	Postponed
Postponed	`Delayed`	Kickoff delayed
Cancelled	`Cancl.` / `Cancelled`	Cancelled
Interrupted	`Abandoned` / `Aban.`	Match abandoned
Interrupted	`Susp.`	Suspended (interrupted after kickoff)
Interrupted	`Int.`	Interrupted

2). HH:MM form (e.g. 15:00, 19:45): not started, the value is the UTC kickoff time (matches the time field). 3). Plain numeric form (e.g. 9, 45, 88): in progress, the value is the current match minute.

Request example

GET /v1/soccer/matches/as_3b37c382f39a4235aa93705f053b2da4?lang=en

Response example

HTTP 200, Argentina vs Switzerland; et_score is cumulative: ft_score 1-1 + extra-time period 2-0

{
  "success": true,
  "data": [
    {
      "match_id": "as_3b37c382f39a4235aa93705f053b2da4",
      "date": "2026-07-12",
      "time": "01:00",
      "status": "AET",
      "league": "World Cup",
      "league_id": "asl_62db9cfc3ebf4b87a44570b16668b23e",
      "season": "2026",
      "home": {
        "name": "Argentina",
        "team_id": "ast_9137ee449e3b40a68149ca319373adaf"
      },
      "away": {
        "name": "Switzerland",
        "team_id": "ast_499130f3976546089056d8d747b6c059"
      },
      "ht_score": "1-0",
      "ft_score": "1-1",
      "et_score": "3-1",
      "venue": ""
    }
  ],
  "meta": {
    "total": 1,
    "page": 1,
    "limit": 1,
    "total_pages": 1,
    "timestamp": "2026-07-13T19:18:24.456028400Z"
  },
  "traceId": "5578181f-8743-4561-9a2e-bdd337a6ec9c"
}

​Endpoint

​Parameters

​Response fields

​Enum reference

​Request example

​Response example

Endpoint

Parameters

Response fields

Enum reference

Request example

Response example