BetWhale API.
BetWhale esports lines, normalized.
Quick answer: BetWhale esports odds are live on KashRock — match winner, map, rounds and kills lines plus tournament outrights for CS2, League of Legends, Dota 2, Valorant and more, on the same canonical ids as the other 24 books. One key, GET /v7/{sport}/lines.
What BetWhale posts
BetWhale posts team mainlines — match winner, map and rounds markets, kills handicaps — plus tournament outrights like Winner and To Reach Final. The outright board is served as the outrightmarket on /lines with BetWhale's own prices, ordered shortest first, with no cross-book consensus.
Where BetWhale shows up
- —/lines — BetWhale'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 betwhale as the leg book and price a ticket or discover +EV parlays against the rest of the market.
- —/flow — When betwhale moves a number first, the shift and steam plays record which venue led and how far the price ran.
Endpoints
BetWhale is read through the shared v7 surface — no book-specific integration, no upstream fetch on the request path.
| Endpoint | What it returns | Key filter |
|---|---|---|
| GET /v7/{sport}/lines | Per-book prices and the consensus view; market=outright for futures | book row: betwhale |
| GET /v7/{sport}/parlays | Price or discover parlays with betwhale as the leg book | book=betwhale |
| GET /v7/{sport}/flow | Steam, shift, volume and whale plays where betwhale moves lead | kind=steam|shift|volume|whale |
| GET /v7/meta | The registry entry — key, kind, supported markets | key=betwhale |
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": 317,
"key": "betwhale",
"display_name": "BetWhale",
"status": "active",
"aliases": [
"bet whale",
"betwhale.ag"
]
}Reading it honestly
The booksobject on /lines reports each venue's presence, row count, and age in seconds on every call. When BetWhale 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 thebetwhalerows - —Compare against the consensus fair price on the same
kr_match_id
Quick reference
| Field | Value |
|---|---|
| Book key | book=betwhale |
| Surfaces | /lines, /parlays, /flow |
| Registry | /v7/meta key=betwhale |
| Plan | Hobby and up, from $29/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.
