Esports schedule API.
Upcoming, live, finished: on kr_match_id.
Why this surface exists
Every other endpoint hangs off the match. If the fixture id drifts, props, lines, and grades fall apart.
What the record represents
Match rows lead with kr_match_id, status, teams, competition, and scores when known.
Core endpoints
GET /v7/{sport}/matches and /matches/{ref}.
| Endpoint | Purpose | Key filters |
|---|---|---|
| GET /v7/{sport}/matches | Fixture list | status, include= |
| GET /v7/{sport}/matches/{ref} | Single match | include=prep,veto,maps |
| GET /v7/{sport}/uav | Overview bundle | match= |
Canonical IDs
- : kr_match_id
- : kr_tm_*
- : slug
Sample payload
Live CS2 fixture with kr_match_id, status=live, and both teams.
| Field | Example | Used for |
|---|---|---|
| kr_match_id | kr_cs2_… | Stable fixture id |
| status | live | upcoming | live | finished |
| team1 / team2 | names + kr_tm_* | Sides |
{
"source": "kashrock",
"sport": "cs2",
"matches": [
{
"kr_match_id": "kr_cs2_imperial-esports-vs-pain-gaming-23-10-2026",
"status": "live",
"team1": "paiN Gaming",
"team2": "Imperial Esports"
}
]
}Comparing sources
Schedule workers across titles, normalized to KR ids.
| Source | Schema | Best use |
|---|---|---|
| Wiki calendars | No odds join | Fans |
| Book calendars | Book-local ids | Narrow |
| KashRock matches | KR ids end to end | Products |
How to use it
Finished matches unlock boxscore and /results.
Operational practices
- : Prefer kr_match_id in all downstream calls
- : Filter status=
- : Sandbox covers CS2 discovery
Quick reference
GET /v7/cs2/matches?status=live returns live fixtures with kr_match_id. Get your free key.
If you need a normalized feed instead of another UI wrapper, the esports api exposes live boards, schedules, and history on one schema: with the IDs and outcome patterns that keep backtests and grading honest. Start free on Sandbox, or see published pricing.