Dexsport API.
Dexsport esports lines, normalized.
Quick answer: Dexsport esports odds are live on KashRock: match winner, map markets, handicaps and correct scores for CS2, Mobile Legends, Dota 2 and more, on the same canonical ids as the other books. One key, GET /v7/{sport}/lines.
What Dexsport posts
A crypto-native book with a deeper esports menu than most: Dexsport's prices land on canonical ids next to the consensus fair price, with a deeplink on every quote.
Where Dexsport shows up
- : /lines: Dexsport's price per market next to the consensus fair price, the books object reports its row count and age in seconds on every call.
- : /parlays: Name dexsport as the leg book and price a ticket or discover +EV parlays against the rest of the market.
- : /flow: When dexsport moves a number first, the shift and steam plays record which venue led and how far the price ran.
Endpoints
Dexsport is read through the shared v7 surface: no book-specific integration, one X-API-Key header on every call.
| Endpoint | What it returns | Key filter |
|---|---|---|
| GET /v7/{sport}/lines | Dexsport's price per market next to the consensus fair price: correct_score via market= | books.dexsport |
| GET /v7/{sport}/parlays | Price a ticket or discover parlays with dexsport as the leg book | leg book |
| GET /v7/{sport}/flow | Steam, shift, volume, and whale plays where dexsport moves lead | - |
| GET /v7/meta | The registry entry: key, kind, supported markets | key=dexsport |
Live in the book registry
The real /v7/meta entry: the key, kind, and what the book supports, exactly as the API reports it.
{
"book_id": 311,
"key": "dexsport",
"display_name": "Dexsport",
"aliases": [
"dex sport",
"dexsport.io"
],
"logo": "https://www.kashrock.com/logos/dexsport.png",
"kind": "sportsbook",
"supports": [
"lines",
"parlays"
]
}Reading it honestly
The booksobject on /lines reports each venue's presence, row count, and age in seconds on every call. When Dexsport has nothing posted for a board, the response says so instead of hiding the gap: an empty board is an answer, not an error.
Start in minutes
- : Create a key on Pricing : Sandbox is $0; book lines need Hobby and up
- : Call
GET /v7/{sport}/linesand read thedexsportrows - : Compare against the consensus fair price on the same
kr_match_id
Quick reference
| Field | Value |
|---|---|
| Book key | book=dexsport |
| Surfaces | /lines, /parlays, /flow |
| Registry | /v7/meta key=dexsport |
| Plan | Hobby and up, from $29.99/mo |
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.