How the esports API works

One bearer token, a versioned schema, limits you can read off every response and a WebSocket that pushes updates. Counter-Strike history back to 2020 behind it.

Auth, versioning, history and errors

Four promises the API keeps.

One bearer token, any language

Send Authorization: Bearer <key>. No OAuth, no signing, and an ?apiKey= fallback.

A schema that won't move under you

Everything under /v1/cs2/, in snake_case. A new game adds a namespace, not a new shape.

History, not a rolling window

27,000+ matches back to 2020. Odds history is append-only, from July 2026.

Errors you can branch on

Every error is a coded envelope with a stable code, and a request_id comes back on every response.

Rate limits and monthly quota

A per-key token bucket smooths bursts, and every metered response says what is left and when it resets.

  • 50,000 requests a month on Standard, 150,000 on Pro
  • Over either cap: a 429 with Retry-After in seconds
  • Nothing is billed automatically
Response headersStandard plan
$ curl -i \
    -H "Authorization: Bearer $ESPORTSODDS_API_KEY" \
    "api.esportsodds.gg/v1/cs2/matches"

HTTP/2 200
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 99
X-Quota-Limit: 50000
X-Quota-Remaining: 39873
X-Quota-Reset: 2026-12-01T00:00:00Z

39,873 of 50,000 left this month. One square is 10,000 requests.

WebSocket push updates

Subscribe to the matches you care about, and every score or line change in our feed is pushed to you, using no requests.

  1. Mint a short-lived ticketPOST /v1/cs2/ws-token
  2. Connect and subscribe{"subscribe": ["match:019f4ba2"]}
  3. Updates arrive when our feed changes{"type": "odds_update", "price": 1.68, …}

Being precise. We poll matches and the market line about once a minute, so freshness is bounded by that cadence. Every line carries the age of its inputs (input_oldest_at), typically a few minutes while a match is live. Lines from after the start are kept and flagged in_play. This is a polled feed, not a real-time one.

The CS2 odds line

One reference line per match, not a list of prices.

eo_marketLive today

The market odds line

At least two books behind every line. Appended, never overwritten, so history holds.

"source": "eo_market",
"price": 1.72,
"book_count": 4
eo_modelComing soon

Our own modeled line

In validation. It ships when it clears our accuracy bar, and appears nowhere in the API until then.

"source": "eo_model",
"status": "validating"
# not yet served, no early access

CS2 data coverage

Coverage is not uniform: a gap stays a gap, and we never fill in missing rounds.

Share of completed matches with each layer of data
LayerShare, as squaresShare of matches
Fixtures and results Every completed match carries a winner~100%
Per-map scores At least one played map91.3%
Per-player stats K/A/D, ADR, KAST, clutches, multi-kills86.2%
Per-round economy and duels Concentrated in top-tier eventsVaries
One square is 5% of completed matches.
Matches since 2020
27,000+
On CS2
20,000+
Players
5,600+
Teams
1,800+
Tournaments
1,100+
What's in the data

Make your first call today

A sandbox key reads a fixed sample of past matches, no card. Plans from $99 USD a month.