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
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-list API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/matches-list?key=<API_KEY>&type=recent'
Query Result
Use Cases
- Drive a home-screen scoreboard whose live tab renders each match's status line and current innings score from the live view.
- Build a results page from the recent view that groups completed matches by series and shows the stateTitle and result text.
- Fill an upcoming-fixtures calendar with startDate, matchDesc and venue details, converting epoch-millisecond start times into the reader's local time zone.
- Reuse one list component across three tabs with a request wrapper that only changes the type value, keeping a separate empty-state message for each tab.
- Collect matchId and seriesId values from the list to seed scorecard and series lookups in a data pipeline.
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.