Sandbox key

Try the API on a fixed sample of past CS2 matches with a shared key that needs no account, or with a free sandbox key of your own.

Try it now, no account

The public sample key is eo_sample_public. It needs no account, and it reads a fixed sample of past matches, the same sample a sandbox key reads. It is shared by everyone who uses it. For evaluation; our Terms apply.

bash
curl -H "Authorization: Bearer eo_sample_public" \
  "https://api.esportsodds.gg/v1/cs2/coverage"

To see a match, list one from the sample, then fetch it by its id. The list needs tournament set to one of the sample's events: the call below uses the first, and What it reads lists them.

bash
curl -H "Authorization: Bearer eo_sample_public" \
  "https://api.esportsodds.gg/v1/cs2/matches?tournament=019f23d2-5a32-71d0-ac4b-dfc7eb5dd3f0&status=completed&limit=1"

# Put the id from that response in place of MATCH_ID.
curl -H "Authorization: Bearer eo_sample_public" \
  "https://api.esportsodds.gg/v1/cs2/matches/MATCH_ID"

Limits of the sample key

Because everyone shares the key, its limits are per network address and for everyone together:

  • 2 requests a second from each network address, with a burst of 10.
  • 500 requests a UTC day from each network address, and 10,000 a UTC day for everyone together. Each response carries X-Quota-Limit: 500, your address's allowance for the day, and X-Quota-Remaining counts it down.
  • Past a daily limit, a call answers 429 sample_quota_exceeded. It is not counted, and Retry-After gives the seconds until 00:00 UTC, when the day's counts reset.
  • A call outside the sample answers 403 sandbox_scope, which is not counted. A sandbox key gets the same answer.
  • There is no WebSocket: POST /v1/cs2/ws-token answers 403 sandbox_scope.

Want a key that is yours alone? A sandbox key is free with an account, and a paid plan reads current data.

Your own sandbox key

A sandbox key is a free API key for trying the API. It reads a fixed sample of past matches with the same endpoints and response shapes as a paid key, so the code you write against it works unchanged when you subscribe. No card is needed, and nothing is ever charged for it.

It is not a trial of a paid plan: it never turns into a subscription. Current and full data come with a paid plan.

Get one

Sign up at esportsodds.gg, accept the Terms, and click Create sandbox key in the dashboard. It shows the key with a first call in curl and Python to copy. Copy the key when it appears: it is shown once. Keys start with eo_sandbox_. There is one per account. Lost it? Email support@esportsodds.gg for a new one.

bash
export ESPORTSODDS_API_KEY="eo_sandbox_..."
curl -H "Authorization: Bearer $ESPORTSODDS_API_KEY" \
  "https://api.esportsodds.gg/v1/cs2/matches?tournament=019f23d2-5a32-71d0-ac4b-dfc7eb5dd3f0&limit=5"

The Python client reads the same ESPORTSODDS_API_KEY. Its sandbox_tour.py example prints an event's latest results, then one match's veto, maps and top players, in two requests. After pip install esportsodds, from a clone of that repository:

bash
python examples/sandbox_tour.py 019f23d2-5a32-71d0-ac4b-dfc7eb5dd3f0

The client's quickstart asks for upcoming matches, which are outside the sample, so start here instead.

What it reads

The sample is every completed match of two events, about a hundred matches in all:

EventTournament id
Esports World Cup 2026019f23d2-5a32-71d0-ac4b-dfc7eb5dd3f0
CCT Europe 2026 Series 7019ff0f2-3b3e-75ec-b89e-a9fefaeee00a

One event is top tier and one is lower tier, so you see what a full match looks like and what a thinner one looks like. We may change the sample; the events above are the current one.

A sandbox key can call:

EndpointInside the sample when
GET /v1/cs2/matches?tournament= is a sample event
GET /v1/cs2/matches/{id} and its /maps, /stats, /vetoes, /rounds, /history, /depth, /lineups, /streamsthe match is in the sample
GET /v1/cs2/tournaments/{id} and /tournaments/{id}/teamsthe id is a sample event
GET /v1/cs2/odds?match= is a sample match
GET /v1/cs2/coverage, GET /v1/cs2/model/metricsalways

Follow any match from that list into its sub-resources:

bash
curl -H "Authorization: Bearer $ESPORTSODDS_API_KEY" \
  "https://api.esportsodds.gg/v1/cs2/matches/MATCH_ID/stats"

Limits

  • 2,000 requests in total, for the life of the key. It does not reset. X-Quota-Limit and X-Quota-Remaining on each counted response show where you are.
  • 5 requests per second, with a burst of 20 (X-RateLimit-* headers, as on any key).
  • No WebSocket: POST /v1/cs2/ws-token answers 403 sandbox_scope.
  • Once the 2,000 are used, every call answers 429 sandbox_quota_exceeded, inside the sample or not.

Errors a sandbox key can get

StatusCodeMeaningWhat to do
403sandbox_scopeThe request is outside the sample (another event, a current match, a team or player route). Not counted against your 2,000. The message names the sample's events and a call that works, /v1/cs2/matches?tournament=<id>.Ask for something inside the sample, or subscribe for current data from your dashboard.
429sandbox_quota_exceededAll 2,000 requests are used. There is no Retry-After: the allowance does not come back.Subscribe for a monthly allowance from your dashboard.

Every other error behaves as on a paid key: see Errors.

Moving to a paid key

When you subscribe, create a paid key in the dashboard and swap it in for ESPORTSODDS_API_KEY. Paths, parameters and response shapes do not change; the only difference is that every match, event, team and player is in reach.