Get cricket venue details by venueId
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the profile of 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 is a flat JSON object with ground, city, country, timezone, homeTeam, ends, capacity, imageId and imageUrl. In that example capacity is a formatted string (11,600), imageId is a string, ends lists the named ends of the ground as one comma-separated string and timezone is a UTC offset string such as +13:00. No live probe was recorded for this operation, so these fields come from an unverified source example; treat each field as optional and expect values to vary by venue. The example contains no coordinates, pitch report or ticketing fields.
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-info API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/venues-get-info?key=<API_KEY>&venueId=45'
Query Result
Use Cases
- Open a venue detail page from a series venues list or a match page by calling this endpoint with the selected venue's id.
- Fill a ground-guide section of a match preview with the ground name, city, country, home team and named ends.
- Convert scheduled start times into the stadium's local time by applying the returned timezone offset in a fixtures widget.
- Enrich an internal venue table keyed by venueId with capacity and image references while storing missing values as null.
- Pair the venue profile with the venue's scheduled-match and statistics endpoints to assemble a single ground hub for editors.
Frequently asked questions
What does the venues-get-info endpoint return?
It returns the details of one ground identified by venueId. The source example shows a flat object with ground, city, country, timezone, homeTeam, ends, capacity, imageId and imageUrl.
Where do I get a valid venueId?
Use the id field of a venue returned by the series venues endpoint. The prefilled value 45 is only a default example taken from the source documentation.
Was this response verified with a live call?
No. No probe call was recorded for this operation, so the field list comes from a source response example. Validate it against a real request for your venueId before relying on any field.
Are capacity and ends always returned?
Do not assume so. In the example capacity is a formatted string (11,600) and ends is a single comma-separated string, but other grounds may omit them or format them differently. Parse defensively and treat both as optional.
Does the response include coordinates or ticketing details?
The source example contains neither coordinates nor ticketing or pitch-report fields, so do not plan features that depend on them. Use the fields shown: ground, city, country, timezone, homeTeam, ends, capacity and image references.
How do I find matches played at this venue?
This endpoint only describes the ground. Use the venue matches endpoint with the same venueId for scheduled fixtures, and the venue stats endpoint for ground records.