DOCS / GAMES / RAINBOW SIX SIEGE

R6 coverage. Phase 2 — schema work in progress.

Rainbow Six Siege is a Phase-2 game on our roadmap. It is seeded in the catalogue at /v1/games/r6 with status: coming_soon and ships with fixtures, results, brackets and match-stats capability flags as soon as the parser passes the production gate (7 days of clean scrapes + manual spot-check + integration tests).

Coming-soon games still return a real catalogue row at /v1/games/r6; the status field is the source of truth for what is live. Fixture and match endpoints return 200 + an empty data array with a meta.note until the cutover.

Get an API key Read the quickstart

What will land

GET /v1/tournaments?game=r6

Active R6 tournaments

BLAST R6 Major cycle, regional leagues (NAL, EUL, BR6, APAC North/South), and the open qualifier circuits Liquipedia carries.

GET /v1/matches?game=r6

Matches by game

Bo1 and Bo3 with per-map scores. Cursor pagination, never offset. Up to 200 per page.

GET /v1/matches/:id

One match

Canonical record — teams, map veto outcome, broadcast, scheduled time, final score.

GET /v1/teams/:slug

Team page

Roster, recent results, head-to-head, regional partnership.

Capability flags

R6 will land with the same feature set as CS2 — fixtures, results, match_stats and brackets. Round-by-round depth is deferred for now; the launch surface is fixture-and-result first, same posture as CS2.

Watch this space

Status flips to live after the production gate clears. The /v1/games endpoint is the canonical view — your client can poll it (or read it once at startup) to discover when R6 goes live without us shipping a separate announcement channel.

Attribution

R6 reference data is sourced from Liquipedia contributors. Every response will include a meta.sources array with article URLs and licence — same hard rule as the live games, set out in our Attribution Policy.