Polymarket API.
Crowd-priced mainlines for accurate models.
Quick answer: Polymarket publishes market data; KashRock normalizes its esports events into GET /v6/esports/{sport}/props?book=polymarket and the consensus on GET /v6/esports/{sport}/lines — including the CFTC-regulated polymarket_us venue on the same kr_match_id space.
GET /v6/esports/{sport}/props?book=polymarket and consensus GET /v6/esports/{sport}/lines.Does Polymarket have an API?
Polymarket publishes market data; KashRock normalizes its esports events into GET /v6/esports/{sport}/props?book=polymarket and the consensus on GET /v6/esports/{sport}/lines — including the CFTC-regulated polymarket_us venue on the same kr_match_id space.
What you get
- —Match and map markets as odds and implied probability.
- —Joins cleanly with Kalshi and Thunderpick on the /lines consensus path.
- —Hardens projections with live prediction-market prices — not guesses.
Endpoints
One key covers Polymarket and the other 24 books — every row comes back on the same schema, so nothing about the read is Polymarket-specific.
| Endpoint | What it returns | Key filter |
|---|---|---|
| GET /v6/esports/cs2/props?book=polymarket | Live Polymarket board, normalized to the shared prop schema | book=polymarket |
| GET /v6/esports/{sport}/lines | Consensus lines with Polymarket priced alongside the other venues | sport |
| GET /v7/meta | The registry entry for Polymarket — key, kind, and supported markets | key=polymarket |
A live Polymarket prop
A real Polymarket 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_5e73ad47ceb5bce8",
"player_name": "Quintessence",
"stat_type": "MONEYLINE_MAP_1",
"line": null,
"odds": 104,
"direction": "home",
"team": "Quintessence",
"book_name": "Polymarket",
"event_time": "2026-09-12T15:30:00+00:00"
}
]
}Polymarket 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 Polymarket 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=polymarketwith 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=polymarket |
| Endpoint | GET /v6/esports/cs2/props?book=polymarket |
| 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. Pair with Kalshi API and Thunderpick API. Odds hub: Esports Odds API.