> ## 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.
# Get Match
> Match metadata, maps, rounds, streams, markets — gated by your scopes
## What it returns
A single match. Fields included depend on which scopes your key carries:
| Field group | Required scope |
| ---------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| `id`, `team_a`, `team_b`, `event`, `bo_type`, `status`, `scheduled_at`, `score_a/b`, `hltv_event_id`, `team_a_hltv_id`, `team_b_hltv_id` | `cs2:matches:list` or `cs2:matches:read` |
| `started_at`, `finished_at`, `maps[]` | `cs2:matches:read` |
| `rounds[]`, `events[]`, `streams[]`, `demo_url`, `player_stats[]` | `cs2:matches:detail` |
| `markets[]` | `cs2:markets:read` |
| `scoreboard` | `cs2:matches:scoreboard` |
| `uof_match_id`, `data_delay_seconds`, `suspended`, ... | `cs2:matches:internals` |
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`](/api-reference/tournaments/get-tournament) and [`GET /cs2/v1/teams`](/api-reference/teams/get-team) 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
```bash theme={null}
curl -H "X-API-Key: $TT_KEY" \
"https://ticktock.bet/cs2/v1/matches/52ef…"
```
The same URL also accepts `Accept: application/xml` (or hit the `.xml` sibling URL) for a byte-identical AMQP-compatible `` envelope — note this is a **compact fixture shape**, not the rich JSON detail. The XML carries the two teams as nested `` elements with a `home` / `away` `qualifier`, plus an `` block with `sport_format` (and `best_of` when known). See [Scopes & Bundles → Content negotiation](/getting-started/scopes#content-negotiation) for the full list of XML-capable endpoints.
## OpenAPI
````yaml openapi/cs2-api.json GET /cs2/v1/matches/{match_id}
openapi: 3.1.0
info:
title: TickTock B2B API
description: >-
Unified CS2 API (``/cs2/v1/*``) plus sport-agnostic ``/v1/*`` meta
endpoints. Tenant-authenticated via ``X-API-Key`` or ``x-access-token``
header (REST), or ``api_key`` query parameter (WebSocket). Field visibility
is gated by per-key scopes — see ``docs/CS2_API_REFERENCE.md`` for the
catalog and migration.
version: 1.0.0
servers:
- url: https://ticktock.bet
description: Production (same-origin proxy)
- url: https://feed.ticktock.bet
description: Production (B2B subdomain)
security: []
paths:
/cs2/v1/matches/{match_id}:
get:
tags:
- CS2
summary: CS2 match detail
description: >-
Returns match metadata. ``{id}`` is our internal UUID or an UOF match
reference — the URN ``od:match:{int}`` or its bare integer — for feed
clients that only hold the UOF id.
Field set depends on the calling key's scopes:
* ``cs2:matches:read`` — basic + maps + timestamps + current_map
* ``cs2:matches:detail`` — adds rounds, events, latest_round, streams,
demo_url
* ``cs2:markets:read`` — adds markets[] (per-tenant ClientMarketConfig
filtered)
* ``cs2:matches:scoreboard`` — adds live scoreboard from Redis cache
* ``cs2:matches:internals`` — adds integration IDs, ops flags,
data_status
Round-by-round full event log with VOD anchors lives at ``GET
/cs2/v1/matches/{id}/timeline`` — lighter payload here.
Supports both JSON (default, rich payload, scope-filtered) and XML via
``Accept: application/xml`` or the ``.xml`` sibling URL. The XML body is
byte-compatible with the AMQP ```` envelope — a
compact fixture shape, not the rich JSON detail.
operationId: get_match_cs2_v1_matches__match_id__get
parameters:
- name: match_id
in: path
required: true
schema:
type: string
title: Match Id
- name: accept
in: header
required: false
schema:
type: string
default: application/json
title: Accept
responses:
'200':
description: Successful Response
content:
application/json:
schema:
title: Response Get Match Cs2 V1 Matches Match Id Get
example:
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
hltv_event_id: 7438
team_a_hltv_id: 7187
team_b_hltv_id: 5995
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
application/xml: {}
'401':
description: >-
Missing API key. Pass either `X-API-Key: ` or
`$x$access-token: ` on REST calls (or `?api_key=` on
WebSocket handshakes).
content:
application/json:
schema:
type: object
properties:
detail:
type: string
description: Human-readable error message.
required:
- detail
example:
detail: Missing X-API-Key or $x$access-token header
'403':
description: >-
API key authenticated but lacks the scope required for this
endpoint, or the path's sport is not in the key's `sport_allowlist`.
Use `GET /v1/whoami` to inspect the granted scope set.
content:
application/json:
schema:
type: object
properties:
detail:
type: string
description: Human-readable error message.
required:
- detail
example:
detail: >-
Required scope 'cs2:matches:detail' is not granted to this API
key. Contact your account manager to extend the key's scopes.
'404':
description: Resource not found.
content:
application/json:
schema:
type: object
properties:
detail:
type: string
description: Human-readable error message.
required:
- detail
example:
detail: Match not found
'422':
description: >-
Validation error — a query/path parameter failed validation. The
body lists the offending fields.
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
example:
detail:
- type: enum
loc:
- query
- time_filter
msg: 'Input should be one of: 3m, 6m, 1y, all'
input: 2w
'429':
description: >-
Tenant rate limit exceeded. Default is 600 req/min per tenant;
configurable per contract. WebSocket connections are not
rate-limited at the request layer.
content:
application/json:
schema:
type: object
properties:
detail:
type: string
description: Human-readable error message.
required:
- detail
example:
detail: Rate limit exceeded (600 req/min)
headers:
Retry-After:
description: Seconds to wait before retrying.
schema:
type: integer
example: 30
security:
- XAPIKeyHeader: []
- XAccessTokenHeader: []
- UOFAccessTokenHeader: []
components:
schemas:
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
securitySchemes:
XAPIKeyHeader:
type: apiKey
description: Tenant API key issued during onboarding
in: header
name: X-API-Key
XAccessTokenHeader:
type: apiKey
description: UOF-standard alias for the tenant API key
in: header
name: x-access-token
UOFAccessTokenHeader:
type: apiKey
description: Deprecated alias for x-access-token (backward compatibility)
in: header
name: $x$access-token
````