List live, recent or upcoming cricket matches

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

Returns cricket matches for one state view chosen with the required `type` path parameter: `live`, `recent` or `upcoming` (default `recent`). No probe call was recorded for this operation, so the fields below come from a source response example and are unverified. That example has a top-level `typeMatches` array grouped by competition class (`matchType`, for example International, League, Domestic and Women), each holding `seriesMatches` with a `matches` list. Each entry has `matchInfo` (matchId, seriesId, seriesName, matchDesc, matchFormat, startDate, endDate, state, stateTitle, status, team1, team2 with teamId, teamName and teamSName, and venueInfo with ground, city and timezone) and, for matches that have scores, `matchScore` with per-innings runs, wickets and overs. Dates are epoch-millisecond strings. Use the returned matchId with the match-detail endpoints. Coverage depends on current fixtures, so a view can come back with no matches.

API Features

Three match-state views One `type` path value switches the same endpoint between live, recent and upcoming matches, so a single client wrapper can serve every tab.
Competition-grouped payload Matches are nested under typeMatches and seriesMatches, which lets an interface render International, League, Domestic and Women sections without regrouping the data.
Teams, venue and result text Each matchInfo block carries both teams with short names, venue ground and city, the match state and a human-readable status line such as a win margin.
Innings scores in the list Where scores exist, matchScore returns runs, wickets and overs per innings so a scoreboard card does not need a second request.
IDs for follow-up lookups matchId, seriesId and team ids in each entry feed the match-detail, series and team endpoints, so the list works as an entry point for identifier-linked workflows.

Live API Demo

GET /api/project/cricbuzz-cricket/matches-list

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

Use Cases

Frequently asked questions

Which values does the type parameter accept?

The documented values are `live`, `recent` and `upcoming`, and the default is `recent`. Other values are not documented, so validate the value on your side before sending the request.

Can a view return no matches?

Yes. Results depend on the fixtures that exist at request time, so the live view in particular can be empty when nothing is in progress. Handle an empty or missing typeMatches array with a clear empty state.

How do I get full details for a match from this list?

Take matchId from matchInfo and pass it to the match-detail endpoints, for example match-details/get-info for match facts. This list is a summary view, not a full scorecard.

How are dates and times represented?

In the source example, startDate and endDate are epoch-millisecond strings and venueInfo includes a timezone offset such as +09:00. This was not confirmed by a probe call, so check a real response before relying on exact formats.

Can I filter by country or time zone?

No. This endpoint exposes only the `type` path parameter. Convert timestamps to the viewer's time zone in your own code and filter by series or team after receiving the list.

Related operations

Guides

View Subscription Plans →