# Team Data API ## Team Short Info > \## Get Team Information\ > \ > This endpoint retrieves detailed information about a specific cricket team based on the provided \`teamId\`.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`teamId\` (string): The unique identifier of the cricket team whose information is being requested.\ > \ > \ > \### Response\ > \ > The response will return a JSON object containing 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.\ > \ > \- \`response\` (object): Contains detailed information about the team:\ > \ > \- \`teamID\` (string): The unique identifier for the team.\ > \ > \- \`name\` (string): The full name of the team.\ > \ > \- \`shortName\` (string): The abbreviated name of the team.\ > \ > \- \`description\` (string): A brief description of the team.\ > \ > \- \`image\` (string): A URL link to an image representing the team.\ > \ > \ > This endpoint is useful for applications that need to display cricket team information, allowing users to access details about their favorite teams. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Team Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/team/info/{teamId}":{"get":{"tags":["Team Data API"],"summary":"Team Short Info","description":"## Get Team Information\n\nThis endpoint retrieves detailed information about a specific cricket team based on the provided `teamId`.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/team/info/:teamId`\n \n- **Path Parameters**:\n \n - `teamId` (string): The unique identifier of the cricket team whose information is being requested.\n \n\n### Response\n\nThe response will return a JSON object containing 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.\n \n- `response` (object): Contains detailed information about the team:\n \n - `teamID` (string): The unique identifier for the team.\n \n - `name` (string): The full name of the team.\n \n - `shortName` (string): The abbreviated name of the team.\n \n - `description` (string): A brief description of the team.\n \n - `image` (string): A URL link to an image representing the team.\n \n\nThis endpoint is useful for applications that need to display cricket team information, allowing users to access details about their favorite teams.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"teamId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Team Info Full > \### Get Team Information\ > \ > This endpoint retrieves detailed information about a specific cricket team identified by the \`teamId\` parameter.\ > \ > \#### Request Type\ > \ > \- \*\*HTTP Method\*\*: GET\ > \ > \ > \#### API Version\ > \ > \- \*\*Version\*\*: v2\ > \ > \ > \#### Endpoint\ > \ > \- \*\*URL\*\*: \` > \ > \ > \#### Request Parameters\ > \ > \- \`teamId\` (path parameter):\ > \ > \- \*\*Type\*\*: String\ > \ > \- \*\*Description\*\*: The unique identifier for the cricket team whose information is being requested.\ > \ > \- \*\*Example\*\*: \`12345\`\ > \ > \ > \#### Expected Responses\ > \ > \- \*\*200 OK\*\*: Returns the detailed information of the requested cricket team.\ > \ > \- \*\*Response Body\*\*: Contains team details such as:\ > \ > \- \`name\`: The name of the cricket team.\ > \ > \- \`players\`: A list of players in the team.\ > \ > \- \`statistics\`: Various statistics related to the team.\ > \ > \- {"name": "Team A","players": \\\[ {"name": "Player 1", "role": "Batsman"}, {"name": "Player 2", "role": "Bowler"}\\],"statistics": { "matchesPlayed": 100, "wins": 70, "losses": 30}}\ > \ > \- \*\*404 Not Found\*\*: The specified \`teamId\` does not correspond to any existing cricket team.\ > \ > \- \*\*Response Body\*\*: An error message indicating that the team was not found.\ > \ > \- {"error": "Team not found"}\ > \ > \- \*\*401 Unauthorized\*\*: Authentication credentials are missing or invalid.\ > \ > \- \*\*Response Body\*\*: An error message indicating authentication failure.\ > \ > \- {"error": "Authentication failed"}\ > \ > \ > \#### Authentication\ > \ > Ensure that you include the appropriate authentication headers in your request to access this endpoint.\ > \ > \#### Headers\ > \ > \- Include necessary headers as required by your authentication method (e.g., API Key, Bearer Token). ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Team Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/team/{teamId}":{"get":{"tags":["Team Data API"],"summary":"Team Info Full","description":"### Get Team Information\n\nThis endpoint retrieves detailed information about a specific cricket team identified by the `teamId` parameter.\n\n#### Request Type\n\n- **HTTP Method**: GET\n \n\n#### API Version\n\n- **Version**: v2\n \n\n#### Endpoint\n\n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/team/:teamId`\n \n\n#### Request Parameters\n\n- `teamId` (path parameter):\n \n - **Type**: String\n \n - **Description**: The unique identifier for the cricket team whose information is being requested.\n \n - **Example**: `12345`\n \n\n#### Expected Responses\n\n- **200 OK**: Returns the detailed information of the requested cricket team.\n \n - **Response Body**: Contains team details such as:\n \n - `name`: The name of the cricket team.\n \n - `players`: A list of players in the team.\n \n - `statistics`: Various statistics related to the team.\n \n - {\"name\": \"Team A\",\"players\": \\[ {\"name\": \"Player 1\", \"role\": \"Batsman\"}, {\"name\": \"Player 2\", \"role\": \"Bowler\"}\\],\"statistics\": { \"matchesPlayed\": 100, \"wins\": 70, \"losses\": 30}}\n \n- **404 Not Found**: The specified `teamId` does not correspond to any existing cricket team.\n \n - **Response Body**: An error message indicating that the team was not found.\n \n - {\"error\": \"Team not found\"}\n \n- **401 Unauthorized**: Authentication credentials are missing or invalid.\n \n - **Response Body**: An error message indicating authentication failure.\n \n - {\"error\": \"Authentication failed\"}\n \n\n#### Authentication\n\nEnsure that you include the appropriate authentication headers in your request to access this endpoint.\n\n#### Headers\n\n- Include necessary headers as required by your authentication method (e.g., API Key, Bearer Token).","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"teamId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Team Recent > \### Endpoint Description\ > \ > This endpoint retrieves the recent match details for a specified cricket team. It provides comprehensive information about the team's performance across different formats of the game, including One Day Internationals (ODI), Twenty20 (T20), and Test matches. This data can be useful for fans, analysts, and teams to assess recent performances and trends.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`teamId\` (string): The unique identifier of the cricket team whose information is being requested.\ > \ > \ > \### Expected Response\ > \ > The response will return a JSON object structured as follows:\ > \ > \- \*\*odi\*\*: An object containing the recent ODI match details.\ > \ > \- \*\*winLost\*\*: An array indicating the win/loss status for the matches.\ > \ > \- \*\*scoreCard\*\*: An array of scorecard objects for each ODI match, which includes:\ > \ > \- \*\*win\*\*: Indicates if the team won the match.\ > \ > \- \*\*matchName\*\*: The name of the match.\ > \ > \- \*\*matchNumber\*\*: The match number in the series.\ > \ > \- \*\*startDate\*\*: The date when the match started.\ > \ > \- \*\*matchStatus\*\*: The current status of the match (e.g., ongoing, completed).\ > \ > \- \*\*winningTeamID\*\*: The ID of the team that won the match.\ > \ > \- \*\*isLiveCriclyticsAvailable\*\*: A boolean indicating if live Criclytics data is available for the match.\ > \ > \- \*\*matchType\*\*: The type of match (e.g., ODI).\ > \ > \- \*\*venue\*\*: The venue where the match was held.\ > \ > \- \*\*matchResult\*\*: The final result of the match.\ > \ > \- \*\*matchID\*\*: The unique identifier for the match.\ > \ > \- \*\*matchScore\*\*: An array containing details about the teams and their scores, including:\ > \ > \- \*\*teamShortName\*\*: The short name of the team.\ > \ > \- \*\*teamID\*\*: The unique identifier for the team.\ > \ > \- \*\*teamFullName\*\*: The full name of the team.\ > \ > \- \*\*teamScore\*\*: An array of objects providing score details for each inning, which includes:\ > \ > \- \*\*inning\*\*: The inning number.\ > \ > \- \*\*inningNumber\*\*: The specific number of the inning.\ > \ > \- \*\*battingTeam\*\*: The name of the batting team.\ > \ > \- \*\*runsScored\*\*: The total runs scored in that inning.\ > \ > \- \*\*wickets\*\*: The number of wickets lost.\ > \ > \- \*\*overs\*\*: The total overs faced.\ > \ > \- \*\*runRate\*\*: The run rate achieved.\ > \ > \- \*\*battingSide\*\*: The side that was batting.\ > \ > \- \*\*battingTeamShortName\*\*: The short name of the batting team.\ > \ > \- \*\*declared\*\*: A boolean indicating if the inning was declared.\ > \ > \- \*\*folowOn\*\*: A boolean indicating if the follow-on rule was applied.\ > \ > \- \*\*t20\*\*: Similar structure as the ODI section, but for T20 matches.\ > \ > \- \*\*test\*\*: Similar structure as the ODI section, but for Test matches.\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`teamId\` provided in the request is valid to receive accurate match details.\ > \ > \- The response includes detailed score information for each match, which can be useful for analyzing team performance over recent games.\ > \ > \- This endpoint is particularly useful for sports analysts and fans looking to track the performance of their favorite teams over time. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Team Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/team/{teamId}/recent":{"get":{"tags":["Team Data API"],"summary":"Team Recent","description":"### Endpoint Description\n\nThis endpoint retrieves the recent match details for a specified cricket team. It provides comprehensive information about the team's performance across different formats of the game, including One Day Internationals (ODI), Twenty20 (T20), and Test matches. This data can be useful for fans, analysts, and teams to assess recent performances and trends.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/team/:teamId/recent`\n \n- **Path Parameters**:\n \n - `teamId` (string): The unique identifier of the cricket team whose information is being requested.\n \n\n### Expected Response\n\nThe response will return a JSON object structured as follows:\n\n- **odi**: An object containing the recent ODI match details.\n \n - **winLost**: An array indicating the win/loss status for the matches.\n \n - **scoreCard**: An array of scorecard objects for each ODI match, which includes:\n \n - **win**: Indicates if the team won the match.\n \n - **matchName**: The name of the match.\n \n - **matchNumber**: The match number in the series.\n \n - **startDate**: The date when the match started.\n \n - **matchStatus**: The current status of the match (e.g., ongoing, completed).\n \n - **winningTeamID**: The ID of the team that won the match.\n \n - **isLiveCriclyticsAvailable**: A boolean indicating if live Criclytics data is available for the match.\n \n - **matchType**: The type of match (e.g., ODI).\n \n - **venue**: The venue where the match was held.\n \n - **matchResult**: The final result of the match.\n \n - **matchID**: The unique identifier for the match.\n \n - **matchScore**: An array containing details about the teams and their scores, including:\n \n - **teamShortName**: The short name of the team.\n \n - **teamID**: The unique identifier for the team.\n \n - **teamFullName**: The full name of the team.\n \n - **teamScore**: An array of objects providing score details for each inning, which includes:\n \n - **inning**: The inning number.\n \n - **inningNumber**: The specific number of the inning.\n \n - **battingTeam**: The name of the batting team.\n \n - **runsScored**: The total runs scored in that inning.\n \n - **wickets**: The number of wickets lost.\n \n - **overs**: The total overs faced.\n \n - **runRate**: The run rate achieved.\n \n - **battingSide**: The side that was batting.\n \n - **battingTeamShortName**: The short name of the batting team.\n \n - **declared**: A boolean indicating if the inning was declared.\n \n - **folowOn**: A boolean indicating if the follow-on rule was applied.\n \n- **t20**: Similar structure as the ODI section, but for T20 matches.\n \n- **test**: Similar structure as the ODI section, but for Test matches.\n \n\n### Notes\n\n- Ensure that the `teamId` provided in the request is valid to receive accurate match details.\n \n- The response includes detailed score information for each match, which can be useful for analyzing team performance over recent games.\n \n- This endpoint is particularly useful for sports analysts and fans looking to track the performance of their favorite teams over time.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"teamId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Team Schedule Matches > \## Get Recent Matches for a Cricket Team\ > \ > This endpoint retrieves the recent match details for a specific cricket team identified by the \`teamId\` parameter.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*URL\*\*: \` > \ > \ > \#### Path Parameters\ > \ > \- \`teamId\` (string): The unique identifier for the cricket team whose recent matches you want to fetch.\ > \ > \ > \### Response\ > \ > The response will be a JSON array containing objects with the following fields:\ > \ > \- \`matchID\` (string): The unique identifier for the match.\ > \ > \- \`matchDateTimeIST\` (string): The date and time of the match in IST.\ > \ > \- \`matchStatus\` (string): The current status of the match (e.g., scheduled, completed).\ > \ > \- \`compType\` (string): The type of competition (e.g., league, tournament).\ > \ > \- \`awayTeamID\` (string): The unique identifier for the away team.\ > \ > \- \`homeTeamName\` (string): The name of the home team.\ > \ > \- \`homeTeamID\` (string): The unique identifier for the home team.\ > \ > \- \`awayTeamName\` (string): The name of the away team.\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`teamId\` provided is valid to receive accurate match details.\ > \ > \- The response may contain multiple match objects, depending on the number of recent matches played by the team. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Team Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/team/{teamId}/schedule":{"get":{"tags":["Team Data API"],"summary":"Team Schedule Matches","description":"## Get Recent Matches for a Cricket Team\n\nThis endpoint retrieves the recent match details for a specific cricket team identified by the `teamId` parameter.\n\n### Request\n\n- **Method**: `GET`\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/team/:teamId/schedule`\n \n\n#### Path Parameters\n\n- `teamId` (string): The unique identifier for the cricket team whose recent matches you want to fetch.\n \n\n### Response\n\nThe response will be a JSON array containing objects with the following fields:\n\n- `matchID` (string): The unique identifier for the match.\n \n- `matchDateTimeIST` (string): The date and time of the match in IST.\n \n- `matchStatus` (string): The current status of the match (e.g., scheduled, completed).\n \n- `compType` (string): The type of competition (e.g., league, tournament).\n \n- `awayTeamID` (string): The unique identifier for the away team.\n \n- `homeTeamName` (string): The name of the home team.\n \n- `homeTeamID` (string): The unique identifier for the home team.\n \n- `awayTeamName` (string): The name of the away team.\n \n\n### Notes\n\n- Ensure that the `teamId` provided is valid to receive accurate match details.\n \n- The response may contain multiple match objects, depending on the number of recent matches played by the team.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"teamId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Team Stats > \## API Endpoint: Get Team Statistics\ > \ > \### Request Method\ > \ > \`GET\`\ > \ > \### Endpoint\ > \ > \` > \ > \### Parameters\ > \ > \- \`teamId\` (path parameter): The unique identifier for the cricket team whose statistics are being requested.\ > \ > \ > \### Expected Response Format\ > \ > The response will return a JSON object containing various statistics for the specified cricket team, structured as follows:\ > \ > \- \`image\`: A string representing the team's image URL (if available).\ > \ > \- \`teamID\`: A string representing the unique identifier for the team.\ > \ > \- \`teamName\`: A string representing the full name of the team.\ > \ > \- \`teamShortName\`: A string representing the abbreviated name of the team.\ > \ > \- \`odi\`: An object containing One Day International statistics:\ > \ > \- \`matchesWon\`: Number of matches won.\ > \ > \- \`matchesLost\`: Number of matches lost.\ > \ > \- \`matchesPlayed\`: Total matches played.\ > \ > \- \`matchesTied\`: Number of matches tied.\ > \ > \- \`winPercentage\`: Win percentage.\ > \ > \- \`mostRuns\`: An object detailing the player with the most runs, including:\ > \ > \- \`playerName\`: Name of the player.\ > \ > \- \`playerID\`: Unique identifier for the player.\ > \ > \- \`matchesPlayed\`: Matches played by the player.\ > \ > \- \`runs\`: Total runs scored by the player.\ > \ > \- \`average\`: Batting average of the player.\ > \ > \- \`mostWickets\`: An object detailing the player with the most wickets, including:\ > \ > \- \`playerName\`: Name of the player.\ > \ > \- \`playerID\`: Unique identifier for the player.\ > \ > \- \`matchesPlayed\`: Matches played by the player.\ > \ > \- \`wicket\`: Total wickets taken by the player.\ > \ > \- \`economy\`: Economy rate of the player.\ > \ > \- \`bestScore\`: An object detailing the player's best score, including:\ > \ > \- \`playerName\`: Name of the player.\ > \ > \- \`playerID\`: Unique identifier for the player.\ > \ > \- \`matchesPlayed\`: Matches played by the player.\ > \ > \- \`runs\`: Runs scored in the best innings.\ > \ > \- \`average\`: Batting average of the player.\ > \ > \- \`bestFigures\`: An object detailing the player's best bowling figures, including:\ > \ > \- \`playerName\`: Name of the player.\ > \ > \- \`playerID\`: Unique identifier for the player.\ > \ > \- \`matchesPlayed\`: Matches played by the player.\ > \ > \- \`runs\`: Runs conceded in the best bowling performance.\ > \ > \- \`average\`: Bowling average of the player.\ > \ > \- \`test\`: An object containing Test match statistics with the same structure as \`odi\`.\ > \ > \- \`t20\`: An object containing T20 match statistics with the same structure as \`odi\`.\ > \ > \ > This endpoint provides a comprehensive overview of a cricket team's performance across different formats of the game. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Team Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/team/{teamId}/stats":{"get":{"tags":["Team Data API"],"summary":"Team Stats","description":"## API Endpoint: Get Team Statistics\n\n### Request Method\n\n`GET`\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/cricket/api/v2/team/:teamId/stats`\n\n### Parameters\n\n- `teamId` (path parameter): The unique identifier for the cricket team whose statistics are being requested.\n \n\n### Expected Response Format\n\nThe response will return a JSON object containing various statistics for the specified cricket team, structured as follows:\n\n- `image`: A string representing the team's image URL (if available).\n \n- `teamID`: A string representing the unique identifier for the team.\n \n- `teamName`: A string representing the full name of the team.\n \n- `teamShortName`: A string representing the abbreviated name of the team.\n \n- `odi`: An object containing One Day International statistics:\n \n - `matchesWon`: Number of matches won.\n \n - `matchesLost`: Number of matches lost.\n \n - `matchesPlayed`: Total matches played.\n \n - `matchesTied`: Number of matches tied.\n \n - `winPercentage`: Win percentage.\n \n - `mostRuns`: An object detailing the player with the most runs, including:\n \n - `playerName`: Name of the player.\n \n - `playerID`: Unique identifier for the player.\n \n - `matchesPlayed`: Matches played by the player.\n \n - `runs`: Total runs scored by the player.\n \n - `average`: Batting average of the player.\n \n - `mostWickets`: An object detailing the player with the most wickets, including:\n \n - `playerName`: Name of the player.\n \n - `playerID`: Unique identifier for the player.\n \n - `matchesPlayed`: Matches played by the player.\n \n - `wicket`: Total wickets taken by the player.\n \n - `economy`: Economy rate of the player.\n \n - `bestScore`: An object detailing the player's best score, including:\n \n - `playerName`: Name of the player.\n \n - `playerID`: Unique identifier for the player.\n \n - `matchesPlayed`: Matches played by the player.\n \n - `runs`: Runs scored in the best innings.\n \n - `average`: Batting average of the player.\n \n - `bestFigures`: An object detailing the player's best bowling figures, including:\n \n - `playerName`: Name of the player.\n \n - `playerID`: Unique identifier for the player.\n \n - `matchesPlayed`: Matches played by the player.\n \n - `runs`: Runs conceded in the best bowling performance.\n \n - `average`: Bowling average of the player.\n \n- `test`: An object containing Test match statistics with the same structure as `odi`.\n \n- `t20`: An object containing T20 match statistics with the same structure as `odi`.\n \n\nThis endpoint provides a comprehensive overview of a cricket team's performance across different formats of the game.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"teamId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Team Squads > \# Get Team Squads\ > \ > This endpoint retrieves the squad details for a specific cricket team identified by the \`teamId\`. It provides information on the players in three formats: One Day Internationals (ODI), Test matches, and Twenty20 (T20) formats.\ > \ > \## Request\ > \ > \*\*Method:\*\* GET \ > \*\*Endpoint:\*\* \` > \ > \### Path Parameters\ > \ > \- \`teamId\` (string): The unique identifier for the cricket team whose squad details are being requested.\ > \ > \ > \### Response Fields\ > \ > \- \`odiSquad\`: An array of players representing the ODI squad, where each player has:\ > \ > \- \`playerID\`: Unique identifier for the player.\ > \ > \- \`playerName\`: Name of the player.\ > \ > \- \`playerImage\`: URL to the player's image.\ > \ > \- \`testSquad\`: An array of players representing the Test squad, with the same structure as \`odiSquad\`.\ > \ > \- \`t20Squad\`: An array of players representing the T20 squad, also with the same structure as \`odiSquad\`.\ > \ > \ > This endpoint is useful for obtaining the current squad composition for a team across different formats of the game. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Team Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/team/{teamId}/squads":{"get":{"tags":["Team Data API"],"summary":"Team Squads","description":"# Get Team Squads\n\nThis endpoint retrieves the squad details for a specific cricket team identified by the `teamId`. It provides information on the players in three formats: One Day Internationals (ODI), Test matches, and Twenty20 (T20) formats.\n\n## Request\n\n**Method:** GET \n**Endpoint:** `https://apiv3.sportsapi360.com/cricket/api/v2/team/:teamId/squads`\n\n### Path Parameters\n\n- `teamId` (string): The unique identifier for the cricket team whose squad details are being requested.\n \n\n### Response Fields\n\n- `odiSquad`: An array of players representing the ODI squad, where each player has:\n \n - `playerID`: Unique identifier for the player.\n \n - `playerName`: Name of the player.\n \n - `playerImage`: URL to the player's image.\n \n- `testSquad`: An array of players representing the Test squad, with the same structure as `odiSquad`.\n \n- `t20Squad`: An array of players representing the T20 squad, also with the same structure as `odiSquad`.\n \n\nThis endpoint is useful for obtaining the current squad composition for a team across different formats of the game.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"teamId","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/team-data-api.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.