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
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/venues-get-matches API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/venues-get-matches?key=<API_KEY>&venueId=45'
Query Result
Use Cases
- Build a ground-specific fixtures page that lists every scheduled match at the venue the visitor selected.
- Help editors plan coverage for a stadium by pulling the upcoming matches there and grouping them by series.
- Feed a local-time calendar for a venue by combining startDate with the returned venueInfo timezone offset.
- Use matchId and seriesId from each row to link a venue fixture to its scorecard, commentary or series pages.
- Alert a venue-focused newsletter or ticket-planning tool when a new match with a different matchFormat appears in the schedule.
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.