Skip to main content
GET
/
cs2
/
v1
/
matches
/
{match_id}
/
summary
Match summary (final result + per-map scores)
curl --request GET \
  --url https://ticktock.bet/cs2/v1/matches/{match_id}/summary \
  --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

Compact end-of-match summary: final score, winning team, completion timestamps, and event metadata. Same shape used by the AMQP feed’s <sport_event> summary message — pass Accept: application/xml to get a byte-identical XML body. Useful for back-office reconciliation and end-of-day reports without pulling the full match detail.

​
Required scope

  • Minimum: cs2:matches:read

​
Example (XML)

Pass Accept: application/xml on the JSON URL, or hit the .xml sibling — both forms return the same byte-identical <match_summary> envelope. 
# Accept-header variant
curl -H "X-API-Key: $TT_KEY" -H "Accept: application/xml" \
  "https://ticktock.bet/cs2/v1/matches/52ef…/summary"

# URL-extension variant
curl -H "X-API-Key: $TT_KEY" \
  "https://ticktock.bet/cs2/v1/matches/52ef…/summary.xml"

Authorizations

​
X-API-Key
string
header
required

Tenant API key issued during onboarding

Headers

​
accept
string
default:application/json

Path Parameters

​
match_id
string
required

Response

Successful Response

Last modified on May 12, 2026