Skip to main content
The live snapshot is the data shape that carries real-time match state across both REST and WebSocket surfaces. Whether you poll on demand or receive pushed updates, the structure is consistent within a sportdata shape that carries real-time match state across both REST and WebSocket surfaces. Whether you poll on demand or receive pushed updates, the structure is consistent within a sport.
The snapshot schema depends on the sport. Always branch on the sport field. This page documents the soccer snapshot first, then the cricket snapshot (which has a completely different shape — no clock, phase, stats, or events; instead an innings score, batting/bowling cards, a current-over ticker, and a per-innings scorecard). Other sports will follow over time; treat unknown fields as optional.

Used by

  • GET /matches/{id}/live — returns the snapshot directly
  • GET /matches/{id}/result — returns the snapshot as half_time and full_time objects
  • WebSocket snapshot and update frames — the snapshot is the data field

The soccer live snapshot object

Returned with "sport": "soccer".

Top-level fields

The snapshot schema depends on the sport. Always branch on the sport field. This page documents the soccer snapshot first, then the cricket snapshot (which has a completely different shape — no clock, phase, stats, or events; instead an innings score, batting/bowling cards, a current-over ticker, and a per-innings scorecard). Other sports will follow over time; treat unknown fields as optional.

Used by

  • GET /matches/{id}/live — returns the snapshot directly
  • GET /matches/{id}/result — returns the snapshot as half_time and full_time objects
  • WebSocket snapshot and update frames — the snapshot is the data field

The soccer live snapshot object

Returned with "sport": "soccer".

Top-level fields

integer
required
Schema version. Currently 1Schema version. Currently 1.
integer
Your match id. Present on WebSocket frames for multiplexing; omitted on REST responsesYour match id. Present on WebSocket frames for multiplexing; omitted on REST responses.
object
Upstream reference ids. Clients can usually ignore this objectUpstream reference ids. Clients can usually ignore this object.
string
required
"soccer""soccer".
string
required
League or competition name, e.g. "USA MLS Next Pro League"League or competition name, e.g. "USA MLS Next Pro League".
string
required
Home team nameHome team name.
string
required
Away team nameAway team name.
string
required
Current match state: live, ht (half-time), ft (full-time), or not_startedCurrent match state: live, ht (half-time), ft (full-time), or not_started.
object
required
Match clock. See Clock belowtch clock. See Clock below.
object
required
Current score. See Score belowCurrent score. See Score below.
object
required
Decoded current game state. See Phase belowDecoded current game state. See Phase below.
object
required
Map of stat key → {"home": int, "away": int}. See StatisticsMap of stat key → {"home": int, "away": int}. See Statistics.
array | null
Timeline incidents. null if no events have occurred yet. See Events.
object
Last event-anchored ball position on the pitch. See Ball Position.
datetime
required
When this snapshot was produced, in ISO 8601 UTC.
array | null
Timeline incidents. null if no events have occurred yet. See Events.
object
Last event-anchored ball position on the pitch. See Ball Position.
datetime
required
When this snapshot was produced, in ISO 8601 UTC.

ScorScore

The current match score as {"home": int, "away": int}, with an optional shootout tally when a penalty shootout has beguncurrent match score as {"home": int, "away": int}, with an optional shootout tally when a penalty shootout has begun.

Clock

Displaying a live timer

minute:second is the clock as of as_of, not as of right now. How you turn it into a ticking timer depends on which surface you read from:
  • REST (GET /matches/{id}/live) — the server projects the clock forward to request time before responding. When running is true, minute:second is already current and as_of is set to the response time. Display minute:second as-is.
  • WebSocket snapshot and update frames — frames carry the clock as of the last provider update, so consumers must advance it themselves between frames. While running is true:
    When running is false (half-time, full-time, stoppages), do not project — display minute:second as-is. A new frame will reset the anchor when play resumes.
The clock only ticks within the current period; period transitions (e.g. 1HHT2H) always arrive in a real frame, so the projected value can run uncapped through stoppage time and snaps back if the provider pauses silently.

Phase

The phase object describes what is happening on the pitch right now.

Full soccer example

The cricket live snapshot object

