Get the player list for a cricket team by teamId
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the player list for one cricket team. The single required path input is teamId, a numeric team identifier taken from the teamId field of the teams list endpoint; the default example value is 2. The source response example shows a top-level player array whose rows are either role headings (a name such as BATSMEN, ALL ROUNDER, WICKET KEEPER or BOWLER with only an imageId) or player rows with id (string), name, imageId, battingStyle and, for most non-keeper players, bowlingStyle. No live probe was recorded for this operation, so these fields come from an unverified source example and the example list may be truncated; treat optional style fields as possibly absent. This is a team-level roster, not a match squad or a series-edition squad.
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/teams-get-players API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-players?key=<API_KEY>&teamId=2'
Query Result
Use Cases
- Create a team-level player directory whose entries link to individual player biographies and statistics.
- Render a squad page grouped by role by treating rows without an id as section headings and the rows after them as that role's players.
- Keep the general team player list distinct from match squads and series-edition rosters in your data model instead of treating it as a playing XI.
- Seed a player-name autocomplete scoped to one selected team using the returned names and ids.
- Build batting-hand and bowling-style filters for a scouting or fantasy research view from the style strings on each player row.
Frequently asked questions
What does the teams-get-players endpoint return?
It returns the player list for the team identified by teamId. The source example shows a player array containing role heading rows and player rows with id, name, imageId, battingStyle and, for many players, bowlingStyle.
Where do I get a valid teamId?
Use the teamId field returned by the teams list endpoint. The prefilled value 2 is only a default example; in the source examples for sibling team endpoints it corresponds to India, but that mapping is unverified here.
How do I tell role headings from real players?
In the source example, heading rows such as BATSMEN or BOWLER have only a name and an imageId, while player rows also have an id. Treat a missing id as a heading, and confirm this against a live response before relying on it.
Is this the same as a match squad or a tournament squad?
No. This is the general team-level player list. Match squads and series-edition rosters are separate concepts, so do not assume the returned list is the playing XI for a given fixture.
Are battingStyle and bowlingStyle always present?
Not guaranteed. In the source example, wicket keeper rows include battingStyle without bowlingStyle, so handle both fields as optional.
Was this response verified with a live call?
No probe call was recorded for this operation. The documented fields come from a source response example and may be truncated or differ from live data, so validate against your own request before shipping.