Rainbow Six API.
R6 props and odds without stitching feeds.
Rainbow Six data usually means a stats scrape for the competitive side and a separate pull for book lines. A Siege API should hand you normalized markets, schedules and player records on one schema — with the same canonical ids whether the row came from a DFS board or a prediction market.
Why a Rainbow Six API needs a schema
R6 has a real esports calendar — regional leagues, Majors, SI — but book coverage is thinner than CS2, so the feeds that exist are scattered across DFS apps and prediction markets. A normalized layer turns that patchwork into one queryable board.
Practical rule: when only Kalshi lists an R6 match, the honest answer is a Kalshi price — not a padded-out board pretending five books priced it.
What we normalize today
Match/series structure, sport-prefixed market keys (R6_*), and canonical player, team and match ids. DFS kill props and sportsbook mainlines share the same schema and join on the same kr_match_id.
Core R6 endpoints
Paths under /v7/r6/. Same client and filters as CS2 and Valorant — sport is just a path segment.
| Endpoint | Purpose | Key filters |
|---|---|---|
| GET /v7/r6/props | DFS player props when listed | book, market, player |
| GET /v7/r6/matches | Schedule / live / completed | status, date, team |
| GET /v7/r6/lines | Team lines + consensus (Hobby+) | market, view |
| GET /v7/r6/players | Player directory & rankings | q, sort, market |
| GET /v7/r6/results | Settled prop grades | grade, from, to |
Canonical IDs
- —kr_match_id / canonical_event_id for series joins
- —R6_* market keys carry the map scope (MAPS_1_2, MAP_N)
- —kr_pl_* player ids stay stable across books and seasons
Sample live R6 prop
Live PrizePicks R6 prop from production — Nuers over 18.0 kills across maps 1–2 against Cloud9, on the canonical match id.
| Field | Example | Used for |
|---|---|---|
| propId | kr_prop_8cd5410192f9 | Stable market key across books |
| stat_type | R6_KILLS_MAPS_1_2 | Sport-prefixed market with map scope |
| kr_match_id | kr_r6_cloud9-vs-darkzero-08-10-2026 | Canonical match join |
| book_name | PrizePicks | Venue |
{
"source": "kashrock",
"sport": "r6",
"props": [
{
"propId": "kr_prop_8cd5410192f9",
"player_name": "Nuers",
"stat_type": "R6_KILLS_MAPS_1_2",
"line": 18,
"odds": -137,
"direction": "over",
"team": "DarkZero",
"opponent": "Cloud9",
"book_name": "PrizePicks",
"kr_match_id": "kr_r6_cloud9-vs-darkzero-08-10-2026",
"event_time": "2026-10-08T15:00:00.000Z"
}
]
}Comparing R6 sources
Use community stats sites for deep competitive metrics. Use KashRock when you need book markets, schedules and settled results on one schema.
| Source | Schema | Best use |
|---|---|---|
| R6 stats sites | Strong competitive metrics | KPR / maps — not book lines |
| Single-book scrape | One venue, brittle | Prototypes |
| KashRock R6 API | Normalized markets + IDs | Props, odds, models |
Settlement patterns
Kills props settle from the map record under the book's own settlement rules version. Only grade when the venue actually offered the line and the map exists in the vault.
Operational practices
- —Check the books object per board before assuming DFS depth on R6
- —Use /lines on Hobby+ for consensus fair odds on mainlines
- —Poll /results by graded_at for settlement joins
Quick reference
GET /v7/r6/props for listed markets, /matches for schedule, /lines for consensus. Transparent pricing.
If you need a normalized feed instead of another UI wrapper, the Esports API exposes live boards, schedules, and history on one schema — with the IDs and outcome patterns that keep backtests and grading honest. Start free on Sandbox, or see published pricing.
