Veikkaus API.
Veikkaus esports lines, normalized.
Quick answer: Veikkaus esports odds are live on KashRock: match winner, map and rounds lines for CS2, Dota 2, League of Legends, Rainbow Six Siege and Call of Duty on the same canonical ids as the other books. One key, GET /v7/{sport}/lines.
What Veikkaus posts
Veikkaus posts a deep esports board under Pitkäveto: match winner, per-map winners, map handicaps, total maps, total rounds per map and series, kill totals, round handicaps, correct score and tournament outrights. Every price lands on the same kr_match_id and market names as the rest of the line books.
Where Veikkaus shows up
- : /lines: Veikkaus'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 veikkaus as the leg book and price a ticket or discover +EV parlays against the rest of the market.
- : /flow: When veikkaus moves a number first, the shift and steam plays record which venue led and how far the price ran.
Endpoints
Veikkaus 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 | book row: veikkaus |
| GET /v7/{sport}/parlays | Price or discover parlays with veikkaus as the leg book | book=veikkaus |
| GET /v7/{sport}/flow | Steam, shift, volume and whale plays where veikkaus moves lead | kind=steam|shift|volume|whale |
| GET /v7/meta | The registry entry: key, kind, supported markets | key=veikkaus |
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": 907,
"key": "veikkaus",
"display_name": "Veikkaus",
"status": "active",
"aliases": [
"veikkaus.fi",
"veikkaus sport",
"pitka veto"
]
}Reading it honestly
The booksobject on /lines reports each venue's presence, row count, and age in seconds on every call. When Veikkaus 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 theveikkausrows - : Compare against the consensus fair price on the same
kr_match_id
Quick reference
| Field | Value |
|---|---|
| Book key | book=veikkaus |
| Surfaces | /lines, /parlays, /flow |
| Registry | /v7/meta key=veikkaus |
| 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.
