CS2 API documentation.

Get a free key at citoapi.com, then send it in the x-api-key header to any /cs2 route. GET /cs2 returns what the API covers; GET /cs2/matches/live returns matches in progress.

curl -s "https://api.citoapi.com/api/v1/cs2/matches/live" -H "x-api-key: $CITO_API_KEY"

import os, requests

r = requests.get("https://api.citoapi.com/api/v1/cs2/matches/live",
                 headers={"x-api-key": os.environ["CITO_API_KEY"]}, timeout=10)
r.raise_for_status()
for m in r.json()["data"]:
    print(m["team1Name"], m["team1Score"], "-", m["team2Score"], m["team2Name"])

const res = await fetch("https://api.citoapi.com/api/v1/cs2/matches/live", {
  headers: { "x-api-key": process.env.CITO_API_KEY },
})
const { data } = await res.json()
for (const m of data) console.log(m.team1Name, m.team1Score, "-", m.team2Score, m.team2Name)

Send the key in the x-api-key header on every request; Authorization: Bearer <key> also works. Keys start with cito_ and are 69 characters long. Keep the key on a server: the API does not allow browser calls from other origins.

Successful responses are { success: true, data, meta }. Lists put paging in meta: page, limit, total, totalPages, hasNext and hasPrev. Pass page and limit to move through results.

{
  "success": true,
  "data": [
    {
      "rank": 1,
      "teamName": "Spirit",
      "points": 1000,
      "change": 0
    },
    {
      "rank": 2,
      "teamName": "Vitality",
      "points": 676,
      "change": 0
    }
  ],
  "meta": {
    "page": 1,
    "limit": 2,
    "total": 251,
    "hasNext": true,
    "ranking": "world",
    "rankingDate": "2026-10-03"
  }
}

Errors return { success: false, error: { code, message, status, docs } } with a matching HTTP status. The code is stable and safe to branch on; the message is for people.

Limits are per plan: 10 requests a minute and 500 a month on Free, up to 400 a minute and 1,000,000 a month on Scale. Responses carry X-RateLimit-Remaining; a 429 adds Retry-After, X-RateLimit-Limit and X-RateLimit-Reset.

Every match, map, team, player and event has a stable ID such as cs2-match-2398722 or cs2-team-9565. Teams, players and events also accept a readable slug, so /cs2/teams/vitality and /cs2/players/zywoo work as well as their IDs.

Four ways, from simplest to most real-time: poll GET /cs2/matches/live, keep the SSE stream at /cs2/live/stream open (every plan), open the WebSocket at /cs2/live/ws (Scale, or Pro with the add-on), or receive webhooks (Pro and Scale).

The CS2 API endpoints page lists every route grouped by job, and the complete reference with parameters lives on citoapi.com/docs/api/cs2. AI agents can use the Cito MCP server: npx cito-mcp install.