Thunderpick API.
Sportsbook mainlines for sharper models.
Quick answer: Thunderpick does not publish a self-serve odds API for its esports markets. KashRock normalizes Thunderpick esports lines and props alongside 24 other books — query GET /v6/esports/{sport}/props?book=thunderpick with a free Sandbox key.
GET /v6/esports/{sport}/props?book=thunderpick and consensus GET /v6/esports/{sport}/lines.Does Thunderpick have an API?
Thunderpick does not publish a self-serve odds API for its esports markets. KashRock normalizes Thunderpick esports lines and props alongside 24 other books — query GET /v6/esports/{sport}/props?book=thunderpick with a free Sandbox key.
What you get
- —Match and map winners, totals, handicaps, plus player props where listed.
- —Normalized odds and lines next to prediction-market mainlines.
- —Feeds model priors with live sportsbook prices — not a single-book scrape.
Endpoints
One key covers Thunderpick and the other 24 books — every row comes back on the same schema, so nothing about the read is Thunderpick-specific.
| Endpoint | What it returns | Key filter |
|---|---|---|
| GET /v6/esports/cs2/props?book=thunderpick | Live Thunderpick board, normalized to the shared prop schema | book=thunderpick |
| GET /v6/esports/{sport}/lines | Consensus lines with Thunderpick priced alongside the other venues | sport |
| GET /v7/meta | The registry entry for Thunderpick — key, kind, and supported markets | key=thunderpick |
A live Thunderpick prop
A real Thunderpick row from production — the same shape every other book returns, with the canonical propId that lets you line-shop across venues.
{
"source": "kashrock",
"sport": "cs2",
"props": [
{
"propId": "prop_da111f08efb414ec",
"player_name": "SINQU Esports",
"stat_type": "MONEYLINE",
"line": null,
"odds": 530,
"direction": "home",
"team": "SINQU Esports",
"book_name": "Thunderpick",
"event_time": "2026-09-11T17:03:00+00:00"
}
]
}Thunderpick via KashRock vs scraping it yourself
- —The app's internal endpoints change without notice — the normalized schema does not
- —Player, stat, line, direction, and team arrive already mapped to canonical KashRock ids
- —The same propId lines Thunderpick up next to every other book for comparison
- —One API key and one auth header replace per-source session handling
Start in minutes
- —Create a free Sandbox key on Pricing — $0, no card, 500 requests every UTC day
- —Call
GET /v6/esports/cs2/props?book=thunderpickwith the key in the X-API-Key header - —Filter by stat_type, player, or match — the response is the board as KashRock serves it
Quick reference
| Field | Value |
|---|---|
| Book key | book=thunderpick |
| Endpoint | GET /v6/esports/cs2/props?book=thunderpick |
| Row shape | propId, player_name, stat_type, line, direction, odds, team, event_time |
| Free tier | Sandbox $0 — 500 requests / UTC day |
| Consensus lines | Hobby and up, from $29/mo |
Consensus product: Esports Consensus API. Prediction markets: Kalshi API, Polymarket API. Line shopping: Esports Odds API.