Map veto (pick/ban) sequence for one match
The match's map pick/ban sequence in veto order (a CS2 bo3 runs ban/ban/pick/pick/ban/ban/decider). The decider step carries a null `team_id` — no team makes that choice. Unknown match id yields an empty list. Enveloped: `{"data": [MapVeto, ...], "meta": {...}}` (not cursor-paginated; `next_cursor` is null).
The match's map pick/ban sequence in veto order (a CS2 bo3 runs ban/ban/pick/pick/ban/ban/decider). The decider step carries a null team_id — no team makes that choice. Unknown match id yields an empty list. Enveloped: {"data": [MapVeto, ...], "meta": {...}} (not cursor-paginated; next_cursor is null).
Primary auth (live). Authorization: Bearer <api-key> — the header takes precedence over the query fallback. The raw key is hashed (SHA-256, hex) and looked up in api.keys.key_hash; the raw value is never stored.
In: header
Path Parameters
Game slug. cs2 is the only populated title today; an un-onboarded game 404s cleanly.
Resource identifier — either a UUID or the resource's human-readable slug, scoped to {game}. /v1/cs2/teams/natus-vincere and /v1/cs2/teams/019f23d1-fb5c-7987-b522-47c3a5e72111 address the same row, so you can go straight from a slug you already have without first looking up its id.
Slugs work on teams, players and tournaments. Matches have no slug, so a match id must be a UUID. Either way, an identifier that resolves to nothing returns 404 not_found.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/cs2/matches/019f2858-e253-7f3d-bdff-bc7738bd1036/vetoes"{ "data": [ { "id": "01a0b9d0-982b-760a-b7dd-31d21f3af98e", "match_id": "01a0a3e2-96a5-7a9f-8af2-fae0f1a7d678", "order": 1, "team_id": "01a0916e-90e4-7469-903a-463c4fc69c4b", "choice_type": "ban", "map_name": "de_nuke", "created_at": "2026-09-19T13:18:03.676691Z" }, { "id": "01a0b9d0-982b-7863-845f-bc04014c5295", "match_id": "01a0a3e2-96a5-7a9f-8af2-fae0f1a7d678", "order": 2, "team_id": "019f2858-e255-78e4-9e7c-32f307dfac91", "choice_type": "ban", "map_name": "de_anubis", "created_at": "2026-09-19T13:18:03.676691Z" }, { "id": "01a0b9d0-982b-79a7-b6c4-23fff3e74759", "match_id": "01a0a3e2-96a5-7a9f-8af2-fae0f1a7d678", "order": 3, "team_id": "01a0916e-90e4-7469-903a-463c4fc69c4b", "choice_type": "pick", "map_name": "de_ancient", "created_at": "2026-09-19T13:18:03.676691Z" } ], "meta": { "count": 7, "next_cursor": null }}{ "error": { "code": "not_found", "message": "not found", "request_id": "019f3d18-c15f-7319-81a7-343e8a80a578" }}{ "error": { "code": "not_found", "message": "not found", "request_id": "019f3d18-c15f-7319-81a7-343e8a80a578" }}{ "error": { "code": "rate_limited", "message": "rate limit exceeded", "request_id": "019f3d18-c15f-7319-81a7-343e8a80a578" }}Where a match is being broadcast GET
The channels carrying a match, official broadcast first and then by audience. **This is a live pointer, not a historical record.** The set is replaced in full on every refresh while a match is in progress, and it is emptied when the match ends — a channel URL stops resolving to this match once the broadcast is over, so a finished match returns an empty list rather than dead links. Do not store these rows as a match archive. Streams appear once a match is IN PROGRESS. A scheduled match that has not started returns an empty list even when a broadcast is already announced. `viewers` is the count at `observed_at`, not a live figure, and is `null` when the channel did not report one — which is not the same as zero. `platform` is one of `twitch`, `kick`, `youtube` or `other`; treat it as an open list. `embed_url` is the platform's embeddable player URL and is omitted when the channel has none. An unknown match id returns an empty list.
Matches with their sub-resources embedded GET
The match list with each match's data embedded, so a historical pull costs one request per **page of 25 matches** instead of up to seven requests per match. It takes exactly the filters, ordering and cursors of `GET /v1/{game}/matches` — including `changed_since` and `sort=changed_at` — and each embedded array is byte-for-byte what the matching per-match route returns. **One request, whatever it carries.** A bulk page counts as a single request against your monthly allowance. During a free trial this endpoint has its own ceiling of 20 requests (a 500-match sample); see the rate-limits guide. **Page size is capped at 25** and reported back as `meta.max_limit`, so a larger `limit` is visibly clamped rather than silently ignored. A full page of recent matches with everything included is around 7 MB before compression and can reach about 10 MB — send `Accept-Encoding: gzip` (most HTTP clients do; with curl pass `--compressed`) and it travels at roughly a tenth of that. **At most two bulk pages are built at once, server-wide.** If both slots are taken you get `503` with `Retry-After: 2` and the code `unavailable`. That refusal is not counted against your quota. Page sequentially, honour `Retry-After`, and you will rarely see it. Ask only for what you need: an `include` you omit is absent from the response and costs nothing to build. With no `include` at all this is the plain match list at a smaller page size. Check `data_available` on each row to tell "this match has no rounds on record" from "you did not ask for rounds".