Skip to main content
GET
Match summary (final result + per-map scores)

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.

Identifier

{match_id} accepts either the Ticktock match UUID or an UOF match reference — the URN od:match:{int} or its bare integer — so feed clients that only hold the UOF id can resolve a summary directly. An id that matches no known match returns 404.

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. Its <sport_event> carries the two teams as nested <competitor> elements with a home / away qualifier and an <extra_info> block with sport_format.

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