List auction tournaments, years and default selections
View all Cricket Live Scores, Scorecards & Stats API endpoints →Discover auction tournament identifiers, available years and default selections before choosing an edition for team or player queries. The optional tournament and year query parameters use identifiers from seasons.tournament.tournaments and values from seasons.year; their documented request defaults are ipl and 2026. A saved successful HTTP 200 check confirmed a JSON object containing seasons.tournament as an object, seasons.year as an array, defaults as an object and appIndex as an object. The source example further documents seasons.tournament.tournaments entries with identifier and title, defaults.tournament with identifier and title, defaults.year, and appIndex.seoTitle and appIndex.webURL as navigation metadata. These nested example fields and values were not individually verified by that check. Use returned selections rather than assuming that a documented example year is the current default or that every listed year is available for both IPL and WPL. This endpoint discovers editions; it does not return purchased-player rosters or team budgets.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/cricbuzz-cricket/auction-list-seasons API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-list-seasons?key=<API_KEY>&tournament=ipl&year=2026'
Query Result
Use Cases
- Build an IPL/WPL edition picker using tournament identifiers and titles from the documented tournament list.
- Populate an auction archive year selector from seasons.year rather than maintaining a hard-coded year range.
- Suggest an initial auction selection from returned defaults while allowing the user to confirm a different edition.
- Offer a manual edition-selection step before a user submits auction team-budget or purchased-player requests.
Frequently asked questions
What does the auction seasons response contain?
The successful saved check confirmed seasons.tournament, seasons.year, defaults and appIndex with their documented object or array types. The source example additionally shows tournament identifier/title entries, a default tournament and year, and appIndex navigation metadata; those individual example values are not guaranteed current.
Where should tournament and year parameter values come from?
Use identifiers from seasons.tournament.tournaments for tournament and values from seasons.year for year. Both query parameters are optional, with documented request defaults of ipl and 2026.
Are all listed years necessarily available for both IPL and WPL?
The available evidence does not establish a tournament-by-year availability matrix. Do not assume that every combination of a listed tournament and year is supported.
Does the documented 2026 value always mean the current auction edition?
No. It is the documented request default and an example value, not a freshness guarantee. Read returned defaults when preparing an edition selection.
Can I get auction team purchases from this endpoint?
No. This response is for tournament, year and default discovery. Use the auction team list for team identifiers, then the single-team auction endpoint for documented purchased-player details.