Returned with "sport": "cricket" from the same surfaces as the soccer snapshot — GET /matches/{id}/live and the WebSocket data field. The shape is different: an innings score, the batting and bowling cards, a current-over ticker, the last decoded incident, and a full per-innings scorecard. There is no clock, phase, stats, events, or ball.

Reading a cricket snapshot

The payload has two layers — a quick-glance live state and the full card:
  • Live, at a glance (top level): score (the current innings total), over (the over in progress), batsmen (the two at the crease), bowler (current spell), and last_event. This is everything you need for a compact live scoreboard — e.g. “West Indies 138/3 (40.1) — Jangoo 20*, Da Silva 12* — Dinusha 9-0-25-1”.
  • Full detail (scorecard): every innings of the match in order, each with its complete batting and bowling cards, fall of wickets, and an over-by-over breakdown (overs: runs in that over plus cumulative score — the data behind a worm or run-rate graph). Use this for a full scorecard view.
The top-level score/batsmen/bowler/over describe the same innings that is flagged "live": true in scorecard. They come from two separate provider feeds, so they can differ by a ball or two for a moment; the next frame reconciles them. scorecard is omitted until the match is live mid-session — limited-overs games have up to two innings, a Test up to four.
Multi-day Tests. Between days a Test is at stumps: the live snapshot freezes at the last ball — no new frames until play resumes the next day — and the catalog match object’s status becomes CLOSE_OF_PLAY (see Match status values), so the match stays visible in /matches and /matches/live rather than disappearing overnight. The snapshot’s own status (below) is the in-play state and is distinct from that catalog lifecycle status.

Top-level fields

integer
Your match id. Present on WebSocket frames.
string
required
"cricket".
string
required
Competition or match name, e.g. "West Indies vs Sri Lanka - 1st Test".
string
required
Home team name.
string
required
Away team name.
string
required
Current match state: live, ht (half-time), et (extra time in progress), shootout (penalty shootout in progress), ft (full-time — used for both regulation full-time and after extra time), or not_started.Current match state: live, ht (half-time), et (extra time in progress), shootout (penalty shootout in progress), ft (full-time — used for both regulation full-time and after extra time), or not_started.Current match state: not_started, live, innings_break, stopped (rain, bad light, tea, …), or ended.
string
required
Format: test, t20, one_day (50-over), the_hundred, or limited_overs (overs not yet known).
integer
required
Current innings number.
string
required
Side at the crease: "home" or "away".
object
required
The batting side’s innings score. See Cricket score below.
string
Raw score string from the provider; for a multi-innings match it may carry prior innings too.
object
required
Current-over ticker. See Over below.
array
required
The two batters at the crease. See Batsman below.
object
required
Current bowler’s spell figures. See Bowler below.
object
The decoded last incident. See Last event below.
array
Full per-innings card (all innings, in order). See Scorecard below. Omitted until the match is live mid-session.
datetime
required
When this snapshot was produced, in ISO 8601 UTC.

Cricket score

The batting side’s current innings total.

Over

Ticker for the over in progress.

Batsman

Each entry in batsmen describes one of the two batters at the crease.

Bowler

The current bowler’s spell figures.

Scorecard

scorecard is an array of innings — every innings of the match, in order. The live innings is flagged with "live": true; finished innings carry their final figures; innings yet to bat are present but omit score.

Last event

The decoded last incident on the field.

Full cricket example

The batting and bowling arrays above are trimmed to one or two rows for brevity; a real innings carries every batter and bowler.

Appendix: enumerations

Snapshot sport: soccer, cricket. Other sports may appear in future — branch on this field. Snapshot status — soccer: not_started, live, ht, ft. Snapshot status — cricket: not_started, live, innings_break, stopped (rain, bad light, tea, …), ended. Cricket match_type: test, t20, one_day (50-over), the_hundred, limited_overs (overs not yet known). Clock period (soccer): 1H, 2H, HT, FT (and similar period codes). Event type (soccer): goal, corner, yellow_card, red_card, penalty, substitution, shootout, event. Common soccer stat keys: shots_on_target, shots_off_target, attacks, dangerous_attacks, possession, corners, yellow_cards, red_cards. Cricket last_event.label is drawn from the provider’s incident table, e.g. runs, bye, wide, no ball, wicket, bowled, LBW, caught, stumped, run out, bowling, maiden over, end of over, duck, century, review, innings break, match ended.

