Steam Web API empty match data: why, and the fix.

"n/a" from GetNextMatchSharingCode means there is no match newer than the knowncode you sent; it is a normal answer, not a failure. Some client implementations also treat HTTP 202 from this method as "no new match yet". An empty body elsewhere usually means the data is not exposed through the Web API at all.

The Steam Web API's CS2 interfaces (ICSGOPlayers_730, ICSGOServers_730, ICSGOTournaments_730, IEconItems_730) expose share codes, server status, Major pick'em layouts and items. None of them return a scoreboard. A share code decodes to a match ID, a reservation ID and a TV port, which identify a replay but contain no stats.

For your own matchmaking games: walk share codes with GetNextMatchSharingCode, then download and parse each replay demo. For professional matches: call a CS2 esports API, which already holds the scores, maps and player lines.

import os, requests

H = {"x-api-key": os.environ["CITO_API_KEY"]}
API = "https://api.citoapi.com/api/v1/cs2"

match = requests.get(f"{API}/matches/results", params={"limit": 1}, headers=H).json()["data"][0]
print(match["team1Name"], match["team1Score"], "-", match["team2Score"], match["team2Name"])

stats = requests.get(f"{API}/matches/{match['id']}/player-stats", headers=H).json()["data"]
print(stats)  # kills, deaths, ADR, KAST and rating per player, per map

Those are only available through Steam: the share-code walk needs your Steam ID, your game authentication code and one known share code, and every match after it has to come from its demo. The CS2 API covers professional matches, not personal matchmaking history.

For professional matches you never call Steam, so there is no n/a and no empty body: every finished match already has its maps, scores and per-player lines. A match that is not indexed yet returns data_available: false with a reason, never a silent empty response.

curl -s "https://api.citoapi.com/api/v1/cs2/matches/results?limit=5" -H "x-api-key: $CITO_API_KEY"