Esports WebSocket API.
Subscribe to a match. Get every change pushed.

Open one socket, subscribe to a match by kr_match_id, and get a snapshot, then a push each time the frame, box score, odds or status changes. No polling loop to tune.

Why this surface exists

Polling a live board every second wastes requests and still lags. A socket sends only what changed, the moment it changes.

What the record represents

Every message has op. Updates add sport, game_id, type, ts and data, so one handler can route frames, box scores, odds and status.

Core endpoints

Connect to WS /v7/live/ws with an x-api-key header, or with ?ticket= from POST /v7/ws-ticket in a browser.

EndpointPurposeKey filters
WS /v7/live/wsLive pushes for the matches you subscribe toBuilder+
POST /v7/ws-ticketShort ticket for browsers that cannot set headersBuilder+
subscribe game_id=*Every live match in a titlePro+
subscribe board=linesPushed changes to the lines board (props for props)Builder+

Canonical IDs

  • : game_id is a kr_match_id
  • : player_id in box scores is kr_pl_*
  • : the same IDs as /v7/{sport}/live and /props

Sample payload

A frame update pushed for a live CS2 match, trimmed from a real message.

FieldExampleUsed for
ophello | snapshot | updateMessage kind
typeframe | boxscore | odds | statusWhat changed, on update
game_idkr_cs2_…The match, as a KashRock ID
datathe changed stateScore, players, odds or status
GET /v7/live/ws
{
  "op": "update",
  "sport": "cs2",
  "game_id": "kr_cs2_forze-reload-vs-wbt-academy-22-11-2026",
  "type": "frame",
  "ts": "2026-11-22T11:57:46.689320+00:00",
  "data": {
    "state": "live",
    "upstream_ts": "2026-11-22T11:57:38+00:00",
    "blue": {
      "kills": 0,
      "map_score": 0,
      "series_score": 2
    },
    "red": {
      "kills": 1,
      "map_score": 0,
      "series_score": 0
    }
  }
}

Comparing sources

The socket pushes the same live state that GET /v7/{sport}/live returns, so you can poll first and switch later.

SourceSchemaBest use
Polling /liveOne request per tickSimple dashboards
WebSocketOne connection, pushed changesLive apps and alerts
MCP get_live_wsReturns the URL, auth and subscribe messagesAgents that hand off to code

How to use it

Live pushes are not settlement. Grade props from /v7/{sport}/results after the match.

Operational practices

  • : Send {"op":"ping"} to keep the socket open
  • : Reconnect and resubscribe on close
  • : Keep the key on your server

Quick reference

WS /v7/live/ws, then {"op":"subscribe","sport":"cs2","game_id":"<kr_match_id>"}. Get your free key.

Start Building

  1. 1. Get a free key. Sandbox needs no card and reads props and matches on every title. Get A Free Key
  2. 2. Make the first call.
    curl -H "x-api-key: $KASHROCK_API_KEY" \
      "https://kashrock.up.railway.app/v7/cs2/matches?status=upcoming&limit=5"
  3. 3. Pick a guide. Quickstart, Player Props, Live Data, Odds And Lines, WebSockets, MCP For AI Agents. Using an AI agent? Set it up here.
  4. 4. Coming from another API? KashRock vs Cito API, KashRock vs PandaScore, KashRock vs OpticOdds, KashRock vs The Odds API. Plans and limits are on the Pricing Page.

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.

Frequently asked questions

Which plan has the WebSocket?

Builder and up. Builder allows 2 connections and 5 matches, Pro 10 and 25 plus the whole board, Quant 20 and 50. Sandbox and Hobby keys are refused at the handshake.

How do I connect from a browser?

Get a short ticket from POST /v7/ws-ticket on your server, then connect with ?ticket= so the key never reaches the browser.

What if a match has no live stats?

You get a status push that says so, for example stats_available false with a reason. No plan adds coverage for a match that has none.

Is there a runnable example?

Yes. The CS2 live dashboard template lists live matches, prints the board and follows one match over the socket.