Tournament Endpoints

Tournament Endpoints (12)

All endpoints use base URL https://api.sportsapipro.com/v2/cricket.

Tournament Info

GET /api/tournament/:id/info
GET /api/tournament/:id/seasons
GET /api/tournament/:id/image
GET /api/tournament/:id/featured-events
GET /api/tournament/:id/media

Season-Specific Endpoints

All require tournamentId + seasonId. Discover season IDs via /api/tournament/:id/seasons.

GET /api/tournament/:id/season/:sid/standings?type=total
GET /api/tournament/:id/season/:sid/rounds
GET /api/tournament/:id/season/:sid/knockout
GET /api/tournament/:id/season/:sid/events/round/:round
GET /api/tournament/:id/season/:sid/events/last/:page
GET /api/tournament/:id/season/:sid/events/next/:page
GET /api/tournament/:id/season/:sid/info
GET /api/tournament/:id/season/:sid/venues

Cricket tournaments do not use a round/matchday system upstream — most seasons (IPL, internationals, county cricket) return 404 on /rounds and /events/round/:round. Use /events/last/:page for the paginated match list, /standings for the points table, and /knockout for the playoff bracket instead.

Tracking bilateral and one-off series

Bilateral tours (“India in Afghanistan, 3 T20I Series”), tri-series and one-off internationals are not first-class tournaments. They appear on each event as tournament, nested inside a permanent format parent exposed as uniqueTournament.

"tournament":       { "id": 118948, "name": "India in Afghanistan, 3 T20I Series" },
"uniqueTournament": { "id": 11191,  "name": "T20 International" },
"season":           { "id": 93728,  "year": "2026" }

The series id has no endpoints of its own. GET /tournament/118948/info, /seasons, /featured-events, /media and /season/:sid/... all return 404 — that is expected, not an outage. Track the series on uniqueTournament.id + season.id and group events by tournament.id.

Format parents

ID	Format parent
11191	T20 International
11190	One Day International
11189	Test Series
11222	Twenty20 International Women
11221	One Day International Women
11188	Tri-Series
11393	Quad-Series
11232	Friendly International

These come from GET /categories/1343/tournaments (category 1343 = World), which lists recurring unique tournaments only — response shape data.groups[].uniqueTournaments[]. Series never appear there.

A format parent can have several current seasons

GET /tournament/:id/seasons returns more than one season for the current year, and each holds a different set of series. Query only one and you will miss fixtures. Verified 15 Sep 2026:

Parent	Current-year seasons	Forward fixtures
11191 T20I	77257, 93728	19 events to 27 Dec, 18 events to 1 Nov
11190 ODI	77922	26 events to 19 Dec
11189 Test	79087, 95102, 103028	first two `404` on `/events/next` (empty seasons), 103028 has 3 events

Empty seasons return 404 on /events/next/:page — tolerate it and continue.

Discovery recipe

daily job
 1. for each format parent (11191, 11190, 11189, 11222, 11221, 11188, 11393)
      GET /tournament/{parent}/seasons          -> keep every current-year season id
 2. for each (parent, season)
      GET /tournament/{parent}/season/{sid}/events/next/{page}   page 0..n until empty or 404
      GET /tournament/{parent}/season/{sid}/events/last/{page}   for completed results
 3. group events by event.tournament.id -> that is the series
      name    = event.tournament.name  (also carries the format: "3 T20I Series")
      start   = min(startTimestamp), end = max(startTimestamp)
      matches = the grouped event ids
 4. store (uniqueTournamentId, seasonId, seriesTournamentId) as your tracking key
 5. same-day accuracy: GET /live   (never /schedule — its status can be stale)

About 20–40 requests per day covers all international cricket. Fixtures are populated roughly 6–14 weeks ahead.

Worked example — India in Afghanistan, 3 T20I Series

curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.sportsapipro.com/v2/cricket/tournament/11191/season/93728/events/next/0"

Returns 18 upcoming matches across 7 different series. Filtering tournament.id == 118948 across events/next/* and events/last/* for both 2026 seasons yields the complete series:

Match ID	Start (UTC)	Status
16801767	2026-09-13 14:00	finished
16801768	2026-09-15 14:00	notstarted
16801769	2026-09-17 14:00	notstarted

GET /tournament/11191/featured-events also surfaces the current headline fixture of the parent format, including bilateral ones.

There is no series-level metadata endpoint. Series name and format come from event.tournament.name / slug, dates from the min/max startTimestamp of its events, and grounds from GET /match/:matchId/venue. In earlier years, series were modelled as season names instead (e.g. season 58886 = “Oman in Scotland, One-off T20I Series, 2024”), so historical data can look different from current seasons.

API Reference

Guides

Popular Sports

Team Sports

Racquet & Precision Sports

Specialty Sports

V3 API

V4 Odds API

V6 AiScore API

V1 Legacy

Football V1

Basketball V1

Tennis V1

Hockey V1