Get completed match results for a cricket team by teamId

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

Returns match results for one cricket team. The single required path input is teamId, a numeric team identifier taken from the teamId field of the teams list endpoint; the default example value is 2. The source response example shows a top-level appIndex object with navigation metadata and a teamMatchesData array. Result entries use a matchDetailsMap whose key is the series name, with a match array and a seriesId. Each match has matchInfo (matchId, matchDesc, matchFormat, state, status, hideScoreStatus, startDate and endDate as millisecond epoch strings, seriesId, seriesName, team1 and team2 with teamId, teamName, teamSName and imageId, and venueInfo with id, ground, city and timezone) and, when scores exist, matchScore with per-team innings runs, wickets and overs. Some array entries are advertisement slots with an adDetail object instead of match data, and an abandoned match in the example has no matchScore. No live probe was recorded, so these fields come from an unverified, possibly truncated source example. The path takes no documented paging or date-range inputs.

API Features

Results grouped by series In the source example each matchDetailsMap entry is keyed by series name and carries a seriesId, so a results tab can show one section per tour or tournament.
Result status text Each matchInfo includes state, status and hideScoreStatus, for example a won-by margin, an abandoned-due-to-rain note or a match completed label.
Innings scores per team When scoring data exists, matchScore returns team1Score and team2Score with innings runs, wickets and overs for building compact result cards.
Venue and format details venueInfo supplies the ground, city, venue id and timezone, and matchInfo adds matchFormat and matchDesc such as semi-final or numbered ODI labels.
Match IDs for deeper pages Every result carries a matchId and both team ids, giving you the keys to open a match center or scorecard view from a team's results list.

Live API Demo

GET /api/project/cricbuzz-cricket/teams-get-results

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/teams-get-results?key=<API_KEY>&teamId=2'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does the teams-get-results endpoint return?

It returns match results for the team identified by teamId. The source example shows teamMatchesData entries grouped by series, each with matchInfo and, when available, matchScore innings figures.

Where do I get a valid teamId?

Use the teamId field from the teams list endpoint. The prefilled value 2 is only a default example, and the source example for this operation shows it returning results where the team is named India.

Can I filter results by date, series or page?

The documented input is only teamId. No date range, series filter or pagination parameter is listed, so do not assume the response covers unlimited history or that you can page through it.

Why do some entries have adDetail instead of match data?

The source example interleaves advertisement slot objects with the series groups. Skip entries that lack matchDetailsMap when you build a results list.

Does every result include a score?

Not necessarily. In the source example a match abandoned due to rain has a status line but no matchScore, so treat matchScore and individual innings as optional.

Were these fields confirmed with a live probe?

No probe call was recorded for this operation. The field list comes from a source response example that may be truncated, so verify the real response shape in your own request before relying on it.

Related operations

Guides

View Subscription Plans →