Live data
Show score, kills, deaths, assists and in-game events for esports matches as they play.
Starts on
Hobby and up
Credits per call
10
Endpoint
GET /v7/{sport}/liveMCP tool
v7_liveBy plan
Hobby is 15 seconds behind. Builder, Pro and Quant are real time.
Limits
Live stats exist only for matches a live source covers. A higher plan adds speed and capacity, never coverage for a match that has none.
1. Find live matches
curl "https://kashrock.up.railway.app/v7/cs2/matches?status=live" -H "x-api-key: $KASHROCK_API_KEY"Take kr_match_id from each match. GET /v7/all/live lists live games on every title in one call.
2. Read one match
curl "https://kashrock.up.railway.app/v7/cs2/live?game=kr_cs2_...&include=boxscore" \
-H "x-api-key: $KASHROCK_API_KEY"include takes boxscore, events, frame, odds, odds_history or streams. Blocks nest per game at games[i].include.<name>. Events come back as an array of { ts, type, side, info, map }, for example kills and towers.
3. Handle a match with no stats
Every game says whether live stats are flowing:
{ "kr_match_id": "kr_dota2_...", "has_live_stats": false, "reason": "feed_stale" }When has_live_stats is false, show the match without stats and say why. Do not retry in a loop, and do not suggest an upgrade: no plan adds coverage for a match.
4. Stop polling
On Builder and up, subscribe to the same match on the live WebSocket and get pushes instead of polling. Hobby reads live data 15 seconds behind; data_delay on the response says so.
Endpoint reference: /docs/endpoints/live.
