Esports props API.
DFS and book props — one propId schema.
Why this surface exists
A prop without a stable propId cannot be graded or CLV'd. Props is where the board becomes durable.
What the record represents
Rows lead with propId, stat_type, line, direction, book, and canonical player/match ids.
Core endpoints
GET /v7/{sport}/props with board/view filters.
| Endpoint | Purpose | Key filters |
|---|---|---|
| GET /v7/{sport}/props | Live prop board | board=, view=, book= |
| GET /v7/{sport}/props?view=gaps | DFS book-vs-book spreads | Hobby+ |
| GET /v7/{sport}/results | Settled grades |
Canonical IDs
- —propId
- —kr_pl_*
- —kr_match_id
Sample payload
PrizePicks CS2 maps 1–2 kills line with propId and direction on the row.
| Field | Example | Used for |
|---|---|---|
| propId | kr_prop_… | Stable offer family |
| stat_type | CS2_KILLS_MAPS_1_2 | Sport-prefixed market |
| line / direction | 24.5 / over | Threshold and side |
| book_name | prizepicks | Venue |
{
"source": "kashrock",
"sport": "cs2",
"props": [
{
"propId": "kr_prop_195304f116d9",
"player_name": "Mercury",
"stat_type": "CS2_KILLS_MAPS_1_2",
"line": 24.5,
"book_name": "prizepicks",
"direction": "over"
}
]
}Comparing sources
DFS apps and sportsbooks on the coverage list — one schema.
| Source | Schema | Best use |
|---|---|---|
| Per-book scrapes | Break often | Fragile |
| One DFS app export | One venue | Narrow |
| KashRock props | Multi-book, KR ids | Products |
How to use it
Bind propId at placement; settle with /results.
Operational practices
- —Store propId + direction
- —Use view=gaps for shopping
- —Sandbox = CS2 eval
Quick reference
GET /v7/cs2/props returns the live prop board with propId. Get your free key.
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.