What it streams
In-game / post-game statistics updates for fixtures — team-level stats (corners, cards, shots, possession, …) and player-level stats (goals, assists, aces, kills, …), keyed by a sport-agnostic stat model.Routing
- Entity key:
payload.fixtureId - Filters:
sportIds,tournamentIds,fixtureIds - Access: live/pregame access is determined by your
apiKey
Payload structure
Stats travel as resolved facts in the canonical stat model. Team stat rows:
Player stat rows carry
playerId and a single value instead of the participant pair:
Semantics
- Latest state. Treat each update as the current resolved value for
(fixtureId, period, statType [, playerId])— not a tick ledger. - Resolved, not raw. Values are cross-source resolved facts (the same layer settlement reads), so counts only move forward during play and corrections arrive as explicit updates.
- The main scoreline also travels here as
statType = "score"— but the dedicatedscoreschannel remains the recommended score feed. statTypeis an open taxonomy: which stats exist varies per sport; new stats appear as new values, never as schema changes.