Clock

Displaying a live timer

minute:second is the clock as of as_of, not as of right now. How you turn it into a ticking timer depends on which surface you read from:
  • REST (GET /matches/{id}/live) — the server projects the clock forward to request time before responding. When running is true, minute:second is already current and as_of is set to the response time. Display minute:second as-is.
  • WebSocket snapshot and update frames — frames carry the clock as of the last provider update, so consumers must advance it themselves between frames. While running is true:
    When running is false (half-time, full-time, stoppages), do not project — display minute:second as-is. A new frame will reset the anchor when play resumes.
The clock only ticks within the current period; period transitions (e.g. 1HHT2H) always arrive in a real frame, so the projected value can run uncapped through stoppage time and snaps back if the provider pauses silently.

Phase

The phase object describes what is happening on the pitch right now.

Full soccer example

The cricket live snapshot object

Returned with "sport": "cricket" from the same surfaces as the soccer snapshot — GET /matches/{id}/live and the WebSocket data field. The shape is different: an innings score, the batting and bowling cards, a current-over ticker, the last decoded incident, and a full per-innings scorecard. There is no clock, phase, stats, events, or ball.

Reading a cricket snapshot

The payload has two layers — a quick-glance live state and the full card:
  • Live, at a glance (top level): score (the current innings total), over (the over in progress), batsmen (the two at the crease), bowler (current spell), and last_event. This is everything you need for a compact live scoreboard — e.g. “West Indies 138/3 (40.1) — Jangoo 20*, Da Silva 12* — Dinusha 9-0-25-1”.
  • Full detail (scorecard): every innings of the match in order, each with its complete batting and bowling cards, fall of wickets, and an over-by-over breakdown (overs: runs in that over plus cumulative score — the data behind a worm or run-rate graph). Use this for a full scorecard view.
The top-level score/batsmen/bowler/over describe the same innings that is flagged "live": true in scorecard. They come from two separate provider feeds, so they can differ by a ball or two for a moment; the next frame reconciles them. scorecard is omitted until the match is live mid-session — limited-overs games have up to two innings, a Test up to four.
Multi-day Tests. Between days a Test is at stumps: the live snapshot freezes at the last ball — no new frames until play resumes the next day — and the catalog match object’s status becomes CLOSE_OF_PLAY (see Match status values), so the match stays visible in /matches and /matches/live rather than disappearing overnight. The snapshot’s own status (below) is the in-play state and is distinct from that catalog lifecycle status.

Top-level fields

