List recent and upcoming matches in a cricket series by seriesId

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

Returns the fixtures of one cricket series, selected with the required numeric seriesId path parameter (the id value from the series list or archived series list endpoints). The source response example documents an appIndex block (seoTitle, webURL) and a matchDetails array. Each matchDetailsMap entry has a date-range key, a match list and the seriesId. Every match carries matchInfo (matchId, matchDesc, matchFormat, state, status, startDate and endDate as epoch-millisecond strings, currBatTeamId, isTimeAnnounced, team1 and team2 with teamId, teamName, teamSName and imageId, and venueInfo with ground, city and timezone) plus a matchScore object with per-team, per-innings runs, wickets, overs and declaration flags. Advertisement placeholder entries (adDetail with layout, name and position) can appear between fixtures and should be skipped. These fields come from a source example rather than a live probe, so treat optional blocks such as matchScore as coverage-dependent.

API Features

Series-scoped fixture list One seriesId returns the recent and upcoming matches of a single tournament or tour, so a tournament page does not need a global match search.
Date-range grouping keys Fixtures arrive inside matchDetailsMap groups whose key is a readable date-range label, such as the multi-day span of a Test, ready to use as schedule headings.
Match identity and format fields Each matchInfo includes matchId, matchDesc, matchFormat, state and a status sentence, giving stable keys and display labels for every fixture.
Teams and venue on every fixture The team1 and team2 objects provide teamId, teamName, teamSName and imageId, while venueInfo adds ground, city and a UTC offset timezone.
Per-innings score summary The matchScore object reports runs, wickets, overs and declaration flags by innings for each side, enough for a result line on a list page.
Ad placeholders to filter out Entries that contain adDetail instead of matchDetailsMap are layout placeholders, so a client can skip them by checking which key is present.

Live API Demo

GET /api/project/cricbuzz-cricket/series-get-matches

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

Use Cases

Frequently asked questions

Where do I get the seriesId for this endpoint?

Use the id field returned by the series list or archived series list endpoints. The default value 3641 is an example id that the source response example associates with the New Zealand tour of England, 2022.

Does it return both finished and upcoming matches?

The endpoint is described as returning recent and upcoming matches for a series. The source example only shows finished fixtures with a status sentence and innings scores, and no live probe was recorded here, so for upcoming fixtures expect state and status to differ and score blocks such as matchScore to be partial or absent.

How are startDate and endDate formatted?

In the source example they are epoch-millisecond values serialized as strings. Convert them on the client and use venueInfo.timezone, a UTC offset such as +01:00, when you need to show local match time.

What are the adDetail entries inside matchDetails?

They are layout placeholders with layout, name and position fields, not matches. Skip any array element that has no matchDetailsMap when you build a fixture list.

Can I get full scorecards or commentary from this endpoint?

No. It gives a fixture list with summary scores only. Pass a matchId to the match scorecard or commentary endpoints of this product when you need batting cards, bowling figures or ball-by-ball text.

What should I do when a series returns no fixtures?

Coverage depends on the competition, so handle an empty or missing matchDetails array and any non-200 response as a normal empty state instead of retrying with a different seriesId automatically.

Related operations

Guides

View Subscription Plans →