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
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/teams-get-results API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-results?key=<API_KEY>&teamId=2'
Query Result
Use Cases
- Populate a selected team's results tab and open each result's match center for deeper context using the returned matchId.
- Prepare a team-results digest without assuming an unlimited historical date range or unlisted pagination controls.
- Show a recent-form strip for a team by reading the status text and innings scores of its latest completed matches.
- Group a team's recent results by tour or tournament in a mobile app using the series-name key and seriesId.
- Cross-check a venue-level history view by reading ground, city and timezone from each result's venueInfo.
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.