List a cricket match's players grouped by role with fantasy badges.
View all Cricket Live Scores, Scorecards & Stats API endpoints →Retrieve the player research list for one cricket match, grouped by role and annotated with fantasy badges such as In form. The only input is the required numeric path parameter matchId, taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied default is 151543. No response was observed for this operation in the supplied probe evidence, so the fields below come from a truncated, unverified source example and are documented illustrations, not a verified contract. The example shows a disclaimer array, a legends array and a playerStyles array, plus playersByRole. Each playersByRole entry has a role label (for example WICKET KEEPERS) and a players array. Each illustrated player has id, name, teamName, teamShortName, teamFlagId, faceImageId, isVisible, a playerStyle array of code/label pairs and a badges array; some players also carry a short description with form or matchup commentary. Each legends entry has a code, label and desc, and some entries add color and isSeparate fields. Badge labels illustrated include In form, Injured, Off Field Pick, Ideal for Conditions and C/VC. The list is a role-grouped research roster, not a confirmed starting XI and not a fantasy points total, and availability depends on coverage for the chosen match.
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/fantasy-list-players API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-list-players?key=<API_KEY>&matchId=151543'
Query Result
Use Cases
- Build a fantasy research player picker for one match with sections for wicket keepers, batters and other roles taken straight from playersByRole.
- Add filter chips for the In form and Ideal for Conditions badges so analysts can narrow a long player list to flagged names.
- Join each player id to a separate player-profile lookup and open a match-context profile when a user selects a row.
- Show Injured badges as a caution on a pre-match squad explorer while still telling readers to confirm the final team announcement elsewhere.
- Render team-coded roster cards by pairing teamShortName with the image IDs returned for each player and team flag.
Frequently asked questions
Where do I get the matchId for this endpoint?
Use the matchId field returned by the match list, match schedule, series match, team schedule, team result or venue match endpoints. It is a required numeric path value, and 151543 is the supplied default.
Is the returned list the confirmed playing XI?
No. The endpoint is documented as all players of a match grouped by role with fantasy badges. Treat it as a research roster and confirm the final lineup from an announced team sheet before presenting it as the starting XI.
What do the badges mean?
The unverified source example includes a legends array that defines the codes: In form, Injured, Off Field Pick, Ideal for Conditions and C/VC. Each player's badges array lists the codes that apply, and may be empty.
Which response fields are documented, and were they observed?
The source example shows disclaimer, legends, playerStyles and playersByRole, with id, name, team fields, image IDs, playerStyle, badges and an optional description per player. The example is truncated and no probe response was observed for this operation, so treat the fields as illustrative rather than verified.
Does it return fantasy points or player prices?
No such fields appear in the documented example. It carries roles, badges, style labels and commentary, so use other sources for points, credits or salary values.
What if a match has no fantasy data?
Coverage depends on the match, and the documentation does not describe the response for matches without fantasy content. Handle empty or missing playersByRole gracefully in your client.