Soccer
Statpad serves five soccer leagues: the Premier League (epl), LaLiga (laliga), the Bundesliga (bundesliga), Serie A (seriea) and Ligue 1 (ligue1). All five fill the same endpoints and the same fields, with the sport’s details in the soccer blocks, so the same code reads every league.
The examples come from five recorded matches, one per league, all played on November 8, 2026:
The home team is first, as soccer writes a match.
Live state
live_state on GET /v1/{league}/games/{id} carries the situation in its soccer block. The other sports’ blocks are null.
This is the Premier League match’s live state after full time, from game.json, unedited:
Periods, extra time and shoot-outs
Every soccer league has a period_kind of half and 2 regulation_periods. A league match has two halves. Periods 3 to 5 appear only in a match that goes to extra time or a shoot-out. Build a scoreboard labels the periods, and the clock section formats the match minute.
A shoot-out kick is a penalty_goal, penalty_missed or penalty_saved event in period 5 with soccer.is_shootout set. It never counts toward the score. The shoot-out’s score is in the live state’s home_shootout and away_shootout.
Events
GET /v1/{league}/games/{id}/plays lists the match’s events. It returns a page of events, 500 by default and up to 1,000 with limit, with a next_cursor for the rest. Lists, pagination and dates shows how to page. An event’s type and its soccer.play_type are the same value, one of these:
The soccer block on each event:
Positions run 0 to 100. Usually they’re from the acting team’s point of view, with x running from its own goal line to the goal line it attacks and y across the pitch, so a shot that scores usually ends near end_x 100. Statpad copies the positions from the feed as it sends them, and the feed doesn’t always follow that convention, so use them to draw events, not to decide what happened. To find goals, read type and is_scoring.
Events have no clock_seconds and no group_id. Order them by sequence and id, and label them with minute and added_minute. team_id is the team credited with the event, which for a shot is the shooting team.
Each event’s participants lists the players in it with a role: scorer, assist, shooter, fouler, fouled, player_in and player_out on a substitution, passer on an offside, or player for any other part. An offside’s one participant is the player who played the pass, not the player caught offside. Join each participant’s player_id to players[].id in the game roster response, not to the box score, because a player in a play can have no stat line.
Statpad writes each event’s description from its fields, in English. Read the structured fields rather than parsing the text, whose wording can change.
This is the first goal of the Premier League match, from plays.json, unedited:
Alysson scored for Aston Villa in the 1st minute with his left foot, from field_x 90.8 and field_y 34.2, and John McGinn assisted.
Play groups
Soccer has no drives or possessions in the data. GET /v1/{league}/games/{id}/play-groups returns an empty list.
Box score
GET /v1/{league}/games/{id}/boxscore has one line for every player in the match squad, unused substitutes included. Each line holds one category, soccer:
Treat every code as optional, and ignore codes you don’t use. Build a scoreboard joins the lines to player names.
Rosters
GET /v1/{league}/games/{id}/roster lists both match squads, with each player’s team, jersey, position for the match, such as G, RB or AM-L, and whether they started. Positions are the feed’s codes, so treat them as display text.
What isn’t filled yet
Coverage by league lists the gaps every sport shares, such as team totals and the score by period.
League differences
The five leagues fill the same fields. Their recorded matches have the same live state fields, the same 15 box score codes and the same event types, apart from events that simply didn’t happen in a given match, such as a handball.