integer
Your match id. Present on WebSocket frames.
string
required
"cricket".
string
required
Competition or match name, e.g. "West Indies vs Sri Lanka - 1st Test".
string
required
Home team name.
string
required
Away team name.
string
required
Current match state: not_started, live, innings_break, stopped (rain, bad light, tea, …), or ended.
string
required
Format: test, t20, one_day (50-over), the_hundred, or limited_overs (overs not yet known).
integer
required
Current innings number.
string
required
Side at the crease: "home" or "away".
object
required
The batting side’s innings score. See Cricket score below.
string
Raw score string from the provider; for a multi-innings match it may carry prior innings too.
object
required
Current-over ticker. See Over below.
object
required
Map of stat key → {"home": int, "away": int} (integer counters). See StatisticsMap of stat key → {"home": int, "away": int} (integer counters). See Statistics.
object
Expected goals per side, {"home": float, "away": float}. Optional — omitted when the provider doesn’t supply it (common in smaller leagues)Expected goals per side, {"home": float, "away": float}. Optional — omitted when the provider doesn’t supply it (common in smaller leagues).
object
Fractional stats map — same shape as stats but with float values, for stats that are naturally percentages or ratios (e.g. passing_accuracy, crossing_accuracy in 0–1; action_area as an attacking-third share). Optional. See StatisticsFractional stats map — same shape as stats but with float values, for stats that are naturally percentages or ratios (e.g. passing_accuracy, crossing_accuracy in 0–1; action_area as an attacking-third share). Optional. See Statistics.
array
Per-minute pressure series — an array of floats in [-1, 1], oldest first. Positive values mean the home side is pressing, negative values the away side. OptionalPer-minute pressure series — an array of floats in [-1, 1], oldest first. Positive values mean the home side is pressing, negative values the away side. Optional.
object
Each team’s recent results coming into this match, as {"home": [...], "away": [...]}. See Form below. OptionalEach team’s recent results coming into this match, as {"home": [...], "away": [...]}. See Form below. Optional.
array
required
The two batters at the crease. See Batsman below.
object
required
Current bowler’s spell figures. See Bowler below.
array
Chronological list of goalscorers. See Goals below. Optional.
array
10-minute incident buckets, oldest first. See Intervals below. Optional.
array
Per-player match tallies (shots, assists, saves, …). See Players below. Optional.
object
The decoded last incident. See Last event below.
object
Ball position on the pitch. While a live animation position is streaming, ball follows it (only x/y/event set); otherwise it anchors to the last notable event (goal, shot, …) with detail and minute filled. See Ball Position.
array
Full per-innings card (all innings, in order). See Scorecard below. Omitted until the match is live mid-session.
datetime
required
When this snapshot was produced, in ISO 8601 UTC.
Fields marked optional above are omitted when the provider doesn’t supply them — smaller leagues often lack xg, momentum, and players. Guard for their presence rather than assuming they’re always set.

Cricket score

array
required
The two batters at the crease. See Batsman below.
object
required
Current bowler’s spell figures. See Bowler below.
array
Chronological list of goalscorers. See Goals below. Optional.
array
10-minute incident buckets, oldest first. See Intervals below. Optional.
array
Per-player match tallies (shots, assists, saves, …). See Players below. Optional.
object
The decoded last incident. See Last event below.
object
Ball position on the pitch. While a live animation position is streaming, ball follows it (only x/y/event set); otherwise it anchors to the last notable event (goal, shot, …) with detail and minute filled. See Ball Position.
array
Full per-innings card (all innings, in order). See Scorecard below. Omitted until the match is live mid-session.
datetime
required
When this snapshot was produced, in ISO 8601 UTC.
Fields marked optional above are omitted when the provider doesn’t supply them — smaller leagues often lack xg, momentum, and players. Guard for their presence rather than assuming they’re always set.

Cricket score

The batting side’s current innings total.

Over

Ticker for the over in progress.

Batsman

Each entry in batsmen describes one of the two batters at the crease.

Bowler

The current bowler’s spell figures.

Scorecard

scorecard is an array of innings — every innings of the match, in order. The live innings is flagged with "live": true; finished innings carry their final figures; innings yet to bat are present but omit score.

Last event

The decoded last incident on the field.
Match against code, not label. Labels are display text and may be refined over time — for example, codes that used to read "General alert" now carry their specific meaning — so any client logic that depends on the phase should key off the stable code.

Form

form decodes each team’s last matches coming into this one. Each entry describes one previous fixture, most recent first.

Goals

Each entry in goals is one scorer, in chronological order. This is the goalscorer list you’d render alongside the match score; the events array carries every incident, goals is the pre-filtered subset.

Intervals

Each entry in intervals is one 10-minute bucket of incident counts, oldest first. Buckets have a fixed per-side shape, so summing across buckets reconciles with the match counters in stats. Use this for a “shots by phase of match” or interval-based betting view without post-processing the events timeline yourself.

Players

Each entry in players is one player’s cumulative match tallies — the data behind a per-player markets view (shots, cards, assists).

Full cricket example

The batting and bowling arrays above are trimmed to one or two rows for brevity; a real innings carries every batter and bowler.

Appendix: enumerations

Snapshot sport: soccer, cricket. Other sports may appear in future — branch on this field. The batting side’s current innings total.

Over

Ticker for the over in progress.

Batsman

Each entry in batsmen describes one of the two batters at the crease.

Bowler

The current bowler’s spell figures.

Scorecard

