Skip to main content
GET
CS2 match detail

What it returns

A single match. Fields included depend on which scopes your key carries:
The three HLTV ids (hltv_event_id, team_a_hltv_id, team_b_hltv_id) are stable foreign keys you can join with GET /cs2/v1/tournaments and GET /cs2/v1/teams rather than matching by name strings. They are emitted on every match regardless of scope, and remain null only for matches sourced from non-HLTV providers (rare).
Fields outside your scope set are simply absent from the response — not nulled, just not emitted.

Identifier

{match_id} accepts either the Ticktock match UUID or an UOF match reference — the URN od:match:{int} or its bare integer. Feed clients that only hold the UOF id (and never receive tt_match_id) can resolve a match directly. An id that matches no known match returns 404.

Required scope

  • Minimum: cs2:matches:read
  • Recommended for full payload: add cs2:matches:detail, cs2:markets:read

Example

The same URL also accepts Accept: application/xml (or hit the .xml sibling URL) for a byte-identical AMQP-compatible <fixtures_fixture> envelope — note this is a compact fixture shape, not the rich JSON detail. The XML carries the two teams as nested <competitor> elements with a home / away qualifier, plus an <extra_info> block with sport_format (and best_of when known). See Scopes & Bundles → Content negotiation for the full list of XML-capable endpoints.

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 June 21, 2026