Skip to main content
Given a match_id, returns the match’s complete event stream (every call returns a full snapshot of all events so far for the entire match, not an incremental update), current technical statistics (11 items such as corners/free kicks/yellow and red cards), and the latest event frame’s status. Suitable for building a “live text commentary” style match progress display. On each poll, simply replace your local state entirely with the latest response — no need to stitch together increments on the client side. Both status and events[].type are open-ended English codes that may continue to expand — when parsing, gracefully degrade unknown values to a generic event rather than throwing an error. Relationship to Live Score: endpoint 14 provides only the score and phase, while this endpoint provides the specific “what happened.”

Endpoint

Parameters

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

Response fields (data: object)

*_label convention: status / events[].type / stats keys all retain their original code/key values, with parallel localized labels status_label / events[].type_label / stat_labels added alongside (stat_labels is an object containing only the keys that have localized text); sent when lang is a non-default language and localized text exists for the corresponding value. Event text (text), team names, and league names are not yet localized by lang.

Enum reference

status English codes

status sends an English code (snake_case, underscore-joined English wording):
  • Home-team events get a home_ prefix
  • Away-team events get an away_ prefix
  • Neutral/global events have no prefix (home/away pairs share the same meaning, e.g. home_corner/away_corner)
  • status is the event code of the latest frame.
status is an open enum: values may expand over time, and some events may omit this field; downstream consumers should degrade gracefully to a generic event when encountering an unknown code or a missing field.
Neutral / global statuses Home-team events home_* Away-team events away_* The away team has the corresponding away_* codes, paired with the same meaning as the home-team events — e.g. home_attack paired with away_attack represents the away team attacking. Free-kick zone codes The free-kick zone codes are the sole exception to the home/away “same-meaning pair” rule: Home team: home_free_kick_zone_1 ~ home_free_kick_zone_6 (zones 1–6); Away team: away_free_kick_zone_7 ~ away_free_kick_zone_12 (zones 7–12; the away team uses independent numbering, not a mirror of the home team’s zones).

phase

Reference for determining match end, unique to livescore, 4 values:

events[].type

Event types are categorized by keyword matches against the text field (type is derived server-side from the text), matched in priority order from top to bottom:

Goal method suffix

Goal text may have a - {method} suffix, which can be omitted.
The (Assist: …) assist suffix can also be omitted.

stats key dictionary

11 fixed keys, always returned; the value for each key is a [home, away] two-element array

Request example

Response example

HTTP 200, 88 total events, minute always an integer; excerpt