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
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-prediction-hub No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-prediction-hub?key=<API_KEY>'
Query Result
Use Cases
- Offer an upcoming-predictions discovery screen only when the hub supplies content.
- Implement a no-content state for the cataloged HTTP 204 result and avoid substituting fabricated predictions or interpreting it as a guaranteed permanent outage.
- Seed a fixtures carousel with match name, format and start date, then use each matchId to open the match-level fantasy research endpoints.
- Style team chips in a preview-article sidebar from the shortName and color fields of team1 and team2.
- Run a scheduled check that records whether the hub returned content or no content, to see how often forecasts are available for the competitions you follow.
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.