CS2CS2 Match TrackerGet free API key
VetoMap stats

CS2 map veto API: every ban, pick and decider.

The veto decides half the series before a round is played. Every match carries its veto in order, each ban and pick with the team that made it and the decider, and every map names the team that picked it, with half-by-half scores.

Get a free API keyRead the CS2 docs
  • Ban / pick / decider order
  • Picking team per map
  • Half scores per map
GET /cs2/matches/cs2-match-2395002200 OK
$ curl "https://api.citoapi.com/api/v1/cs2/matches/cs2-match-2395002" \ -H "x-api-key: $CITO_API_KEY"
{  "success": true,  "data": {    "id": "cs2-match-2395002",    "eventName": "IEM Cologne Major 2026",    "team1Name": "FURIA",    "team2Name": "Falcons",    "bestOf": 5,    "vetoOrder": [      {        "order": 1,        "action": "ban",        "map": "ancient",        "teamName": "FURIA"      },      {        "order": 2,        "action": "ban",        "map": "overpass",        "teamName": "Falcons"      },      {        "order": 3,        "action": "pick",        "map": "mirage",        "teamName": "FURIA"      },      {        "order": 4,        "action": "pick",        "map": "anubis",        "teamName": "Falcons"      },      {        "order": 7,        "action": "decider",        "map": "nuke",        "teamName": null      }      ...    ]  }}

Seamless Integration with our MCP Server

Give Claude, Cursor and ChatGPT the CS2 data. One command writes the MCP config; agents call live scoreboard, team map stat, opening duel and transfer tools instead of inventing match IDs, and your key stays on your machine.

MCPInstall the Cito MCP server
Claude
Cursor
OpenAI
Python
Cito API
Next.js
Discord
Slack
GitHub

Model the veto

The order, the picks and how they played out.

Veto order

vetoOrder on every match: order, action (ban, pick, decider), map and team.

Who picked each map

pickTeamId on each map, joined to its score.

Half scores

team1Halves and team2Halves per map, for side analysis.

Map pools

Team map stats: maps played, won and picked per map.

Head-to-head

Past meetings of the two teams, map by map.

Live and upcoming

The veto appears on the match as soon as it is known.

Endpoints you can ship with

Results first: open a match for its veto and maps.

Results

Finished matches with the series score and winner, every map and its score, and the player lines behind them.

View docs
  • GET/api/v1/cs2/matches/recent

    Finished matches with final series score and winner, newest first.

  • GET/api/v1/cs2/matches/{matchId}

    One match: event, teams, series score, and maps.

  • GET/api/v1/cs2/matches/{matchId}/maps

    Each map: name, score, winner, and the team that picked it.

  • GET/api/v1/cs2/matches/{matchId}/player-stats

    Per-player stats for each map: kills, deaths, ADR, KAST and rating.

  • GET/api/v1/cs2/teams/{teamIdOrSlug}/results

    One team's finished matches, newest first.

  • GET/api/v1/cs2/events/{eventIdOrSlug}/results

    Final placements and prize money of a tournament.

Frequently asked questions

Veto data

Something missing? Email support@citoapi.com.

Does the CS2 API include the map veto?

Yes. Each match has vetoOrder: every ban and pick in order with the team that made it, and the decider.

Can I see which team picked a map?

Yes. Every map carries pickTeamId, its final score and half scores.

Can I get a team's map pool?

Yes. Team map stats list maps played, won and picked per map.

More match depth

See pricing

Predict map picks

Read your first veto with a free key.

Get a free CS2 API key