List recently played cricket matches with result text, series context, teams, venues and innings scores, grouped by match type.
View all Cricket Live Scores, Scorecards & Stats API endpoints →Return the recent-matches feed as one JSON object. The operation has no input parameters on this page, so a plain GET to /matches/v1/recent is the whole request. The source spec also mentions optional country-code and UTC-offset request headers, but they are not exposed here. 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 the labels 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 plus a matchScore object. In the example matchInfo carries matchId, seriesId, seriesName, matchDesc (for example a medal match or a semi-final), matchFormat (T20 in the example), state set to Complete, stateTitle such as a short winner label, a status sentence stating the result margin, hideScoreStatus, startDate and endDate as epoch-millisecond strings, seriesStartDt and seriesEndDt, isTimeAnnounced, currBatTeamId, an optional isFantasyEnabled flag, team1 and team2 (teamId, teamName, teamSName, imageId) and venueInfo (id, ground, city, timezone, latitude, longitude). matchScore holds team1Score and team2Score, each with an inngs1 object containing inningsId, runs, wickets and overs. The endpoint lists matches that have recently finished; how far back it reaches is not documented, so do not treat it as a complete historical archive. 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-recent 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-recent?key=<API_KEY>'
Query Result
Use Cases
- Populate a recent-results recap view that opens the full scorecard when a user selects a match.
- Find a recently played match after it has left the live listing, without treating this endpoint as a complete historical archive.
- Group recent matches by seriesId to build a tournament results table and sort entries by their endDate timestamps.
- Generate a post-match digest that pairs each status line with team short names and innings totals for newsletters or chat bots.
- Link finished fixtures to ground pages using the venueInfo id, ground and city fields returned with each result.
Frequently asked questions
Is the recent matches response verified by a probe?
No. No probe call was recorded for this operation, so the field list comes from a source example. The structure matches the live-matches feed, but you should confirm optional fields in your own response.
Does this endpoint accept any inputs?
No. This page exposes no input parameters, so you send a plain GET to /matches/v1/recent. The source spec mentions optional country-code and UTC-offset headers, but they are not configurable here.
How do I read who won a recent match?
Use the status sentence and the stateTitle label inside matchInfo. In the example the winner and margin are free text, and no separate winner-id field is shown, so parse the text carefully or open the scorecard for structured detail.
How far back do recent matches go?
The window is not documented. Use the endpoint to catch matches that finished lately, and do not assume it covers complete history or every competition.
How is this different from the live matches endpoint?
The example lists matches whose state is Complete, with result sentences and final innings scores. The live endpoint lists matches in progress, at the toss, at a break or at stumps, so use that one for in-play views.
What do the date fields look like?
startDate, endDate, seriesStartDt and seriesEndDt are epoch-millisecond values returned as strings in the example. Parse them as numbers, and use venueInfo.timezone if you need the ground's local offset.
Can a section or field be missing?
Yes. In the example optional fields such as isFantasyEnabled appear only on some matches, and a group or series can be empty depending on coverage, so guard every lookup and handle an empty typeMatches array.