Get a player's fantasy research profile, badges and key info within one cricket match.
View all Cricket Live Scores, Scorecards & Stats API endpoints →Retrieve the fantasy research profile of one player within one cricket match. Both inputs are required numbers. playerId goes in the path and is taken from the id field of a player returned by the fantasy match-players endpoint (/forecast/v1/allPlayers/{matchId}). matchId goes in the query and is taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied defaults are playerId 8733 and matchId 151543. No response was observed for this operation in the supplied probe evidence, so the fields below come from an unverified source example and are documented illustrations, not a verified contract. The example is a single object with id, fullName, country, role, batStyle, bowlStyle, stockDelivery, battingPosition, battingRole, faceImageId, a badges array of code and label pairs (for example In form and Ideal for Conditions), a keyInfo array of short scouting sentences and a disclaimer array of informational notes. In the example bowlStyle and stockDelivery are empty strings for a batter, so treat the bowling fields as optional. The profile is match-context fantasy research, not a full biography, a career statistics page, a projected fantasy points total or a confirmed selection, 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-get-player-info API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-player-info?key=<API_KEY>&playerId=8733&matchId=151543'
Query Result
Use Cases
- Open a player research card using both playerId and matchId when navigating from the match's player list.
- Keep a player's match-specific fantasy context separate from the global biography and career-statistics pages.
- Show a bottom-sheet summary in a fantasy team builder with role, batting position and keyInfo bullets for the selected player.
- Tag watchlist players with In form and Ideal for Conditions chips and refresh the profile for each upcoming matchId.
- Pre-fill an editorial player note from country, role and keyInfo, then combine it with a separate statistics lookup before publishing.
Frequently asked questions
Where do I get playerId and matchId?
Take playerId from the id field of a player in the fantasy match-players response, and matchId from the match list, schedule, series match, team schedule, team result or venue match endpoints. Both are required numbers, with supplied defaults 8733 and 151543.
Why does the profile need a matchId as well?
The endpoint returns the fantasy profile of a player in a match, so the query matchId scopes the result to one fixture. The same playerId can be requested with a different matchId to get that match's context.
What fields does the example show?
A single object with id, fullName, country, role, batStyle, bowlStyle, stockDelivery, battingPosition, battingRole, faceImageId, badges, keyInfo and disclaimer. Badges are code and label pairs, and keyInfo and disclaimer are arrays of strings.
Were these fields observed in a probe?
No response was observed for this operation in the supplied probe evidence, so the fields are documented illustrations from an unverified source example rather than a verified contract.
Are the bowling fields always filled?
Not in the example. bowlStyle and stockDelivery are empty strings for a batter, so check for blanks before showing a bowling line, and expect different content for bowlers or all-rounders.
How should I use the badge code and label?
Display the label, for example In form or Ideal for Conditions. The code values in the example are short hexadecimal strings, so use them only as identifiers and do not assume a fixed meaning without checking the legend returned by the match-players endpoint.
Is this a full career profile or a points forecast?
No. It is a match-context research profile with role, style and short notes. The example carries a disclaimer that forecasts are informational and can change with weather, injuries or team composition, and it has no points projection.