EsportsScore.gg API

Base URL: https://esportsscore.citranagakencana.com/api/v1

curl "https://esportsscore.citranagakencana.com/api/v1/matches?status=live" \
  -H "Authorization: Bearer $API_KEY"

curl "https://esportsscore.citranagakencana.com/api/v1/tournaments/<tournament-slug>/standings"

Every entity is addressable by id or by its slug (/teams/<team-slug>). Slugs may change — old ones keep resolving — while ids never do, so store ids.

Send an API key as Authorization: Bearer <key> or X-API-Key: <key>. Keys are server-side secrets: never ship them in browser or mobile code. Ask the operator of this site for a key; each consumer gets its own client with its own limits and usage reporting.

Requests without a key are accepted with a lower, per-address limit. The realtime stream, live snapshots and search always accept keyless requests (this website uses them from the browser).

Limits are per minute with bursts allowed: a client may spend its whole allowance at once, which then refills continuously. Keyless requests: 120 per minute per address. Keys: 600 per minute per client unless agreed otherwise. Up to 50 realtime streams may be open per address.

Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (seconds until the allowance is full). Over the limit you get 429 with Retry-After in seconds.

• Single objects come as { data }, lists as { data: [...], meta }.
• Lists are paginated with cursors: pass meta.nextCursor back as cursor until it is null. Cursors are opaque; limit is 1–100 (default 25).
• Timestamps are ISO-8601 in UTC; calendar dates are YYYY-MM-DD; tournaments state their timezone.
• Objects that change carry a version; within one object, a higher version is always newer.
• Terminology is per game (terminology on games and matches): a MOBA plays games, a tactical shooter maps, a battle royale a matchday of games.
• Draft and private tournaments never appear. Unlisted tournaments are reachable by id or slug but not listed.

Responses carry a weak ETag; send it back as If-None-Match to get 304 Not Modified without a body. Lists may be served from shared caches for up to 30 seconds and details for 15 seconds; live endpoints and the stream are never cached. For anything time-critical, use the stream.

Errors use one envelope; branch on code, not on messages, and quote requestId (also in the X-Request-Id header) when asking for help.

{ "error": { "code": "NOT_FOUND", "message": "Match not found", "requestId": "…" } }

GET /api/v1/stream?channels=… is a Server-Sent Events stream. Channels: live (every live match, summaries at most once per second per match), game:<id>, tournament:<id> and contest:<matchId> (every change, immediately).

1. Connect. After you are subscribed the server sends ready.
2. Then fetch the current state from /api/v1/live/snapshots?keys=… (for example match:<id>,standings:<stageId>). Events that arrive meanwhile are not lost: apply any event whose aggregate.version is higher than what you hold.
3. Events (match.updated, score.updated, segment.completed, standing.updated, bracket.updated, …) carry the full object in payload. Ignore duplicates by event id.
4. ping arrives every 20 s; reconnect if nothing arrives for 45 s. A sync frame means the server may have missed events: fetch snapshots again. reconnect asks you to reconnect (deploys).

const es = new EventSource("https://esportsscore.citranagakencana.com/api/v1/stream?channels=contest:" + matchId);
es.addEventListener("ready", async () => {
  const res = await fetch("https://esportsscore.citranagakencana.com/api/v1/live/snapshots?keys=match:" + matchId);
  apply((await res.json()).data["match:" + matchId]);
});
es.addEventListener("match.updated", (e) => {
  const event = JSON.parse(e.data);
  if (event.aggregate.version > current.match.version) apply(event.payload);
});

Building something on top of this data? The operators behind EsportsScore.gg issue keys with higher limits on request.