List upcoming cricket fixtures with match IDs, start times, teams, venues, formats and series context, grouped by match type.
View all Cricket Live Scores, Scorecards & Stats API endpoints →Return the upcoming-matches feed as one JSON object. The operation has no input parameters on this page, so a plain GET to /matches/v1/upcoming is the whole request. The source spec also mentions optional country-code and UTC-offset request headers, but they are not exposed here, so no date window or time-zone behaviour should be assumed. No probe call was recorded for this operation, so the fields below come from a source example and are documented illustrations, not a verified contract. The example 200 body contains typeMatches, an array of groups with a matchType label and a seriesMatches array; filters.matchType, listing International, League, Domestic and Women; appIndex, an object with seoTitle and webURL text; and responseLastUpdated, a string. Each seriesMatches entry holds a seriesAdWrapper with seriesId, seriesName and a matches array, and each match has a matchInfo object. In the example matchInfo carries matchId, seriesId, seriesName, matchDesc (for example 4th Match), matchFormat (T20 and ODI appear), state and stateTitle both set to Preview, a status sentence and a hideScoreStatus string that read as a start time in GMT, startDate and endDate as epoch-millisecond strings, seriesStartDt and seriesEndDt, isTimeAnnounced, team1 and team2 (teamId, teamName, teamSName, imageId) and venueInfo (id, ground, city, timezone, latitude, longitude). Because the fixtures have not started, the example matches carry no matchScore object. How many days ahead the list reaches is not documented, so do not assume a fixed schedule window or complete coverage of every competition. Confirm the live shape and optional fields with your own request before depending on them.
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/matches-upcoming No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/matches-upcoming?key=<API_KEY>'
Query Result
Use Cases
- Build a next-matches panel and route a selected match into match information or research views using its matchId.
- Prepare a local watchlist of upcoming fixtures while verifying how country and time-zone handling behaves, instead of assuming a timezone or date-window contract.
- Show a countdown by converting the startDate epoch-millisecond string, and use isTimeAnnounced to flag times that are not yet confirmed.
- Plan notification schedules per tournament by grouping upcoming fixtures on seriesId and matchFormat.
- Convert kickoff to the venue's local time with venueInfo.timezone for fan-travel or viewing-party planner apps.
Frequently asked questions
Is the upcoming matches response verified by a probe?
No. No probe call was recorded for this operation, so the field list comes from a source example. Confirm the live shape and optional fields in your own response before relying on it.
Does this endpoint accept any inputs?
No. This page exposes no input parameters, so you send a plain GET to /matches/v1/upcoming. The source spec mentions optional country-code and UTC-offset headers, but they are not configurable here, so no date range or time zone can be selected.
Why is there no score for upcoming matches?
The example fixtures are in the Preview state and have no matchScore object. Scores appear on matches that have started, so use the live or recent matches endpoints for those.
Which start time field should I use?
Use startDate, an epoch-millisecond string, for sorting and countdown logic. The status and hideScoreStatus sentences are display text and read as GMT times in the example, so avoid parsing them.
How far ahead does the schedule reach?
The window is not documented. Treat the list as the next set of fixtures the feed provides, not a complete season calendar or a full list of every competition.
How do I get details for a fixture I selected?
Read matchInfo.matchId and, if you need tournament context, seriesId and teamId values. They are numeric identifiers that you can use in other match, series and team requests.
What if isTimeAnnounced is false?
The example shows true for every fixture. If you see false, treat startDate as provisional and avoid presenting it as a confirmed kickoff time, since the documentation does not describe this case.