scorecard is an array of innings — every innings of the match, in order. The live innings is flagged with "live": true; finished innings carry their final figures; innings yet to bat are present but omit score.

Last event

The decoded last incident on the field.
Match against code, not label. Labels are display text and may be refined over time — for example, codes that used to read "General alert" now carry their specific meaning — so any client logic that depends on the phase should key off the stable code.

Form

form decodes each team’s last matches coming into this one. Each entry describes one previous fixture, most recent first.

Goals

Each entry in goals is one scorer, in chronological order. This is the goalscorer list you’d render alongside the match score; the events array carries every incident, goals is the pre-filtered subset.

Intervals

Each entry in intervals is one 10-minute bucket of incident counts, oldest first. Buckets have a fixed per-side shape, so summing across buckets reconciles with the match counters in stats. Use this for a “shots by phase of match” or interval-based betting view without post-processing the events timeline yourself.

Players

Each entry in players is one player’s cumulative match tallies — the data behind a per-player markets view (shots, cards, assists).

Full cricket example

The batting and bowling arrays above are trimmed to one or two rows for brevity; a real innings carries every batter and bowler.

Appendix: enumerations

Snapshot sport: soccer, cricket. Other sports may appear in future — branch on this field. Snapshot status — soccer: not_started, live, ht, et (extra time), shootout, ft (regulation or after extra time)tatus — soccer: not_started, live, ht, et (extra time), shootout, ft (regulation or after extra time). Snapshot status — cricket: not_started, live, innings_break, stopped (rain, bad light, tea, …), endedcricket: not_started, live, innings_break, stopped (rain, bad light, tea, …), ended. Cricket match_type: test, t20, one_day (50-over), the_hundred, limited_overs (overs not yet known)Cricket match_type: test, t20, one_day (50-over), the_hundred, limited_overs (overs not yet known). Clock period (soccer): 1H, 2H, HT, FT, ET1, ET2 (extra-time halves), ET (break between them), AET (full time after extra time), SO (penalty shootoutlock period (soccer): 1H, 2H, HT, FT, ET1, ET2 (extra-time halves), ET (break between them), AET (full time after extra time), SO (penalty shootout). Event type (soccer): goal, corner, yellow_card, red_card, penalty, substitution, shot_on_target, shot_off_target, offside, assist, period_score (HT/FT/AET score markers), shootout (penalty-shootout kicks), event. Treat unknown types as eventEvent type (soccer): goal, corner, yellow_card, red_card, penalty, substitution, shot_on_target, shot_off_target, offside, assist, period_score (HT/FT/AET score markers), shootout (penalty-shootout kicks), event. Treat unknown types as event. Common soccer stat keys (integer counters in stats): shots_on_target, shots_off_target, attacks, dangerous_attacks, possession (percentage), corners, yellow_cards, red_cards, throw_ins, free_kicks, goal_kicks, penalties, substitutions, keeper_saves, key_passes, crossesCommon soccer stat keys (integer counters in stats): shots_on_target, shots_off_target, attacks, dangerous_attacks, possession (percentage), corners, yellow_cards, red_cards, throw_ins, free_kicks, goal_kicks, penalties, substitutions, keeper_saves, key_passes, crosses. Fractional stat keys (float values in stats_float): passing_accuracy, crossing_accuracy (both 0–1), action_area (attacking-third share, %)Fractional stat keys (float values in stats_float): passing_accuracy, crossing_accuracy (both 0–1), action_area (attacking-third share, %). Cricket last_event.label is drawn from the provider’s incident table, e.g. runs, bye, wide, no ball, wicket, bowled, LBW, caught, stumped, run out, bowling, maiden over, end of over, duck, century, review, innings break, match ended. Catalog match status (for the match object, not the live snapshot): NOT_STARTED, STARTED, CLOSE_OF_PLAY (multi-day cricket Test between days), FINISHED.Catalog match status (for the match object, not the live snapshot): NOT_STARTED, STARTED, CLOSE_OF_PLAY (multi-day cricket Test between days), FINISHED.Catalog match status (for the match object, not the live snapshot): NOT_STARTED, STARTED, CLOSE_OF_PLAY (multi-day cricket Test between days), FINISHED.