List scheduled cricket matches by competition type, grouped by day, with optional lastTime paging

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

Returns the cricket fixture schedule for one competition group. The required `type` path parameter (default `international`) takes one of `international`, `league`, `domestic` or `women`. The optional numeric `lastTime` query parameter is a paging cursor: leave it empty to load the first page, or send an epoch timestamp in milliseconds (for example 1640883600000) to load the next page; the parameter note points to the `startDt` field returned by this endpoint as the value of interest. No live probe was recorded for this operation, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`) and a `matchScheduleMap` array. Entries are either a `scheduleAdWrapper` object or an `adDetail` object with `layout`, `name` and `position`. A `scheduleAdWrapper` holds a `date` label, a `longDate` string and a `matchScheduleList` array; each item there names a series (`seriesId`, `seriesName`, `seriesCategory`, sometimes `seriesHomeCountry`) and a `matchInfo` array of matches. A match shows `matchId`, `seriesId`, `matchDesc`, `matchFormat`, `startDate` and `endDate` (strings of epoch-style digits), `team1` and `team2` objects (`teamId`, `teamName`, `teamSName`, `imageId`, sometimes `isFullMember`) and a `venueInfo` object (`ground`, `city`, `country`, `timezone`). The example names the match start fields `startDate` and `endDate`, not `startDt`, so confirm which field to send as lastTime, the page size and the result for a type with no fixtures against a live response before depending on them.

API Features

Four competition groups The type path parameter accepts international, league, domestic or women, so one operation covers the four fixture lists. The form is preloaded with international and offers the other three as options.
Fixtures grouped by day In the source example each scheduleAdWrapper carries a date label and a longDate value with the matches of that day nested inside, which maps directly onto a day-by-day schedule layout.
Series context on every block Each matchScheduleList item names its series with seriesId, seriesName and seriesCategory, so a fixture can be linked back to its tournament without a second lookup.
Teams and venue per match A match entry lists team1 and team2 with teamId, teamName, teamSName and imageId, plus venueInfo with ground, city, country and a timezone offset string, enough for a fixture card.
Match identifiers for follow-up calls matchId and seriesId appear on each match, which a client can carry to the match detail, scorecard or series operations once a user taps a fixture.
lastTime paging for later fixtures Leave lastTime empty for the first page, or pass an epoch timestamp in milliseconds taken from a start field in the response to load the next page of the same type.

Live API Demo

GET /api/project/cricbuzz-cricket/matches-list-schedule

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/matches-list-schedule?key=<API_KEY>&type=international'
📢
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 schedule operation return?

It returns scheduled matches for the chosen type. No probe was recorded, so the shape comes from a truncated, unverified source example: an appIndex object and a matchScheduleMap array of day wrappers, each holding series blocks with matchInfo arrays, alongside advertising placeholder entries.

Which values can I send as type?

The parameter note lists four values: international, league, domestic and women. The form defaults to international. Any other value is outside the documented list, so test it before relying on it.

How does lastTime paging work?

Leave lastTime empty for the first page. For the next page send an epoch timestamp in milliseconds, such as 1640883600000. The note says to use the startDt field from this endpoint, yet the example shows startDate and longDate, so verify the right field and whether it is inclusive on a live response.

Why do some entries have no matches in them?

The example mixes scheduleAdWrapper day blocks with adDetail entries that hold only layout, name and position. Skip entries that lack a scheduleAdWrapper key. Coverage depends on the competition, so a type can also return few or no fixtures.

Can I filter the schedule by date, team or series?

No such filter is documented for this operation. Its only inputs are type and lastTime. Filter by teamId, seriesId or a date on your side after receiving the list, and do not assume a time zone beyond what the venueInfo timezone string shows.

Related operations

Guides

View Subscription Plans →