TABtouch API.
TABtouch esports lines, normalized.
Quick answer: TABtouch esports odds are live on KashRock: match winner, map winner, map handicap, round winner, round and kills handicaps, totals and correct scores for CS2, League of Legends, Dota 2, Valorant, Rainbow Six and Call of Duty, on the same canonical ids as the other books. One key, GET /v7/{sport}/lines.
What TABtouch posts
TABtouch posts deep esports markets: match winner, per-map winners, map handicaps, round winners and handicaps, round and kills totals, correct scores and objective markets. Every price lands on the same canonical ids as the rest of the line books, prematch and in-play on one board.
Where TABtouch shows up
- : /lines: TABtouch'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 tabtouch as the leg book and price a ticket or discover +EV parlays against the rest of the market.
- : /flow: When tabtouch moves a number first, the shift and steam plays record which venue led and how far the price ran.
Endpoints
TABtouch 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 across every market TABtouch posts | book row: tabtouch |
| GET /v7/{sport}/parlays | Price or discover parlays with tabtouch as the leg book | book=tabtouch |
| GET /v7/{sport}/flow | Steam, shift, volume and whale plays where tabtouch moves lead | kind=steam|shift|volume|whale |
| GET /v7/meta | The registry entry: key, kind, supported markets | key=tabtouch |
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": 702,
"key": "tabtouch",
"display_name": "TABtouch",
"status": "active",
"aliases": [
"tabtouch",
"tabtouch.mobi",
"tab touch"
],
"logo": "https://www.kashrock.com/logos/tabtouch.png"
}Reading it honestly
The booksobject on /lines reports each venue's presence, row count, and age in seconds on every call. When TABtouch 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 thetabtouchrows - : Compare against the consensus fair price on the same
kr_match_id
Quick reference
| Field | Value |
|---|---|
| Book key | book=tabtouch |
| Surfaces | /lines, /parlays, /flow |
| Registry | /v7/meta key=tabtouch |
| 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.
