Get match-specific batter-versus-bowler matchup stat cards for a cricket match.

View all Cricket Live Scores, Scorecards & Stats API endpoints →

Retrieve match-specific batter-versus-bowler matchup cards for one cricket match. 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 returns a cards array. Each card has cardHeading (for example a venue, opposition or player-versus-player title), cardLabel (a format label such as ODIs), cardType (playerStatsCard), playerOneImageId, playerTwoImageId and a subCard array. Each subCard entry has a subCardHeading naming a player and a stats array of label and value pairs, with every value returned as a string. Illustrated stat labels include Matches, Innings, Runs, Highest, Average, 100s, 50s, 0s, Wickets, Best figures, Economy, Strike-rate and 4-fers on the venue and opposition cards, and Runs scored, Balls faced and Dismissals on the player-versus-player card. The example is cut off inside that last card, so any further fields are not documented. The cards are match-scoped research context, not a complete all-time head-to-head record, a prediction or a fantasy points total, and availability depends on coverage for the chosen match.

API Features

Match-scoped matchup cards A cards array with cardHeading, cardLabel and cardType lets a client render one panel per matchup theme for a single matchId without stitching several statistics calls together.
Venue and opposition records The example includes cards for players at the match venue and players against the opposition, each with stats such as Matches, Innings, Runs, Highest and Average for quick pre-match comparison.
Batting and bowling stat sets Every subCard carries a stats list of label and value pairs, covering batting figures like 100s and 50s and bowling figures like Wickets, Economy, Strike-rate, Best figures and 4-fers.
Player-versus-player card A dedicated card pairs two players and lists labels such as Innings, Runs scored, Balls faced and Dismissals, giving a compact batter-against-bowler view for one pairing.
Image IDs for both players playerOneImageId and playerTwoImageId are returned on each card, so an interface can request portraits and draw a two-player header above the stat columns.

Live API Demo

GET /api/project/cricbuzz-cricket/fantasy-get-matchups

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-matchups?key=<API_KEY>&matchId=151543'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Which matchId do I pass?

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.

What does the response contain?

The source example shows a cards array. Each card has a heading, a format label, a card type, two player image IDs and a subCard list of players, each with a stats array of label and value pairs. The example is truncated, so treat any field beyond those as undocumented.

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 a truncated source example rather than a verified contract. Validate the live shape with your own request before relying on it.

Is this a complete all-time head-to-head record?

No. The endpoint is described as batter-versus-bowler matchups for a match. The example cards are scoped to a venue, an opposition and a player pairing, so use them as match research context and do not present them as a full career comparison.

Are the stat values numbers?

In the example every value is a string, and some carry a suffix such as an asterisk on a Highest score. Parse values defensively and keep the original text for display.

Does it return fantasy points, odds or predictions?

No such fields appear in the example. The cards hold historical-style stat labels only, so do not describe the output as points projections, betting odds or a guaranteed result.

What if a match has no matchup data?

The documentation does not state how a match without coverage is represented. Build the client to handle an empty cards array or an empty response and show a neutral no-data message.

Related operations

Guides

View Subscription Plans →