> For the complete documentation index, see [llms.txt](https://docsv3.sportsapi360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docsv3.sportsapi360.com/cricket-docs/api-collection-cricket/stadium-data-api.md). # Stadium Data API ## Stadium Details > \### API Endpoint: Get Stadium Details\ > \ > This endpoint retrieves detailed information about a specific cricket stadium based on the provided stadium ID. It is useful for obtaining various statistics and attributes related to the stadium.\ > \ > \#### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`stadiumId\` (string): The unique identifier for the stadium whose details are to be fetched.\ > \ > \ > \#### Response\ > \ > The response will return a JSON object containing the following structure:\ > \ > \- \`image\` (string): URL or path to an image of the stadium.\ > \ > \- \`venueID\` (string): Unique identifier for the venue.\ > \ > \- \`fullName\` (string): Full name of the stadium.\ > \ > \- \`capacity\` (string): Seating capacity of the stadium.\ > \ > \- \`city\` (string): City where the stadium is located.\ > \ > \- \`country\` (string): Country where the stadium is located.\ > \ > \- \`bowlingEnds\` (string): Description of the bowling ends.\ > \ > \- \`floodlight\` (string): Information regarding floodlight availability.\ > \ > \ > Additionally, the response includes \`venueStats\`, which contains detailed statistics for different formats of cricket:\ > \ > \- \`odiDetails\`: Statistics for One Day Internationals.\ > \ > \- \`avgIstInningScore\` (string): Average score in the first innings.\ > \ > \- \`firstBattingWin\` (integer): Number of times the first batting team won.\ > \ > \- \`firstMatch\`, \`lastMatch\`, \`highestScoreMatch\`, \`lowestScoreMatch\`: Objects containing details about specific matches (e.g., match name, status, score, start date).\ > \ > \- \`testDetails\`: Statistics for Test matches (same structure as \`odiDetails\`).\ > \ > \- \`t20Details\`: Statistics for T20 matches (same structure as \`odiDetails\`).\ > \ > \ > This structured response allows consumers of the API to easily access and utilize stadium-related information for various cricket formats. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Stadium Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/stadium/{stadiumId}":{"get":{"tags":["Stadium Data API"],"summary":"Stadium Details","description":"### API Endpoint: Get Stadium Details\n\nThis endpoint retrieves detailed information about a specific cricket stadium based on the provided stadium ID. It is useful for obtaining various statistics and attributes related to the stadium.\n\n#### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/stadium/:stadiumId`\n \n- **Path Parameter**:\n \n - `stadiumId` (string): The unique identifier for the stadium whose details are to be fetched.\n \n\n#### Response\n\nThe response will return a JSON object containing the following structure:\n\n- `image` (string): URL or path to an image of the stadium.\n \n- `venueID` (string): Unique identifier for the venue.\n \n- `fullName` (string): Full name of the stadium.\n \n- `capacity` (string): Seating capacity of the stadium.\n \n- `city` (string): City where the stadium is located.\n \n- `country` (string): Country where the stadium is located.\n \n- `bowlingEnds` (string): Description of the bowling ends.\n \n- `floodlight` (string): Information regarding floodlight availability.\n \n\nAdditionally, the response includes `venueStats`, which contains detailed statistics for different formats of cricket:\n\n- `odiDetails`: Statistics for One Day Internationals.\n \n - `avgIstInningScore` (string): Average score in the first innings.\n \n - `firstBattingWin` (integer): Number of times the first batting team won.\n \n - `firstMatch`, `lastMatch`, `highestScoreMatch`, `lowestScoreMatch`: Objects containing details about specific matches (e.g., match name, status, score, start date).\n \n- `testDetails`: Statistics for Test matches (same structure as `odiDetails`).\n \n- `t20Details`: Statistics for T20 matches (same structure as `odiDetails`).\n \n\nThis structured response allows consumers of the API to easily access and utilize stadium-related information for various cricket formats.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"stadiumId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docsv3.sportsapi360.com/cricket-docs/api-collection-cricket/stadium-data-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.