Live Score - AnySport

Queries the live score and phase (phase) for a single match by match_id, for clients to poll for the latest score. This endpoint provides only the “result” (score, current minute, phase) and no specific events (goalscorers, yellow cards, corners, etc.); use Live Match Stats when you need event-by-event data. Typically used for lightweight scenarios like a score bar or floating score widget that only care about “what’s the current score and what minute is it”; to determine whether a match has finished, always use phase == "finished" rather than guessing from status (this endpoint does not send a status field).

Endpoint

GET /v1/soccer/livescore

Parameters

Parameter	Type	Required	Description
`match_id`	string	Yes	The target match (`as_` id, consistent with /matches); live score is queried per single match
`lang`	string	No	Language, default `en`; invalid values silently fall back to the default language — available values are authoritatively sourced from `GET /v1/soccer/languages`
`page` / `limit`	int	No	Pagination

How to discover “not started / in progress” matches:

/matches/window (recommended): e.g. from_days=0&to_days=0 to fetch the full day’s fixtures, then interpret the status form: not started = HH:MM / Not Started / TBA / empty string, in progress = plain numeric minute / HT; the resulting match_id can be used directly with this endpoint.
/odds/live without a match_id: returns the set of matches currently live (in progress) with active odds.

Response fields (data: array)

Localization note: when lang is a non-default language, home/away/league (team names/league name) are not yet localized by lang; phase_label and other *_label tags work as normal, and the original phase code value is unchanged. Not every value has localized text; when there is no corresponding text this field is omitted, so clients must handle that gracefully.

This endpoint only sends score information and does not include the source status code (status) field; use phase consistently to determine the match phase/whether it has finished. For event-level status (goals/corners/VAR, etc., with English codes), use the 15 Match Events endpoint.

Field	Type	Description
`match_id`	string	Match ID (`as_` prefix, the same ID used across referenced endpoints)
`home`	string	Home team name
`away`	string	Away team name
`league`	string	League name (live-feed naming, e.g. `World Cup 2026`)
`minute`	int	Current minute. Continuous timing: first half 0–45+, second half 46–90+, extra time 91–120+; stoppage time is added directly without resetting
`phase`	string	Phase enum: `regular` / `extra_time` / `penalty` / `finished`; use `phase == finished` to determine the match has ended
`phase_label`	string	Localized text for `phase` (returned per `lang`, e.g. for `lang=zh-CN` it would be `已结束`); the original `phase` code is unchanged, sent when `lang` is a non-default language and localized text exists for that value, omitted when there is no corresponding text, so clients must handle that gracefully
`home_score`	int	Home team’s current total goals (including extra-time goals, excluding the penalty shootout)
`away_score`	int	Away team’s current total goals (including extra-time goals, excluding the penalty shootout)
`ht_score`	string	Half-time score (e.g. `1-0`), empty if half-time hasn’t been reached
`reg_score`	string	Score at the end of regular 90 minutes (e.g. `1-1`), empty if the 90 minutes hasn’t ended
`et_score`	string	Cumulative score at the end of extra time (e.g. `3-1`), empty if there was no extra time or it hasn’t been reported yet; uses the same convention as `et_score` on the referenced matches endpoint
`penalty_score`	string	Penalty shootout score, empty if there was no penalty shootout
`updated_at`	string	Update time, UTC ISO-8601 (with `Z`)

Enum reference

phase enum (4 values)

Value	Meaning
`regular`	Regular play in progress (default value). Note: ordinary attack/defense frames during extra time are also classified as `regular` (the source event code doesn’t distinguish them) — only the explicit boundary frames of extra time (extra-time kickoff / extra-time half-time / extra-time second-half kickoff) are momentarily `extra_time`; to determine “whether currently in extra time,” using `minute > 90` is more reliable
`extra_time`	Extra-time boundary event frames: extra-time kickoff / extra-time half-time break / extra-time second-half kickoff
`penalty`	Penalty shootout: frames for shootout start, scored/missed penalties, and awaiting the next kick
`finished`	Match ended: end of regular full time or end of extra time

Request example

GET /v1/soccer/livescore?match_id=as_3b37c382f39a4235aa93705f053b2da4

Response example

HTTP 200, final score 3-1 including extra time

{
  "success": true,
  "data": [
    {
      "match_id": "as_3b37c382f39a4235aa93705f053b2da4",
      "home": "Argentina",
      "away": "Switzerland",
      "league": "World Cup 2026",
      "minute": 120,
      "phase": "finished",
      "home_score": 3,
      "away_score": 1,
      "ht_score": "1-0",
      "reg_score": "1-1",
      "et_score": "3-1",
      "updated_at": "2026-07-12T03:45:50Z"
    }
  ],
  "meta": {
    "total": 1,
    "page": 1,
    "limit": 50,
    "total_pages": 1,
    "timestamp": "2026-07-13T19:18:24.905164900Z"
  },
  "traceId": "87775517-5dbe-4005-be80-347fd30ea39a"
}

Error example

Missing match_id → HTTP 400, error.code INVALID_PARAMS

GET /v1/soccer/livescore?limit=5

​Endpoint

​Parameters

​Response fields (data: array)

​Enum reference

​phase enum (4 values)

​Request example

​Response example

​Error example

Endpoint

Parameters

Response fields (data: array)

Enum reference

phase enum (4 values)

Request example

Response example

Error example