Game Parsed Event
The game_parsed event occurs when a game has been fully processed and all data has been stored in the database.
Event Name
"event": "game_parsed"
Event Version
"version": "v2"
Request Format
- The request is sent as a
POSTrequest. - The
Content-Typeisapplication/json. - The request contains a
Bearertoken in theAuthorizationheader (configured in your webhook settings).
Payload Format
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"event": "game_parsed",
"version": "v2",
"payload": {
"game": {
"id": "3f1a2b4c-5678-90de-f123-456789abcdef",
"map": "de_dust2",
"players": [
{
"steam_id": 76561198000000000,
"nickname": "PlayerOne",
"team": "team1",
"kills": 15,
"deaths": 8,
"assists": 5,
"mvps": 3,
"headshots": 7,
"score": 42
},
{
"steam_id": 76561198000000001,
"nickname": "PlayerTwo",
"team": "team2",
"kills": 12,
"deaths": 10,
"assists": 3,
"mvps": 1,
"headshots": 4,
"score": 35
}
],
"score_team1": 16,
"score_team2": 10,
"duration": 3600,
"played_at": "2025-03-09T12:00:00Z"
},
"player": {
"steam_id": 76561198000000000,
"nickname": "PlayerOne"
}
}
}
Description
-
id: Unique update identifier (UUID format) for preventing duplicate processing. -
event: Event type identifier ("game_parsed"). -
version: API version ("v2") indicating the payload structure and available fields. -
The
gameobject contains details about the processed game, including:-
id: Unique game identifier (UUID format). -
map: The map where the game took place. -
players: A list of players with their Steam IDs, nicknames, and match statistics:steam_id: Player's Steam ID (integer format).nickname: Player's display name.team: Player's team ("team1" or "team2").kills: Number of kills made by the player.deaths: Number of times the player died.assists: Number of assist points.mvps: Number of MVP (Most Valuable Player) awards.headshots: Number of headshot kills.score: Player's total score points.
-
score_team1: Final score for team 1. -
score_team2: Final score for team 2. -
duration: The total game duration in seconds. -
played_at: The timestamp when the game was played.
-
-
The
playerobject provides details about a specific player related to the update.
Handling the Event
- Ensure your webhook processes the received data and verifies the
Bearertoken. - Store the game details in your system as needed.
- Use the
idfield to prevent duplicate processing of the same update.
Changelog
v2 (current)
- Added
playersarray with detailed player statistics (kills,deaths,assists,mvps,headshots,score). - Added
score_team1andscore_team2. - Added
playerobject for highlighting a specific player in the context of the event.
v1 (deprecated)
- Contained only minimal game information (
game_id,demo_url, and basic metadata). - No player-level statistics were included.