Valorant API.
Markets and IDs without stitching VLR to books.
Valorant tooling usually means one scrape for VLR stats and another for book odds — then a fragile name join in the middle. A Valorant API should give you normalized markets and match structure first, and only claim player-prop depth when the books actually post it.
Why a Valorant API needs a schema
VLR is excellent for competitive metrics. It is not a book feed. If your product needs odds, you still need a normalized market layer with stable IDs.
Practical rule: if a DFS book has no Valorant board today, the honest API response is empty for that book — not a hallucinated kill line.
What we normalize today
Match/series structure, sport-prefixed market keys (VAL_*), and canonical entities. Player-prop depth appears when venues list it; mainlines and handicaps are the reliable baseline.
Core Valorant endpoints
Paths under /v6/esports/valorant/. Same client as CS2 and LoL.
| Endpoint | Purpose | Key filters |
|---|---|---|
| GET /v6/esports/valorant/props | Live markets / props when listed | book, market |
| GET /v6/esports/valorant/matches | Schedule / live / completed | status, dates |
| GET /v6/esports/valorant/lines | Consensus odds (Hobby+) | — |
| GET /v6/esports/valorant/players/{slug}/gamelogs | Map history when available | limit |
Canonical IDs
- —canonical_event_id / matchup_key for series joins
- —VAL_* market keys
- —Dual-index metrics identity — not nickname-only
Sample live Valorant market
Live Polymarket Valorant market from production (example when DFS books are dark on the title).
| Field | Example | Used for |
|---|---|---|
| propId | kr_prop_0c5a6d27fce7 | Stable market key |
| stat_type | VAL_MAP_HANDICAP | Sport-prefixed market |
| line | -1.5 | Handicap / total threshold |
| book_name | Polymarket | Venue |
{
"source": "kashrock",
"sport": "valorant",
"props": [
{
"propId": "kr_prop_0c5a6d27fce7",
"player_name": "Any Questions Gaming",
"stat_type": "VAL_MAP_HANDICAP",
"line": -1.5,
"odds": -102,
"direction": "away",
"team": "Any Questions Gaming",
"book_name": "Polymarket",
"event_time": "2026-09-12T09:00:00.000Z"
}
]
}Comparing Valorant sources
Use VLR for KPR-style metrics. Use KashRock when you need book-native markets and schedules on one schema.
| Source | Schema | Best use |
|---|---|---|
| VLR | Strong competitive stats | KPR / agents — not book lines |
| Single-book scrape | One venue, brittle | Prototypes |
| KashRock Valorant API | Normalized markets + IDs | Odds, schedules, models |
Settlement patterns
Settle map markets from finalized match results. For player props, only grade when the venue actually offered the line and the map record exists.
Operational practices
- —Check coverage per book before assuming DFS depth
- —Use /lines on Hobby+ for consensus fair odds
- —Cache completed matches longer than live boards
Quick reference
GET /v6/esports/valorant/props for listed markets, /matches for schedule, /lines for consensus. Transparent pricing.
If you need a normalized feed instead of another UI wrapper, KashRock 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.