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

Match header for the guide Returns id, title, subtitle, matchDesc, seriesName, seriesShortName and both team short names, enough to render the heading of a match forecast page without a second lookup.
Section tabs with paths The tabs array lists guide sections with a path and title, such as expertCorner, matchUps, venueInfo and allPlayers, so you can link readers to the matching research modules.
Match Forecast video metadata A video object describes the forecast clip with title, description, durationStr, videoType, videoFormat, language and published time, ready for a video card or editorial teaser.
Tagged series, match, team and players tags and tagItems tie the clip to the series, match, teams and featured players by itemId and itemType, which helps cross-link to profile and team endpoints.
Single call for the guide landing One matchId request returns the landing context and navigation for the fantasy guide, so a research page can bootstrap its tab bar from the response.

Live API Demo

GET /api/project/cricbuzz-cricket/fantasy-get-match-forecast

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-match-forecast?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.

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.

Related operations

Guides

View Subscription Plans →