# Player Data API ## Player Details > \## Get Player Details\ > \ > This endpoint retrieves detailed information about a specific cricket player based on their unique player ID.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`playerId\` (string): The unique identifier for the player whose details are being requested.\ > \ > \ > \### Response\ > \ > \- \*\*Status Code\*\*: \`200 OK\`\ > \ > \- \*\*Content-Type\*\*: \`text/xml\`\ > \ > \- \*\*Response Format\*\*: The response will be in JSON format containing the following fields:\ > \ > \- \`image\`: URL of the player's image.\ > \ > \- \`playerID\`: Unique identifier for the player.\ > \ > \- \`fullName\`: Full name of the player.\ > \ > \- \`nationality\`: Nationality of the player.\ > \ > \- \`nationalityId\`: Identifier for the nationality.\ > \ > \- \`nickName\`: Nickname of the player.\ > \ > \- \`name\`: Name of the player.\ > \ > \- \`teamID\`: Identifier for the team the player belongs to.\ > \ > \- \`birthPlace\`: Place of birth of the player.\ > \ > \- \`dob\`: Date of birth of the player.\ > \ > \- \`battingStyle\`: Style of batting.\ > \ > \- \`bowlingStyle\`: Style of bowling.\ > \ > \- \`role\`: Role of the player in the team.\ > \ > \- \`playerIPLTeam\`: The IPL team the player is associated with.\ > \ > \- \`playerIPLBid\`: The IPL bid amount for the player.\ > \ > \- \`description\`: Additional description of the player.\ > \ > \- \`battingStats\`: Array containing various batting statistics.\ > \ > \- \`bowlingStats\`: Array containing various bowling statistics.\ > \ > \- \`fieldingStats\`: Array containing various fielding statistics.\ > \ > \- \`socialDetails\`: Array containing social media details.\ > \ > \- \`trophyDetails\`: Array containing details about trophies won.\ > \ > \- \`teams\`: Array containing details about the teams the player has been a part of. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Player Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/player/{playerId}":{"get":{"tags":["Player Data API"],"summary":"Player Details","description":"## Get Player Details\n\nThis endpoint retrieves detailed information about a specific cricket player based on their unique player ID.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/player/:playerId`\n \n- **Path Parameter**:\n \n - `playerId` (string): The unique identifier for the player whose details are being requested.\n \n\n### Response\n\n- **Status Code**: `200 OK`\n \n- **Content-Type**: `text/xml`\n \n- **Response Format**: The response will be in JSON format containing the following fields:\n \n - `image`: URL of the player's image.\n \n - `playerID`: Unique identifier for the player.\n \n - `fullName`: Full name of the player.\n \n - `nationality`: Nationality of the player.\n \n - `nationalityId`: Identifier for the nationality.\n \n - `nickName`: Nickname of the player.\n \n - `name`: Name of the player.\n \n - `teamID`: Identifier for the team the player belongs to.\n \n - `birthPlace`: Place of birth of the player.\n \n - `dob`: Date of birth of the player.\n \n - `battingStyle`: Style of batting.\n \n - `bowlingStyle`: Style of bowling.\n \n - `role`: Role of the player in the team.\n \n - `playerIPLTeam`: The IPL team the player is associated with.\n \n - `playerIPLBid`: The IPL bid amount for the player.\n \n - `description`: Additional description of the player.\n \n - `battingStats`: Array containing various batting statistics.\n \n - `bowlingStats`: Array containing various bowling statistics.\n \n - `fieldingStats`: Array containing various fielding statistics.\n \n - `socialDetails`: Array containing social media details.\n \n - `trophyDetails`: Array containing details about trophies won.\n \n - `teams`: Array containing details about the teams the player has been a part of.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"playerId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Player Recent Matches > \# Get Recent Matches for a Player\ > \ > This endpoint retrieves the recent match statistics for a specific cricket player identified by their \`playerId\`. It provides detailed information about matches played across different formats including All, T20, ODI, Test, and T20 Domestic.\ > \ > \## Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`playerId\`: The unique identifier for the player whose recent matches are being queried.\ > \ > \ > \## Response Format\ > \ > The response will be a JSON object containing the following keys:\ > \ > \- \`all\`: An array of objects representing all recent matches.\ > \ > \- \`t20\`: An array of objects representing recent T20 matches.\ > \ > \- \`odi\`: An array of objects representing recent ODI matches.\ > \ > \- \`test\`: An array of objects representing recent Test matches.\ > \ > \- \`t20Domestic\`: An array of objects representing recent T20 Domestic matches.\ > \ > \ > Each match object within these arrays may include the following fields:\ > \ > \- \`homeTeamShortName\`: Short name of the home team.\ > \ > \- \`awayTeamShortName\`: Short name of the away team.\ > \ > \- \`homeTeamID\`: Unique identifier for the home team.\ > \ > \- \`awayTeamID\`: Unique identifier for the away team.\ > \ > \- \`matchDate\`: The date of the match.\ > \ > \- \`matchID\`: Unique identifier for the match.\ > \ > \- \`matchType\`: Type of the match (e.g., T20, ODI).\ > \ > \- \`opposition\`: Name of the opposing team.\ > \ > \- \`battingStats\`: Statistics related to batting performance in the match.\ > \ > \- \`bowlingStats\`: Statistics related to bowling performance in the match.\ > \ > \ > \## Additional Notes\ > \ > \- Ensure that the \`playerId\` is valid to receive accurate match data.\ > \ > \- The response will contain empty strings for fields where data is not available.\ > \ > \- This endpoint is useful for applications that require up-to-date information on player performances in recent matches. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Player Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/player/{playerId}/recent":{"get":{"tags":["Player Data API"],"summary":"Player Recent Matches","description":"# Get Recent Matches for a Player\n\nThis endpoint retrieves the recent match statistics for a specific cricket player identified by their `playerId`. It provides detailed information about matches played across different formats including All, T20, ODI, Test, and T20 Domestic.\n\n## Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/player/:playerId/recent`\n \n- **Path Parameters**:\n \n - `playerId`: The unique identifier for the player whose recent matches are being queried.\n \n\n## Response Format\n\nThe response will be a JSON object containing the following keys:\n\n- `all`: An array of objects representing all recent matches.\n \n- `t20`: An array of objects representing recent T20 matches.\n \n- `odi`: An array of objects representing recent ODI matches.\n \n- `test`: An array of objects representing recent Test matches.\n \n- `t20Domestic`: An array of objects representing recent T20 Domestic matches.\n \n\nEach match object within these arrays may include the following fields:\n\n- `homeTeamShortName`: Short name of the home team.\n \n- `awayTeamShortName`: Short name of the away team.\n \n- `homeTeamID`: Unique identifier for the home team.\n \n- `awayTeamID`: Unique identifier for the away team.\n \n- `matchDate`: The date of the match.\n \n- `matchID`: Unique identifier for the match.\n \n- `matchType`: Type of the match (e.g., T20, ODI).\n \n- `opposition`: Name of the opposing team.\n \n- `battingStats`: Statistics related to batting performance in the match.\n \n- `bowlingStats`: Statistics related to bowling performance in the match.\n \n\n## Additional Notes\n\n- Ensure that the `playerId` is valid to receive accurate match data.\n \n- The response will contain empty strings for fields where data is not available.\n \n- This endpoint is useful for applications that require up-to-date information on player performances in recent matches.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"playerId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Player Fantasy > \## Get Fantasy Matches for a Player\ > \ > This endpoint retrieves fantasy match information for a specific player in various formats including T20, Test, ODI, and T20 Domestic.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \ > \### Path Parameters\ > \ > \- \`playerId\` (string): The unique identifier for the player whose fantasy match details are being requested.\ > \ > \ > \### Response Format\ > \ > The response will be a JSON object containing the following keys:\ > \ > \- \*\*t20\*\*: An array of match objects for T20 matches.\ > \ > \- \*\*test\*\*: An array of match objects for Test matches.\ > \ > \- \*\*odi\*\*: An array of match objects for ODI matches.\ > \ > \- \*\*t20Domestic\*\*: An array of match objects for T20 Domestic matches.\ > \ > \- \*\*all\*\*: An array of match objects for all match types.\ > \ > \ > Each match object includes the following fields:\ > \ > \- \*\*opposition\*\*: The team the player is facing.\ > \ > \- \*\*battingStats\*\*: The player's batting statistics for the match.\ > \ > \- \*\*bowlingStats\*\*: The player's bowling statistics for the match.\ > \ > \- \*\*points\*\*: The fantasy points earned by the player in the match.\ > \ > \- \*\*isDreamTeam\*\*: A boolean indicating if the player is part of the Dream Team for that match.\ > \ > \- \*\*matchType\*\*: The type of match (e.g., T20, Test). ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Player Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/player/{playerId}/fantasy/matches":{"get":{"tags":["Player Data API"],"summary":"Player Fantasy","description":"## Get Fantasy Matches for a Player\n\nThis endpoint retrieves fantasy match information for a specific player in various formats including T20, Test, ODI, and T20 Domestic.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/player/:playerId/fantasy/matches`\n \n\n### Path Parameters\n\n- `playerId` (string): The unique identifier for the player whose fantasy match details are being requested.\n \n\n### Response Format\n\nThe response will be a JSON object containing the following keys:\n\n- **t20**: An array of match objects for T20 matches.\n \n- **test**: An array of match objects for Test matches.\n \n- **odi**: An array of match objects for ODI matches.\n \n- **t20Domestic**: An array of match objects for T20 Domestic matches.\n \n- **all**: An array of match objects for all match types.\n \n\nEach match object includes the following fields:\n\n- **opposition**: The team the player is facing.\n \n- **battingStats**: The player's batting statistics for the match.\n \n- **bowlingStats**: The player's bowling statistics for the match.\n \n- **points**: The fantasy points earned by the player in the match.\n \n- **isDreamTeam**: A boolean indicating if the player is part of the Dream Team for that match.\n \n- **matchType**: The type of match (e.g., T20, Test).","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"playerId","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/player-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.