Get the fantasy guide home for a cricket match with forecast video and section links.
View all Cricket Live Scores, Scorecards & Stats API endpoints →Retrieve the fantasy guide landing data for one cricket match, described as the guide home with a win forecast and key sections. 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 an unverified source example and are documented illustrations, not a verified contract. The example contains the match header fields id, title, subtitle, matchDesc, seriesName, seriesShortName, team1ShortName and team2ShortName, a tabs array whose entries have an id, a path and a title and point to the Expert's Corner, Matchups, Venue and All Players sections, and a video object for a Match Forecast clip. The illustrated video object includes id, title, description, durationStr, videoType, videoFormat, language, source, publishedTime, imageId, category, tags and tagItems that link the clip to the series, match, teams and players. The example shows no numeric win-probability fields, so treat any forecast as source-supplied material rather than calibrated odds or an assured result. Video fields can include a signed playback link that is not meant to be stored or shared, and coverage depends on 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-match-forecast API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-match-forecast?key=<API_KEY>&matchId=151543'
Query Result
Use Cases
- Load the fantasy guide landing for a selected match and build a tab bar from the returned path and title values.
- Display the Match Forecast clip card with its title, duration and description on a pre-match preview page, labeled as a source-supplied forecast.
- Link reader-facing tabs to the expert corner, matchups, venue info and all-players endpoints using the same matchId.
- Use the tagged player and team itemId values to cross-link a forecast video to player profile and team pages in an editorial workflow.
- Pre-fill the headline and series label of a match preview newsletter from title, matchDesc and seriesName before adding custom analysis.
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.
Does this endpoint return win probabilities?
It is described as the fantasy guide home with a win forecast and key sections, but the unverified source example shows no numeric probability fields. It shows header data, section tabs and a Match Forecast video. Do not present it as calibrated odds or a guaranteed result.
What do the tabs entries contain?
Each entry in the example has an id, a path and a title. The paths shown are expertCorner, matchUps, venueInfo and allPlayers, which correspond to the other fantasy research endpoints for the same matchId.
What does the video object describe?
In the example it holds metadata for a Match Forecast clip, including title, description, durationStr, videoType, videoFormat, language, source, published time, image IDs and tag lists. The clip link may carry a temporary signed token, so do not store or redistribute it.
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 source example rather than a verified contract.
What if the match has no forecast video yet?
The source notes that video analysis comes first with written forecasts added later, and coverage depends on the match. The documentation does not state how absent sections appear, so treat video and other sections as optional in your client.