List upcoming cricket matches with pre-match forecast text, or an empty result when none.

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

Retrieve the fantasy prediction hub, a list of upcoming cricket matches with pre-match forecast information. The endpoint takes no parameters. The catalog notes that it returned HTTP 204 (no content) at the time of testing, so a call can come back with an empty body and clients should treat that as a no-content state, not as an error or a permanent outage. No response body was observed in the supplied probe evidence. The fields below come from an unverified source example filed under the 204 status and are documented illustrations, not a verified contract. The example holds a matches array. Each entry has matchId, matchName, matchFormat, state, startdt, customStatus, seriesId, seriesName and seriesCategory, plus team1 and team2 objects with id, name, shortName, imageId and color. It also shows a cbPrediction object with a label and a text value, the flags isForecastEnabled and isProbabilityEnabled, a fillerText message, highlightedTeamId, and two link fields, forecastUrl and livePredictionUrl, which appear to be app deep links rather than web addresses. The prediction text is editorial forecast copy, not calibrated betting odds or a guaranteed result, and which matches appear depends on coverage.

API Features

No-input discovery call A single GET with no parameters lets a predictions screen load without first resolving a matchId, which suits a landing tab or a scheduled background check.
Cataloged 204 no-content result The catalog records HTTP 204 at test time, so the contract includes an empty outcome that your client can map to a clear empty state instead of treating it as a failure.
Forecast text per fixture Each example entry carries a cbPrediction label and text value, a fillerText message for the period before the toss and the flags isForecastEnabled and isProbabilityEnabled.
Fixture and series context matchId, matchName, matchFormat, state, startdt, customStatus, seriesId, seriesName and seriesCategory describe each listed match, so rows can be titled and grouped by series.
Team display fields team1 and team2 objects expose id, name, shortName, imageId and color, giving what a fixture row needs for team-coded styling and logo lookups.
Links into the forecast flow forecastUrl, livePredictionUrl and highlightedTeamId point toward a match's forecast view, while matchId can be reused with the other fantasy research endpoints.

Live API Demo

GET /api/project/cricbuzz-cricket/fantasy-get-prediction-hub

No parameters required. Click Query to call the API.

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-prediction-hub?key=<API_KEY>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Does this endpoint take any parameters?

No. The path is fixed and there are no path, query or header inputs to set, so a plain GET is enough.

Why might the response be empty?

The catalog notes that the endpoint returned HTTP 204 at the time of testing. A 204 carries no body, so handle it as a no-content state. The documentation does not say whether it is temporary, so do not assume it is a permanent outage.

What fields does the example show?

A matches array whose entries have match, series and team fields, a cbPrediction object with a label and a text value, enable flags, a fillerText message, highlightedTeamId and two forecast link fields.

Were these fields observed in a probe?

No. No response body was observed in the supplied probe evidence, and the example is filed under the 204 status in the source, so treat the fields as unverified illustrations and confirm the real shape when the hub returns content.

Are the predictions betting odds or guaranteed results?

No. The example prediction is short editorial text with a probability phrase, not calibrated odds. Present it as an informational forecast and do not describe it as a guaranteed outcome.

How do I get more detail for a listed match?

Reuse the matchId from an entry with the other fantasy research endpoints, such as the match player list, matchups, expert corner or match forecast. Each of them takes a matchId.

Can I open forecastUrl in a browser?

The link fields look like app deep links rather than web addresses, so do not assume they resolve in a browser. Build your own navigation from matchId instead.

Related operations

Guides

View Subscription Plans →