Get one team's squad in a cricket match by match and team ID
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the squad of a single team for one cricket match, selected by two required numeric path parameters: `matchId` (default 35878) and `teamId` (default 9). Take the matchId from the match list, schedule, series matches, team schedule and result, and venue match endpoints, and the teamId from the match info operation of the match-details group. There are no query parameters, so no role or category filter can be sent. No probe call was recorded for this operation, so the fields below come only from a truncated, unverified source example: a top-level `player` array of groups, each with a `category` label (the example shows "playing XI" and "bench") and a nested `player` list. Each player row in the example carries `id` (a string), `name`, `role` (values such as Batsman, Bowler, WK-Batsman and Batting Allrounder), `teamname`, the booleans `captain`, `keeper`, `isoverseas` and `isheader`, the image references `faceimageid`, `countryimageid` and `imageId`, and the text fields `battingStyle`, `bowlingStyle`, `battingsummary`, `bowlingsummary`, `inmatchchange` and `playingxichange`. Several of those text fields were empty strings in the example, so do not rely on them being populated. The `category` label is the only selection hint, so do not treat every listed player as a confirmed playing XI member. Coverage depends on the competition and match state, and a fixture without published squads may return a sparse or empty body.
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/match-details-get-team API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-team?key=<API_KEY>&matchId=35878&teamId=9'
Query Result
Use Cases
- Fill a team tab on a match page with one side's announced squad, using the matchId and teamId pair from the match info response.
- Draw captain and wicketkeeper badges on a lineup card from the captain and keeper booleans while leaving other rows unmarked.
- Split a lineup graphic into a starting group and a reserves group using the category label, without assuming the group names are fixed.
- Store the squad response before and after toss time and compare the two snapshots to flag late changes, if the inmatchchange or playingxichange fields turn out to be populated.
- Link each player id to the player profile operations of the same catalog so a lineup entry can open a player detail page.
Frequently asked questions
What does the match team operation return?
It is described as the squad of one team in one match. The only evidence is a truncated source example with a player array of category groups, each holding player rows with id, name, role, teamname and several flags. No probe call was recorded, so verify the shape against a live response.
Which parameters are required and where do the IDs come from?
Both matchId (default 35878) and teamId (default 9) are required path parameters. Use the matchId from the match list, schedule, series matches, team schedule and result, and venue match endpoints, and the teamId from the match info operation of the match-details group.
Does every listed player play in the match?
Not necessarily. The example separates players into category groups such as "playing XI" and "bench", and a squad can also be published before the final eleven is known. Read the category label instead of assuming that every row is a confirmed starter.
How is this different from the operation that returns both teams?
This operation takes a teamId and returns only that side's squad as a player array. The both-teams operation takes only a matchId and covers the whole fixture, so use this one when you already know which team the user selected.
Are the id values numbers or strings?
In the source example each player id is a string such as "8345", while the matchId and teamId path parameters are numeric. Keep the player id as a string when you store or compare it, and check this against a live response.
Are fields like battingStyle and playingxichange always filled in?
No. In the example battingStyle, bowlingStyle, battingsummary, bowlingsummary, inmatchchange and playingxichange are empty strings, and several image references are zero. Treat them as optional and fall back gracefully in your UI.