# Commentery ## Match Commentary > \### Get Match Commentary\ > \ > This endpoint retrieves the commentary for a specific cricket match based on the match ID provided. It delivers detailed information about each ball played in the innings, including commentary, runs scored, and wicket details.\ > \ > \#### Request Method\ > \ > \- \*\*GET\*\*\ > \ > \ > \#### Request Endpoint\ > \ > \- \` > \ > \ > \#### Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter): The unique identifier of the match for which commentary is being requested.\ > \ > \- \*\*id\*\* (query parameter): A specific identifier to retrieve next commentary details.\ > \ > \ > \#### Response Structure\ > \ > The response is returned in JSON format and contains an array of commentary objects, each including the following fields:\ > \ > \- \*\*id\*\* (integer): The unique identifier for the commentary entry.\ > \ > \- \*\*over\*\* (string): The over number in which the ball was bowled.\ > \ > \- \*\*ballType\*\* (string): The type of ball bowled.\ > \ > \- \*\*type\*\* (string): The type of commentary.\ > \ > \- \*\*isBall\*\* (boolean): Indicates if the entry is related to a ball.\ > \ > \- \*\*runs\*\* (string): The runs scored on that ball.\ > \ > \- \*\*zad\*\* (string): Additional data related to the ball.\ > \ > \- \*\*bowlerName\*\* (string): The name of the bowler.\ > \ > \- \*\*batsmanName\*\* (string): The name of the batsman.\ > \ > \- \*\*battingStyle\*\* (string): The batting style of the batsman.\ > \ > \- \*\*commentary\*\* (string): The commentary related to the ball.\ > \ > \- \*\*wicket\*\* (boolean): Indicates if a wicket fell on that ball.\ > \ > \- \*\*isLastBall\*\* (boolean): Indicates if this is the last ball of the over.\ > \ > \- \*\*batsmanID\*\* (string): The ID of the batsman.\ > \ > \- \*\*bowlerID\*\* (string): The ID of the bowler.\ > \ > \- \*\*innings\*\* (string): The innings identifier.\ > \ > \ > This endpoint is crucial for accessing live commentary during a cricket match, enhancing the experience for fans and analysts alike. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Commentery"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/commentary":{"get":{"tags":["Commentery"],"summary":"Match Commentary","description":"### Get Match Commentary\n\nThis endpoint retrieves the commentary for a specific cricket match based on the match ID provided. It delivers detailed information about each ball played in the innings, including commentary, runs scored, and wicket details.\n\n#### Request Method\n\n- **GET**\n \n\n#### Request Endpoint\n\n- `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/commentary?id=202200`\n \n\n#### Request Parameters\n\n- **matchId** (path parameter): The unique identifier of the match for which commentary is being requested.\n \n- **id** (query parameter): A specific identifier to retrieve next commentary details.\n \n\n#### Response Structure\n\nThe response is returned in JSON format and contains an array of commentary objects, each including the following fields:\n\n- **id** (integer): The unique identifier for the commentary entry.\n \n- **over** (string): The over number in which the ball was bowled.\n \n- **ballType** (string): The type of ball bowled.\n \n- **type** (string): The type of commentary.\n \n- **isBall** (boolean): Indicates if the entry is related to a ball.\n \n- **runs** (string): The runs scored on that ball.\n \n- **zad** (string): Additional data related to the ball.\n \n- **bowlerName** (string): The name of the bowler.\n \n- **batsmanName** (string): The name of the batsman.\n \n- **battingStyle** (string): The batting style of the batsman.\n \n- **commentary** (string): The commentary related to the ball.\n \n- **wicket** (boolean): Indicates if a wicket fell on that ball.\n \n- **isLastBall** (boolean): Indicates if this is the last ball of the over.\n \n- **batsmanID** (string): The ID of the batsman.\n \n- **bowlerID** (string): The ID of the bowler.\n \n- **innings** (string): The innings identifier.\n \n\nThis endpoint is crucial for accessing live commentary during a cricket match, enhancing the experience for fans and analysts alike.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"query","schema":{"type":"integer"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Commentary BallByBall > \### Get Ball-by-Ball Commentary for a Match\ > \ > This endpoint retrieves detailed ball-by-ball commentary for a specific cricket match during a given innings. It provides insights into each ball bowled, including commentary, runs scored, and any wickets that may have fallen.\ > \ > \#### Request Method\ > \ > \- \*\*GET\*\*\ > \ > \ > \#### Request Endpoint\ > \ > \- \` > \ > \ > \#### Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter):\ > \ > \- The unique identifier of the match for which commentary is being requested.\ > \ > \- \*\*innings\*\* (query parameter):\ > \ > \- Indicates the innings number (e.g., \`1\` for the first innings, \`2\` for the second innings).\ > \ > \ > \#### Response Structure\ > \ > The response is returned in JSON format and contains the following fields:\ > \ > \- \*\*status\*\* (boolean):\ > \ > \- Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer):\ > \ > \- A code representing the status of the response.\ > \ > \- \*\*message\*\* (string):\ > \ > \- A message providing additional context about the response, if any.\ > \ > \- \*\*response\*\* (array):\ > \ > \- An array containing commentary details for each ball, structured as follows:\ > \ > \- Each element is an array that may include various details related to the ball.\ > \ > \ > \#### Notes\ > \ > \- The endpoint is essential for accessing real-time commentary and enhances the viewing experience for cricket fans by providing detailed insights into each ball bowled.\ > \ > \- Ensure that the \`matchId\` and \`innings\` parameters are correctly specified to retrieve the desired commentary. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Commentery"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/commentary/ballByBall":{"get":{"tags":["Commentery"],"summary":"Match Commentary BallByBall","description":"### Get Ball-by-Ball Commentary for a Match\n\nThis endpoint retrieves detailed ball-by-ball commentary for a specific cricket match during a given innings. It provides insights into each ball bowled, including commentary, runs scored, and any wickets that may have fallen.\n\n#### Request Method\n\n- **GET**\n \n\n#### Request Endpoint\n\n- `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/commentary/ballByBall?innings=2`\n \n\n#### Request Parameters\n\n- **matchId** (path parameter):\n \n - The unique identifier of the match for which commentary is being requested.\n \n- **innings** (query parameter):\n \n - Indicates the innings number (e.g., `1` for the first innings, `2` for the second innings).\n \n\n#### Response Structure\n\nThe response is returned in JSON format and contains the following fields:\n\n- **status** (boolean):\n \n - Indicates whether the request was successful.\n \n- **statusCode** (integer):\n \n - A code representing the status of the response.\n \n- **message** (string):\n \n - A message providing additional context about the response, if any.\n \n- **response** (array):\n \n - An array containing commentary details for each ball, structured as follows:\n \n - Each element is an array that may include various details related to the ball.\n \n\n#### Notes\n\n- The endpoint is essential for accessing real-time commentary and enhances the viewing experience for cricket fans by providing detailed insights into each ball bowled.\n \n- Ensure that the `matchId` and `innings` parameters are correctly specified to retrieve the desired commentary.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"innings","in":"query","schema":{"type":"integer"},"description":"1 to 10"},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Highlights > \### Get Match Highlights\ > \ > This endpoint retrieves the highlights of a specific cricket match for a given innings. It provides detailed information about each ball played in the innings, including commentary, runs scored, and wicket details.\ > \ > \#### Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter): The unique identifier of the match for which highlights are being requested.\ > \ > \- \*\*innings\*\* (query parameter): Indicates the innings number (e.g., \`1\` for the first innings).\ > \ > \ > \#### Response Structure\ > \ > The response is returned in JSON format and contains the following fields:\ > \ > \- \*\*status\*\* (boolean): Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the response.\ > \ > \- \*\*message\*\* (string): A message providing additional context about the response, if any.\ > \ > \- \*\*response\*\* (array): An array of highlight objects, each containing:\ > \ > \- \*\*matchID\*\* (string): The ID of the match.\ > \ > \- \*\*ballID\*\* (string): The ID of the specific ball.\ > \ > \- \*\*ballNumber\*\* (string): The number of the ball in the innings.\ > \ > \- \*\*innings\*\* (string): The innings identifier.\ > \ > \- \*\*over\*\* (string): The over number in which the ball was bowled.\ > \ > \- \*\*overNumber\*\* (string): The sequential number of the over.\ > \ > \- \*\*commentary\*\* (string): Commentary related to the ball.\ > \ > \- \*\*teamID\*\* (string): The ID of the team involved.\ > \ > \- \*\*teamName\*\* (string): The name of the team.\ > \ > \- \*\*runs\*\* (string): The runs scored on that ball.\ > \ > \- \*\*xCoordinate\*\* (integer): The x-coordinate related to the ball's delivery.\ > \ > \- \*\*yCoordinate\*\* (integer): The y-coordinate related to the ball's delivery.\ > \ > \- \*\*zad\*\* (string): Additional data related to the ball.\ > \ > \- \*\*wicket\*\* (boolean): Indicates if a wicket fell on that ball.\ > \ > \ > This endpoint is essential for accessing detailed match highlights and can be used to enhance the viewing experience for cricket fans. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Commentery"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/highlights":{"get":{"tags":["Commentery"],"summary":"Match Highlights","description":"### Get Match Highlights\n\nThis endpoint retrieves the highlights of a specific cricket match for a given innings. It provides detailed information about each ball played in the innings, including commentary, runs scored, and wicket details.\n\n#### Request Parameters\n\n- **matchId** (path parameter): The unique identifier of the match for which highlights are being requested.\n \n- **innings** (query parameter): Indicates the innings number (e.g., `1` for the first innings).\n \n\n#### Response Structure\n\nThe response is returned in JSON format and contains the following fields:\n\n- **status** (boolean): Indicates whether the request was successful.\n \n- **statusCode** (integer): A code representing the status of the response.\n \n- **message** (string): A message providing additional context about the response, if any.\n \n- **response** (array): An array of highlight objects, each containing:\n \n - **matchID** (string): The ID of the match.\n \n - **ballID** (string): The ID of the specific ball.\n \n - **ballNumber** (string): The number of the ball in the innings.\n \n - **innings** (string): The innings identifier.\n \n - **over** (string): The over number in which the ball was bowled.\n \n - **overNumber** (string): The sequential number of the over.\n \n - **commentary** (string): Commentary related to the ball.\n \n - **teamID** (string): The ID of the team involved.\n \n - **teamName** (string): The name of the team.\n \n - **runs** (string): The runs scored on that ball.\n \n - **xCoordinate** (integer): The x-coordinate related to the ball's delivery.\n \n - **yCoordinate** (integer): The y-coordinate related to the ball's delivery.\n \n - **zad** (string): Additional data related to the ball.\n \n - **wicket** (boolean): Indicates if a wicket fell on that ball.\n \n\nThis endpoint is essential for accessing detailed match highlights and can be used to enhance the viewing experience for cricket fans.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"innings","in":"query","schema":{"type":"integer"},"description":"1 to 10"},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` --- # Agent Instructions: 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: ``` GET https://docsv3.sportsapi360.com/cricket-docs/api-collection-cricket/commentery.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.