Skip to main content
Game Detail is the deepest part of V1. Every endpoint below takes the same game ID and shares the standard envelope.

Endpoint family

The game object exposes hasStats, hasLineups, hasStandings, hasBrackets, hasPreviousMeetings so you can hide child tabs that will return empty.
Coaches and stadiums. GET /api/v1/game/{id} returns a full venue (id, name, capacity, live attendance). The head coach appears in GET /api/v1/game/{id}/lineups as the last entry in each team’s members[], identified by formation.name === "Coach" (status: 4, statusText: "Management"). V1 returns only the coach’s athlete id — no name field. For the coach’s full name and country, use V2’s /api/teams/{teamId}. See the World Cup managers & venues guide for the full pattern.

Sample: /game/{id}/events

Common eventType.id values

Sample: /game/{id}/venue

Sample: /game/{id}/officials

Sample: /game/{id}/stages

Sample: /game/{id}/chartevents

Each entry is a shot, mapped to pitch coordinates with xG/xGoT.

Sample: /game/{id}/playbyplay

Sample: /game/{id}/predictions

Community polls — useful for engagement widgets.

Sport-scoped variants

Every game endpoint also works under the sport slug, which lets you front it with a single-sport CDN rule:

Per-sport callouts

  • Tennisstages[] represents sets. gameTime is the set number; per-game points live in events[].
  • Basketball / Hockey / A. Footballstages[] lists quarters/periods; gameTime advances per period and resets on the period change.
  • Baseballstages[] lists innings; refer to V2 baseball innings logic for status code 21-29 semantics (V1 keeps the inning in statusText).
Last modified on June 29, 2026