Get upcoming scheduled matches for a cricket team by teamId
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the scheduled matches 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 request path ends in /schedule. The source response example shows a top-level appIndex object with navigation metadata and a teamMatchesData array. Fixture entries use a matchDetailsMap whose key is a date label such as Tue, 06 Oct 2026, with a match array and a seriesId. Each match has matchInfo (matchId, matchDesc, matchFormat, state such as Preview or Upcoming, status and hideScoreStatus text such as Match starts at Oct 06, 13:30 GMT, isTimeAnnounced, startDate and endDate as millisecond epoch strings, seriesId, seriesName, series start and end dates, team1 and team2 with teamId, teamName, teamSName and imageId, and venueInfo with id, ground, city and timezone). Some array entries are advertisement slots with an adDetail object instead of fixture data. 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-schedules API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-schedules?key=<API_KEY>&teamId=2'
Query Result
Use Cases
- Build a follow-team fixture page keyed by teamId that lists the next matches by date.
- Create a local reminder-candidate list only after validating returned fixture times and changes; the endpoint itself is not a push-notification service.
- Add a team's upcoming home and away dates to a calendar export by converting the millisecond start timestamps to the viewer's timezone.
- Show a tour countdown widget for a selected team using the first returned fixture's start time and series name.
- Pre-plan travel or broadcast coverage by listing the grounds, cities and timezones of a team's next fixtures.
Frequently asked questions
What does the teams-get-schedules endpoint return?
It returns scheduled matches for the team identified by teamId. The source example shows teamMatchesData entries grouped by date label, each with matchInfo describing the fixture, opponents, series and venue.
Why is the path /schedule while the operation name is plural?
The operation is named teams-get-schedules, but the request path ends in /schedule. Call the path exactly as documented with your teamId in place of the placeholder.
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 fixtures where the team is named India.
Does it send reminders or push notifications?
No. It only returns fixture data. If you build reminders, validate the returned start times and re-check for changes before notifying anyone.
How should I read the start time of a fixture?
In the source example startDate and endDate are millisecond epoch strings, while status and hideScoreStatus hold a human-readable GMT start line. Check isTimeAnnounced before treating a time as final.
Why do some entries have adDetail instead of fixtures?
The source example interleaves advertisement slot objects with the fixture groups. Skip entries that lack matchDetailsMap when you build a schedule. No live probe was recorded, so confirm this against a real response.