Get both teams' squads for a cricket match by match ID
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the squads of both teams for one cricket match, selected by the single required numeric `matchId` path parameter (default 41881). Take the matchId from the match list, schedule, series matches, team schedule and result, and venue match endpoints. There are no query parameters and no teamId, so the response always covers the whole fixture. No probe call was recorded for this operation, so the fields below come only from a truncated, unverified source example: an `appindex` object with `seotitle` and `weburl` strings, and a `team1` object whose `players` list contains category groups (the example shows "playing XI"), each with a nested `player` list. Each player row carries `id` (a string), `name`, `role` (values such as Batter, Bowler, WK-Batter 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`. The example is cut off before any second team appears, so the key that holds the other side is not confirmed here. Match squads are not series-wide squads, and a listed player is not a confirmed playing XI member unless the category says so. Coverage depends on the competition and match state.
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-teams API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-teams?key=<API_KEY>&matchId=41881'
Query Result
Use Cases
- Show both squads side by side on a match preview page from a single matchId, with each side's players grouped by category.
- Seed a pre-match article template with both rosters and the captain and wicketkeeper flags for each side.
- Build a squad balance table that counts roles such as batters, bowlers, allrounders and wicketkeepers per team for a tournament companion app.
- Replace two single-team requests with one call when a screen always needs both lineups, and cache the combined payload by matchId.
- Keep match squads separate from series-wide squads in an editorial tool, so a writer can see exactly who was named for this fixture.
Frequently asked questions
What does the match squads operation return?
It is described as the squads of both teams in a match. The only evidence is a truncated source example with an appindex object and a team1 object whose players list groups player rows by category. No probe call was recorded, so verify the full shape against a live response.
Which parameter is required and where does matchId come from?
Only the numeric matchId path parameter is required (default 41881). Use the matchId returned by the match list, schedule, series matches, team schedule and result, and venue match endpoints. No teamId or query parameters are accepted.
How is this different from the single-team squad operation?
This operation takes only a matchId and covers both sides of the fixture. The single-team operation takes a matchId and a teamId and returns one side's player array. Choose this one when a screen shows both lineups together.
Are these the confirmed playing XI?
Not by default. The example groups players under a category label such as "playing XI", but a squad can be published before the final eleven is known. Read the category value and avoid presenting every listed player as a confirmed starter.
Where is the second team in the response?
The supplied example is truncated after the first team, so the key for the other side is not confirmed here. Fetch a live response for your match and inspect the top-level keys before iterating over both teams.
Can I use faceimageid as a unique player key?
No. In the example several players share the same faceimageid value and some image references are zero. Use the player id, which is a string in the example, as the identifier, and treat image references as optional display hints.
What if a match has no squad data?
Coverage depends on the competition and match state, so a fixture without published squads can return a sparse or empty body. Handle that case in your UI instead of treating it as an error.