Get scheduled cricket matches at a venue by venueId

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

Returns the scheduled matches for one cricket ground. The single required path input is venueId, a numeric venue identifier taken from the id field returned by the series venues endpoint; the default example value is 45. The source response example shows a top-level matchDetails array whose entries hold a matchDetailsMap with a key (the series name, such as a domestic one-day trophy) and a match array of matchInfo objects, plus an appIndex object with seoTitle and webURL. Each matchInfo carries matchId, matchDesc, matchFormat, state, status, hideScoreStatus, isTimeAnnounced, startDate and endDate (epoch milliseconds as strings), seriesId, seriesName, seriesStartDt, seriesEndDt, team1 and team2 (teamId, teamName, teamSName, imageId) and venueInfo (id, ground, city, timezone). No live probe was recorded for this operation, so these fields come from an unverified source example, and the example is truncated. It covers scheduled fixtures, not a complete archive of past results at the ground, and a venue with nothing scheduled can return no content.

API Features

Fixtures filtered by ground One numeric venueId returns the matches scheduled at that venue, so a ground page needs no client-side filtering of a global schedule.
Matches grouped under a series key Entries in matchDetails carry a matchDetailsMap whose key names the series and whose match array lists its fixtures at the venue, which suits a series-by-series layout.
Epoch-millisecond start and end times startDate and endDate are epoch-millisecond strings, paired with the venue timezone offset, so local and UTC kickoff times can be computed without parsing display text.
Teams with IDs and short codes team1 and team2 each expose teamId, teamName, teamSName and imageId, letting a fixture row link to team pages and show compact badges.
Status text and match identifiers Each match includes matchId, matchDesc, matchFormat, state and a status string such as a match-start notice, giving you the keys and labels needed for a schedule list that links onward.

Live API Demo

GET /api/project/cricbuzz-cricket/venues-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/venues-get-matches?key=<API_KEY>&venueId=45'
📢
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 venues-get-matches endpoint return?

It returns the matches scheduled at the venue identified by venueId. The source example shows a matchDetails array, each entry with a matchDetailsMap holding a series key and a match array of matchInfo objects, plus an appIndex object.

Where do I get a valid venueId?

Use the id field of a venue from the series venues endpoint. The prefilled value 45 is only a default example from the source documentation and was not confirmed by a live call here.

Does this include past results at the ground?

It is documented as scheduled matches by venue, and the source example shows upcoming fixtures only. Do not treat it as a complete history of games played at the venue.

How should I read startDate and endDate?

In the source example they are epoch-millisecond values delivered as strings. Convert them to numbers before building dates, and use the venueInfo timezone offset to display local time.

What happens if no matches are scheduled?

Coverage depends on the data available for each ground, so a venue with no scheduled matches may return an empty or missing matchDetails section. Handle that case in your interface instead of assuming a populated list.

Was this response verified with a live call?

No. No probe call was recorded for this operation. The fields listed come from a truncated source example, so confirm the structure with your own request before shipping.

Related operations

Guides

View Subscription Plans →