A single match

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.

Comma-separated related resources to embed inline: teams (adds team_a/team_b), tournament, and odds (the latest derived line per outcome). include=teams,tournament,odds turns the four requests a match view needs into one. Unknown names are ignored rather than rejected, so adding an expansion later never breaks an existing client. Omit it and the response is exactly as before — every embedded field is absent, not null.

The match's own data can be embedded the same way: maps, stats, vetoes, rounds, depth, lineups, streams and players, each identical to what the matching /matches/{id}/... route returns — except players, which has no standalone route: it is the union of the players named by this match's lineups and stats rows, resolved to full rows, so a lineup or a scoreboard can be rendered without one /players/{id} request per player. include=maps,stats,vetoes,rounds,depth,lineups,players replaces six follow-up requests with none. A requested one is always present (empty when the match has none); to do this for many matches at once use /v1/{game}/matches/bulk.

Only the detail route offers this: a match row from /v1/{game}/matches already carries team_a_name, team_b_name, team_a_short, team_b_short and tournament_name denormalised, whereas the detail route returns bare ids.