KashRock V7: one schema, every endpoint
Published · by KashRock
V7 is a condense-and-harden release, not a rebuild. About forty routes collapse into twelve sport routes plus /v7/meta and a live WebSocket. Every endpoint reads a cache the workers already filled: a response is a read, not a fan-out: and every route answers in real time.
One route per question
Each route answers one question, in one shape: matches, props, lines, parlays, flow, live, players, teams, history, results, breakdown. Params behave the same on all of them : fields, include, limit/cursor, format=slim|full.
curl -H "X-API-Key: YOUR_KEY" \ "https://kashrock.up.railway.app/v7/cs2/matches?status=upcoming"
What is genuinely new
Parlays prices a ticket or discovers ranked +EV parlays on the book you name: the fair price always excludes the leg book, so a book never grades its own number.
Flow surfaces steam, shift, volume and whale plays: where a price moved, how far, and which venue led, with the thresholds each play cleared.
Teams is the team-level counterpart to player research: form, roster, map pool, head-to-head, and main lines with open/close per book.
Breakdown pages are free and keyless: every published match, team and H2H page is a plain GET, and the same facts render our public pages.
Bet365 joined the line-book set: the registry now covers DFS apps, sportsbooks, and prediction markets, on one key, all priced on the same canonical ids.
What stayed the same
Every V6 route keeps working with its current response shape: existing integrations do not change. Ids are permanent. And an empty board still answers honestly: available: false plus a reason, never a silent 200.
The full contract is in the V7 API reference; the free tier is on pricing.
KashRock is an independent data provider, not a sportsbook. Data is for informational and analytical use.