Get venue and pitch research for one cricket match: ground details, pitch notes, par score, innings averages and pace-versus-spin cards.
View all Cricket Live Scores, Scorecards & Stats API endpoints →Retrieve venue and pitch context for one cricket match from the fantasy research feed. 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. The endpoint description states that most matches without fantasy coverage return HTTP 204, so an empty result is a normal outcome rather than an error. No response was observed for this operation in the supplied probe evidence, so the fields below come from a source example for a covered match and are documented illustrations, not a verified contract. The example 200 body contains groundName, city, country and an id value; groundDetails and pitchDetails arrays of heading and content text pairs (for example boundary dimensions and a written pitch assessment); runsExpected, a heading and content pair such as a par score; averageScores, a card with a heading, a label naming how many matches were counted and a values list of first-innings and second-innings averages; cards, statistic cards such as pace versus spin with cardHeading, cardLabel, cardType and subCard groups of label and value stats (Matches, Wickets, Best figures, Economy, Strike-rate, Dot%); recentMatches, a card with headers and rows where each row has a followUpLinkText slug and a values list that starts with a match ID, then a team label and the two innings scores; and a disclaimer array of informational notices. In the example every number is returned as a string. The data is pre-match research context, not a guaranteed pitch behaviour, a fantasy points total or betting odds, 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-venue-info API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-venue-info?key=<API_KEY>&matchId=151543'
Query Result
Use Cases
- Add available venue and pitch context to a match's fantasy-research page.
- Show an explicit unavailable-coverage message when this endpoint returns 204, and use general venue information only as a separately labeled resource, not an equivalent pitch report.
- Build a toss-decision explainer that sets the par score beside first-innings and second-innings averages from the same response.
- Link the match IDs in recentMatches rows to your own scorecard pages so readers can open earlier games played at the ground.
- Compare pace and spin economy, strike-rate and dot-ball percentages in an analyst notebook before writing bowling-attack notes for a preview.
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 groundName, city, country, an id, groundDetails and pitchDetails text pairs, runsExpected, averageScores, a cards array of pace-versus-spin statistics, recentMatches rows and a disclaimer list. These come from an unverified source example, so confirm the live shape with your own request.
Why do I get 204 with no body?
The endpoint description says most matches without fantasy coverage return 204, and the source example for that status is an empty object. Treat it as a no-data state, show a neutral message and do not retry in a tight loop.
Were these fields observed in a probe?
No. No response was observed for this operation in the supplied probe evidence, so every field is a documented illustration from a source example for a covered match rather than a verified contract.
How do I read the recentMatches rows?
In the example the headers list has three entries (Match, 1st Innings, 2nd Innings) while each values list has four, starting with a match ID, then a team label and the two innings scores. Map columns by position defensively and keep followUpLinkText only as a slug.
Are the numbers real numbers or strings?
In the example the averages, stat values and scores are all strings, and scores use a runs-wickets text form. Parse them in your own code and keep the original text for display.
Is this a guaranteed pitch report or a prediction?
No. The pitch notes and par score are editorial research context for a match, not a promise of how the surface will play, and the response holds no fantasy points or betting odds. The example also carries its own informational disclaimer text.