Get one auction team's purchased players by role
View all Cricket Live Scores, Scorecards & Stats API endpoints →Retrieve the documented purchased-player view for one auction team, grouped by role and accompanied by team strategy information where supplied. The required numeric teamId path parameter comes from the auction team list; 58 is the documented CSK example. Optional currency, tournament and year query parameters select price display and auction context, with documented defaults INR, ipl and 2026. No saved technical probe covers this operation. Its unverified, truncated source example shows an allroundersList array with playerId, playerName, playerImageId, country, countryId, role, cappedStatus, isPlayerOverseas, playsFor, playsForTeam, teamImageId and season. Purchase-related fields shown include auctionStatus, auctionPrice, basePrice, totalEarnings and updatedTime. Prices are display strings, and totalEarnings may contain a placeholder such as --; do not assume all monetary fields are numeric. The source description documents role grouping and team strategy, but the truncated example does not establish the complete set of role groups or the strategy field structure. Treat this as an auction-purchase record for the selected edition, not as a complete retained squad, a confirmed match-day lineup or a prediction of team performance. Currency examples are INR, USD and GBP; unknown currency values are documented to return prices without a currency symbol.
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-get-team API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-get-team?key=<API_KEY>&teamId=58¤cy=INR&tournament=ipl&year=2026'
Query Result
Use Cases
- Create a selected team's post-auction acquisition page with player names arranged into the returned role groups.
- Prepare an editor's team-building review that distinguishes newly purchased players from retained players and match-day selections.
- Display bought-player cards with auction price, base price and sale status in a user-selected documented currency.
- Add country, capped-status and overseas labels to purchased-player profiles, with playerId available for a separate user-requested detail lookup.
Frequently asked questions
How do I find the teamId for this request?
Read teamId from the auction team-list endpoint for the edition being explored. teamId is a required numeric path parameter; 58 is the documented CSK example, not a guarantee of data for every tournament or year.
Does this return the full team squad or a match-day playing XI?
The documented purpose is players bought at auction, grouped by role, with team strategy information. Do not treat it as a complete retained squad or an announced match-day lineup.
Which player fields are documented in the available example?
The unverified source example shows allroundersList entries with player identity, role, country, capped and overseas status, team references, season, auctionStatus, auctionPrice, basePrice, totalEarnings and updatedTime. The example is truncated, so it does not establish the full response.
Which currencies can I request for auction prices?
INR is the documented default; USD and GBP are also documented examples. The parameter is a free-form string rather than a confirmed exhaustive currency list. Unknown values are documented to return prices without a currency symbol.
Are auctionPrice and basePrice numeric amounts?
The available example presents them as formatted strings that may include a currency symbol and scale notation. Preserve their display meaning, and handle placeholder values such as -- rather than assuming every financial field is numeric.
Have the strategy fields and all role groups been verified?
No saved technical probe covers this operation. The source description mentions strategy and grouping by role, while the truncated example shows allroundersList only; it does not establish the strategy schema or a complete list of role groups.