Skip to main content
GET
/
cs2
/
v1
/
matches
/
{match_id}
/
timeline
CS2 match timeline (rounds + events + VOD anchors)
curl --request GET \
  --url https://ticktock.bet/cs2/v1/matches/{match_id}/timeline \
  --header 'X-API-Key: <api-key>'
{
  "data": {
    "id": "52ef0d9c-7c1f-4c4e-9b3a-4a5e2f8b1c10",
    "team_a": "Sashi",
    "team_b": "OG",
    "team_a_logo": "https://images.ticktock.bet/teams/sashi.png",
    "team_b_logo": "https://images.ticktock.bet/teams/og.png",
    "event": "ESL Pro League S20",
    "bo_type": "bo3",
    "status": "live",
    "scheduled_at": "2026-05-10T17:00:00+00:00",
    "score_a": 1,
    "score_b": 0,
    "map_name": "de_mirage"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.ticktock.bet/llms.txt

Use this file to discover all available pages before exploring further.

​
What it returns

Per-round + per-event log for one match. Each event carries:
  • type (kill, bomb_planted, bomb_defused, bomb_exploded, …)
  • actor / target / weapon / side / victim_side
  • time (UTC) and time_offset_seconds (round clock offset)
  • VOD timecode + map number — anchors for stream replay players to jump straight to the moment.
The internal meta blob (raw scorebot JSON) only comes through with cs2:matches:internals.

​
Required scope

  • Minimum: cs2:matches:detail

​
Use cases

  • Dispute resolution — point operations or end users at the exact stream timecode for a contested kill or bomb plant.
  • Custom replay players — index your VOD by round/event using the anchor table.
  • Post-match analytics — feed the event log into your own model.

​
Example

curl -H "X-API-Key: $TT_KEY" \
  "https://ticktock.bet/cs2/v1/matches/52ef…/timeline"

Authorizations

​
X-API-Key
string
header
required

Tenant API key issued during onboarding

Path Parameters

​
match_id
string
required

Response

Successful Response

The response is of type Response Get Match Timeline Cs2 V1 Matches Match Id Timeline Get · object.

Last modified on May 10, 2026