# Match Details ## Match Details > \## Get Match Details\ > \ > This endpoint retrieves detailed information about a specific football match based on the provided match ID.\ > \ > \### Request Parameters\ > \ > \- \`id\` (path parameter): The unique identifier of the match you wish to retrieve. This parameter is required.\ > \ > \ > \### Response Structure\ > \ > The response will contain the following fields:\ > \ > \- \`matchId\`: The unique identifier for the match.\ > \ > \- \`homeTeam\`: The name of the home team.\ > \ > \- \`awayTeam\`: The name of the away team.\ > \ > \- \`score\`: The current score of the match, including goals scored by both teams.\ > \ > \- \`status\`: The current status of the match (e.g., scheduled, ongoing, finished).\ > \ > \- \`date\`: The date and time when the match is scheduled to take place.\ > \ > \ > Use this endpoint to get the latest details about a specific football match by providing the match ID. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/{id}":{"get":{"tags":["Match Details"],"summary":"Match Details","description":"## Get Match Details\n\nThis endpoint retrieves detailed information about a specific football match based on the provided match ID.\n\n### Request Parameters\n\n- `id` (path parameter): The unique identifier of the match you wish to retrieve. This parameter is required.\n \n\n### Response Structure\n\nThe response will contain the following fields:\n\n- `matchId`: The unique identifier for the match.\n \n- `homeTeam`: The name of the home team.\n \n- `awayTeam`: The name of the away team.\n \n- `score`: The current score of the match, including goals scored by both teams.\n \n- `status`: The current status of the match (e.g., scheduled, ongoing, finished).\n \n- `date`: The date and time when the match is scheduled to take place.\n \n\nUse this endpoint to get the latest details about a specific football match by providing the match ID.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Statistics > \## Get Match Statistics\ > \ > This endpoint retrieves detailed statistics for a specific football match identified by its unique \`id\`. The statistics include various groups of data that provide insights into the match performance.\ > \ > \### Request Parameters\ > \ > \- \`id\` (path parameter): The unique identifier for the match whose statistics are being requested.\ > \ > \ > \### Response Structure\ > \ > On a successful request, the response will include the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the request.\ > \ > \- \*\*message\*\* (string): A message providing additional information about the request status.\ > \ > \- \*\*response\*\* (object): Contains the main data of the response.\ > \ > \- \*\*period\*\* (string): Indicates the period of the match for which statistics are provided.\ > \ > \- \*\*groups\*\* (array): A collection of statistic groups.\ > \ > \- \*\*groupName\*\* (string): The name of the statistic group.\ > \ > \- \*\*statisticsItems\*\* (array): A list of individual statistics items.\ > \ > \- \*\*name\*\* (string): The name of the statistic.\ > \ > \- \*\*home\*\* (string): The home team's statistic value.\ > \ > \- \*\*away\*\* (string): The away team's statistic value.\ > \ > \- \*\*compareCode\*\* (integer): A code used for comparison purposes.\ > \ > \- \*\*statisticsType\*\* (string): The type of statistic being represented.\ > \ > \- \*\*valueType\*\* (string): The type of value (e.g., numerical, percentage).\ > \ > \- \*\*homeValue\*\* (integer): The numerical value for the home team.\ > \ > \- \*\*awayValue\*\* (integer): The numerical value for the away team.\ > \ > \- \*\*renderType\*\* (integer): Indicates how the statistic should be rendered.\ > \ > \- \*\*key\*\* (string): A unique key for the statistic.\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`id\` parameter is valid and corresponds to an existing match to receive accurate statistics.\ > \ > \- The response may vary based on the match data available at the time of the request. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/statistics/{id}":{"get":{"tags":["Match Details"],"summary":"Match Statistics","description":"## Get Match Statistics\n\nThis endpoint retrieves detailed statistics for a specific football match identified by its unique `id`. The statistics include various groups of data that provide insights into the match performance.\n\n### Request Parameters\n\n- `id` (path parameter): The unique identifier for the match whose statistics are being requested.\n \n\n### Response Structure\n\nOn a successful request, the response will include the following structure:\n\n- **status** (boolean): Indicates whether the request was successful.\n \n- **statusCode** (integer): A code representing the status of the request.\n \n- **message** (string): A message providing additional information about the request status.\n \n- **response** (object): Contains the main data of the response.\n \n - **period** (string): Indicates the period of the match for which statistics are provided.\n \n - **groups** (array): A collection of statistic groups.\n \n - **groupName** (string): The name of the statistic group.\n \n - **statisticsItems** (array): A list of individual statistics items.\n \n - **name** (string): The name of the statistic.\n \n - **home** (string): The home team's statistic value.\n \n - **away** (string): The away team's statistic value.\n \n - **compareCode** (integer): A code used for comparison purposes.\n \n - **statisticsType** (string): The type of statistic being represented.\n \n - **valueType** (string): The type of value (e.g., numerical, percentage).\n \n - **homeValue** (integer): The numerical value for the home team.\n \n - **awayValue** (integer): The numerical value for the away team.\n \n - **renderType** (integer): Indicates how the statistic should be rendered.\n \n - **key** (string): A unique key for the statistic.\n \n\n### Notes\n\n- Ensure that the `id` parameter is valid and corresponds to an existing match to receive accurate statistics.\n \n- The response may vary based on the match data available at the time of the request.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Lineups > \### Endpoint Description\ > \ > This endpoint retrieves the lineups for a specific football match identified by the \`:id\` parameter. It provides detailed information about the players and their statistics for both the home and away teams.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier for the match whose lineups are being requested.\ > \ > \ > \### Response\ > \ > The response will return a JSON object with the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates the success of the request.\ > \ > \- \*\*statusCode\*\* (integer): The response status code.\ > \ > \- \*\*message\*\* (string): A message providing additional context about the request.\ > \ > \- \*\*response\*\* (object): Contains detailed lineup information:\ > \ > \- \*\*confirmed\*\* (boolean): Indicates if the lineups are confirmed.\ > \ > \- \*\*home\*\* (object): Information about the home team:\ > \ > \- \*\*players\*\* (array): List of players in the home team, each containing:\ > \ > \- \*\*player\*\* (object): Player details including:\ > \ > \- \*\*name\*\* (string): Player's name.\ > \ > \- \*\*shortName\*\* (string): Player's short name.\ > \ > \- \*\*position\*\* (string): Player's position on the field.\ > \ > \- \*\*jerseyNumber\*\* (string): Jersey number.\ > \ > \- \*\*height\*\* (integer): Player's height.\ > \ > \- \*\*id\*\* (integer): Unique player identifier.\ > \ > \- \*\*country\*\* (object): Player's country information.\ > \ > \- \*\*marketValueCurrency\*\* (string): Currency for market value.\ > \ > \- \*\*dateOfBirthTimestamp\*\* (integer): Player's date of birth as a timestamp.\ > \ > \- \*\*proposedMarketValueRaw\*\* (object): Proposed market value details.\ > \ > \- \*\*teamId\*\* (integer): Identifier for the team.\ > \ > \- \*\*shirtNumber\*\* (integer): Shirt number.\ > \ > \- \*\*substitute\*\* (boolean): Indicates if the player is a substitute.\ > \ > \- \*\*statistics\*\* (object): Player statistics including:\ > \ > \- \*\*totalPass\*\* (integer): Total passes made.\ > \ > \- \*\*accuratePass\*\* (integer): Accurate passes made.\ > \ > \- \*\*totalLongBalls\*\* (integer): Total long balls played.\ > \ > \- \*\*accurateLongBalls\*\* (integer): Accurate long balls played.\ > \ > \- \*\*goodHighClaim\*\* (integer): Good high claims.\ > \ > \- \*\*savedShotsFromInsideTheBox\*\* (integer): Shots saved from inside the box.\ > \ > \- \*\*saves\*\* (integer): Total saves made.\ > \ > \- \*\*minutesPlayed\*\* (integer): Minutes played.\ > \ > \- \*\*touches\*\* (integer): Total touches.\ > \ > \- \*\*rating\*\* (float): Player rating.\ > \ > \- \*\*possessionLostCtrl\*\* (integer): Possessions lost under control.\ > \ > \- \*\*ratingVersions\*\* (object): Different versions of player ratings.\ > \ > \- \*\*goalsPrevented\*\* (integer): Goals prevented by the player.\ > \ > \- \*\*supportStaff\*\* (array): List of support staff for the home team.\ > \ > \- \*\*formation\*\* (string): Team formation.\ > \ > \- \*\*playerColor\*\* (object): Color details for players.\ > \ > \- \*\*goalkeeperColor\*\* (object): Color details for the goalkeeper.\ > \ > \- \*\*away\*\* (object): Similar structure as the home team but for the away team.\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`id\` parameter is valid to receive the correct lineups.\ > \ > \- The response may vary based on the match status and whether the lineups are confirmed. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/lineups/{id}":{"get":{"tags":["Match Details"],"summary":"Match Lineups","description":"### Endpoint Description\n\nThis endpoint retrieves the lineups for a specific football match identified by the `:id` parameter. It provides detailed information about the players and their statistics for both the home and away teams.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/match/lineups/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier for the match whose lineups are being requested.\n \n\n### Response\n\nThe response will return a JSON object with the following structure:\n\n- **status** (boolean): Indicates the success of the request.\n \n- **statusCode** (integer): The response status code.\n \n- **message** (string): A message providing additional context about the request.\n \n- **response** (object): Contains detailed lineup information:\n \n - **confirmed** (boolean): Indicates if the lineups are confirmed.\n \n - **home** (object): Information about the home team:\n \n - **players** (array): List of players in the home team, each containing:\n \n - **player** (object): Player details including:\n \n - **name** (string): Player's name.\n \n - **shortName** (string): Player's short name.\n \n - **position** (string): Player's position on the field.\n \n - **jerseyNumber** (string): Jersey number.\n \n - **height** (integer): Player's height.\n \n - **id** (integer): Unique player identifier.\n \n - **country** (object): Player's country information.\n \n - **marketValueCurrency** (string): Currency for market value.\n \n - **dateOfBirthTimestamp** (integer): Player's date of birth as a timestamp.\n \n - **proposedMarketValueRaw** (object): Proposed market value details.\n \n - **teamId** (integer): Identifier for the team.\n \n - **shirtNumber** (integer): Shirt number.\n \n - **substitute** (boolean): Indicates if the player is a substitute.\n \n - **statistics** (object): Player statistics including:\n \n - **totalPass** (integer): Total passes made.\n \n - **accuratePass** (integer): Accurate passes made.\n \n - **totalLongBalls** (integer): Total long balls played.\n \n - **accurateLongBalls** (integer): Accurate long balls played.\n \n - **goodHighClaim** (integer): Good high claims.\n \n - **savedShotsFromInsideTheBox** (integer): Shots saved from inside the box.\n \n - **saves** (integer): Total saves made.\n \n - **minutesPlayed** (integer): Minutes played.\n \n - **touches** (integer): Total touches.\n \n - **rating** (float): Player rating.\n \n - **possessionLostCtrl** (integer): Possessions lost under control.\n \n - **ratingVersions** (object): Different versions of player ratings.\n \n - **goalsPrevented** (integer): Goals prevented by the player.\n \n - **supportStaff** (array): List of support staff for the home team.\n \n - **formation** (string): Team formation.\n \n - **playerColor** (object): Color details for players.\n \n - **goalkeeperColor** (object): Color details for the goalkeeper.\n \n - **away** (object): Similar structure as the home team but for the away team.\n \n\n### Notes\n\n- Ensure that the `id` parameter is valid to receive the correct lineups.\n \n- The response may vary based on the match status and whether the lineups are confirmed.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Incidents > \## Get Match Incidents\ > \ > This endpoint retrieves incidents related to a specific football match identified by its unique \`id\`. It provides detailed information about various incidents that occurred during the match.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (string): The unique identifier of the match for which incidents are being requested.\ > \ > \ > \### Response\ > \ > The response will return a JSON object containing the following fields:\ > \ > \- \`status\` (boolean): Indicates whether the request was successful.\ > \ > \- \`statusCode\` (integer): The status code of the response.\ > \ > \- \`message\` (string): A message providing additional information about the request status.\ > \ > \- \`response\` (array): An array of incident objects, each containing:\ > \ > \- \`incidentType\` (string): The type of incident (e.g., foul, goal).\ > \ > \- \`incidentClass\` (string): The classification of the incident.\ > \ > \- \`reason\` (string): The reason for the incident.\ > \ > \- \`text\` (string): Additional descriptive text about the incident.\ > \ > \- \`homeScore\` (integer): The score of the home team at the time of the incident.\ > \ > \- \`awayScore\` (integer): The score of the away team at the time of the incident.\ > \ > \- \`time\` (integer): The time in minutes when the incident occurred.\ > \ > \- \`length\` (nullable): The duration of the incident, if applicable.\ > \ > \- \`addedTime\` (integer): The amount of added time for the incident.\ > \ > \- \`reversedPeriodTime\` (integer): The time in the reversed period if applicable.\ > \ > \- \`playerName\` (nullable): The name of the player involved in the incident.\ > \ > \- \`player\` (nullable): An identifier for the player involved in the incident.\ > \ > \- \`isHome\` (nullable): Indicates if the incident involved the home team.\ > \ > \- \`confirmed\` (nullable): Indicates if the incident has been confirmed.\ > \ > \- \`assist1\` (nullable): The first assisting player, if applicable.\ > \ > \- \`assist2\` (nullable): The second assisting player, if applicable.\ > \ > \- \`playerIn\` (nullable): The player who came in, if applicable.\ > \ > \- \`playerOut\` (nullable): The player who went out, if applicable.\ > \ > \- \`injury\` (nullable): Indicates if the incident was related to an injury.\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`id\` parameter is valid and corresponds to an existing match to receive accurate incident data.\ > \ > \- The response may contain multiple incidents, depending on the match events. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/incidents/{id}":{"get":{"tags":["Match Details"],"summary":"Match Incidents","description":"## Get Match Incidents\n\nThis endpoint retrieves incidents related to a specific football match identified by its unique `id`. It provides detailed information about various incidents that occurred during the match.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/match/incidents/:id`\n \n- **Path Parameter**:\n \n - `id` (string): The unique identifier of the match for which incidents are 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): The status code of the response.\n \n- `message` (string): A message providing additional information about the request status.\n \n- `response` (array): An array of incident objects, each containing:\n \n - `incidentType` (string): The type of incident (e.g., foul, goal).\n \n - `incidentClass` (string): The classification of the incident.\n \n - `reason` (string): The reason for the incident.\n \n - `text` (string): Additional descriptive text about the incident.\n \n - `homeScore` (integer): The score of the home team at the time of the incident.\n \n - `awayScore` (integer): The score of the away team at the time of the incident.\n \n - `time` (integer): The time in minutes when the incident occurred.\n \n - `length` (nullable): The duration of the incident, if applicable.\n \n - `addedTime` (integer): The amount of added time for the incident.\n \n - `reversedPeriodTime` (integer): The time in the reversed period if applicable.\n \n - `playerName` (nullable): The name of the player involved in the incident.\n \n - `player` (nullable): An identifier for the player involved in the incident.\n \n - `isHome` (nullable): Indicates if the incident involved the home team.\n \n - `confirmed` (nullable): Indicates if the incident has been confirmed.\n \n - `assist1` (nullable): The first assisting player, if applicable.\n \n - `assist2` (nullable): The second assisting player, if applicable.\n \n - `playerIn` (nullable): The player who came in, if applicable.\n \n - `playerOut` (nullable): The player who went out, if applicable.\n \n - `injury` (nullable): Indicates if the incident was related to an injury.\n \n\n### Notes\n\n- Ensure that the `id` parameter is valid and corresponds to an existing match to receive accurate incident data.\n \n- The response may contain multiple incidents, depending on the match events.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Graphs > \## Get Match Graph Data\ > \ > This endpoint retrieves graph data for a specific football match identified by its unique \`id\`. It provides insights into various metrics related to the match over time.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`id\` (required): The unique identifier for the football match whose graph data is to be retrieved.\ > \ > \ > \### Response\ > \ > The response is a JSON object containing the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the response.\ > \ > \- \*\*message\*\* (string): A message providing additional information about the response.\ > \ > \- \*\*response\*\* (object): Contains the graph data:\ > \ > \- \*\*graphPoints\*\* (array): An array of objects representing data points on the graph. Each object contains:\ > \ > \- \*\*minute\*\* (integer): The minute of the match when the data point was recorded.\ > \ > \- \*\*value\*\* (integer): The value associated with the data point.\ > \ > \- \*\*periodTime\*\* (integer): The total time for the match period in seconds.\ > \ > \- \*\*overtimeLength\*\* (integer): The length of any overtime played in seconds.\ > \ > \- \*\*periodCount\*\* (integer): The number of periods in the match.\ > \ > \ > This endpoint is useful for applications that need to visualize match statistics over time, allowing users to analyze the performance and key moments of the game. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/graphs/{id}":{"get":{"tags":["Match Details"],"summary":"Match Graphs","description":"## Get Match Graph Data\n\nThis endpoint retrieves graph data for a specific football match identified by its unique `id`. It provides insights into various metrics related to the match over time.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/match/graphs/:id`\n \n- **Path Parameters**:\n \n - `id` (required): The unique identifier for the football match whose graph data is to be retrieved.\n \n\n### Response\n\nThe response is a JSON object containing the following structure:\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 information about the response.\n \n- **response** (object): Contains the graph data:\n \n - **graphPoints** (array): An array of objects representing data points on the graph. Each object contains:\n \n - **minute** (integer): The minute of the match when the data point was recorded.\n \n - **value** (integer): The value associated with the data point.\n \n - **periodTime** (integer): The total time for the match period in seconds.\n \n - **overtimeLength** (integer): The length of any overtime played in seconds.\n \n - **periodCount** (integer): The number of periods in the match.\n \n\nThis endpoint is useful for applications that need to visualize match statistics over time, allowing users to analyze the performance and key moments of the game.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Shotmap > \## Endpoint Description\ > \ > This endpoint retrieves the shot map data for a specific match in football based on the provided match ID. The shot map includes detailed information about various shots taken during the match, including player details, shot types, and coordinates.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`id\` (required): The unique identifier of the match for which the shot map is requested.\ > \ > \ > \### Response Structure\ > \ > The response will return a JSON object with the following structure:\ > \ > \- \*\*status\*\*: A boolean indicating the success of the request.\ > \ > \- \*\*statusCode\*\*: An integer representing the status code of the response.\ > \ > \- \*\*message\*\*: A string providing additional information about the response.\ > \ > \- \*\*response\*\*: An array of shot data objects, each containing:\ > \ > \- \*\*player\*\*: An object with details about the player:\ > \ > \- \*\*name\*\*: The name of the player.\ > \ > \- \*\*shortName\*\*: The abbreviated name of the player.\ > \ > \- \*\*position\*\*: The position of the player on the field.\ > \ > \- \*\*jerseyNumber\*\*: The jersey number of the player.\ > \ > \- \*\*id\*\*: The unique identifier of the player.\ > \ > \- \*\*isHome\*\*: A boolean indicating if the player is part of the home team.\ > \ > \- \*\*shotType\*\*: A string describing the type of shot taken.\ > \ > \- \*\*situation\*\*: A string representing the situation during which the shot was taken.\ > \ > \- \*\*playerCoordinates\*\*: An object containing the coordinates (x, y, z) of the player at the time of the shot.\ > \ > \- \*\*bodyPart\*\*: A string indicating which body part was used for the shot.\ > \ > \- \*\*goalMouthLocation\*\*: A string describing the location of the goal mouth.\ > \ > \- \*\*goalMouthCoordinates\*\*: An object containing the coordinates (x, y, z) of the goal mouth.\ > \ > \- \*\*blockCoordinates\*\*: An object containing the coordinates (x, y, z) where the shot was blocked, if applicable.\ > \ > \- \*\*xg\*\*: A float representing the expected goals from the shot.\ > \ > \- \*\*xgot\*\*: A float representing the expected goals on target from the shot.\ > \ > \- \*\*id\*\*: The unique identifier of the shot.\ > \ > \- \*\*time\*\*: An integer representing the time of the shot in the match.\ > \ > \- \*\*timeSeconds\*\*: An integer representing the time of the shot in seconds.\ > \ > \- \*\*draw\*\*: An object containing the coordinates for drawing the shot:\ > \ > \- \*\*start\*\*: The starting coordinates (x, y) of the shot.\ > \ > \- \*\*block\*\*: The coordinates (x, y) where the shot was blocked.\ > \ > \- \*\*end\*\*: The ending coordinates (x, y) of the shot.\ > \ > \- \*\*goal\*\*: The coordinates (x, y) of the goal.\ > \ > \- \*\*reversedPeriodTime\*\*: An integer representing the reversed period time.\ > \ > \- \*\*reversedPeriodTimeSeconds\*\*: An integer representing the reversed period time in seconds.\ > \ > \- \*\*periodTimeSeconds\*\*: An integer representing the period time in seconds.\ > \ > \- \*\*incidentType\*\*: A string describing the type of incident related to the shot.\ > \ > \ > This endpoint is essential for analyzing match performance and player statistics based on shot data. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/shotmap/{id}":{"get":{"tags":["Match Details"],"summary":"Match Shotmap","description":"## Endpoint Description\n\nThis endpoint retrieves the shot map data for a specific match in football based on the provided match ID. The shot map includes detailed information about various shots taken during the match, including player details, shot types, and coordinates.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/match/shotmap/:id`\n \n- **Path Parameters**:\n \n - `id` (required): The unique identifier of the match for which the shot map is requested.\n \n\n### Response Structure\n\nThe response will return a JSON object with the following structure:\n\n- **status**: A boolean indicating the success of the request.\n \n- **statusCode**: An integer representing the status code of the response.\n \n- **message**: A string providing additional information about the response.\n \n- **response**: An array of shot data objects, each containing:\n \n - **player**: An object with details about the player:\n \n - **name**: The name of the player.\n \n - **shortName**: The abbreviated name of the player.\n \n - **position**: The position of the player on the field.\n \n - **jerseyNumber**: The jersey number of the player.\n \n - **id**: The unique identifier of the player.\n \n - **isHome**: A boolean indicating if the player is part of the home team.\n \n - **shotType**: A string describing the type of shot taken.\n \n - **situation**: A string representing the situation during which the shot was taken.\n \n - **playerCoordinates**: An object containing the coordinates (x, y, z) of the player at the time of the shot.\n \n - **bodyPart**: A string indicating which body part was used for the shot.\n \n - **goalMouthLocation**: A string describing the location of the goal mouth.\n \n - **goalMouthCoordinates**: An object containing the coordinates (x, y, z) of the goal mouth.\n \n - **blockCoordinates**: An object containing the coordinates (x, y, z) where the shot was blocked, if applicable.\n \n - **xg**: A float representing the expected goals from the shot.\n \n - **xgot**: A float representing the expected goals on target from the shot.\n \n - **id**: The unique identifier of the shot.\n \n - **time**: An integer representing the time of the shot in the match.\n \n - **timeSeconds**: An integer representing the time of the shot in seconds.\n \n - **draw**: An object containing the coordinates for drawing the shot:\n \n - **start**: The starting coordinates (x, y) of the shot.\n \n - **block**: The coordinates (x, y) where the shot was blocked.\n \n - **end**: The ending coordinates (x, y) of the shot.\n \n - **goal**: The coordinates (x, y) of the goal.\n \n - **reversedPeriodTime**: An integer representing the reversed period time.\n \n - **reversedPeriodTimeSeconds**: An integer representing the reversed period time in seconds.\n \n - **periodTimeSeconds**: An integer representing the period time in seconds.\n \n - **incidentType**: A string describing the type of incident related to the shot.\n \n\nThis endpoint is essential for analyzing match performance and player statistics based on shot data.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Shotmap Player > \### Endpoint Description\ > \ > This endpoint retrieves detailed information about a specific player's shot during a football match. It provides insights into the player's actions, shot characteristics, and relevant coordinates on the field.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \#### Path Parameters\ > \ > \- \`id\` (string): The unique identifier for the match.\ > \ > \- \`player\` (string): The unique identifier for the player whose shot details are being requested.\ > \ > \ > \### Response\ > \ > The response is a JSON object containing the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates the success of the request.\ > \ > \- \*\*statusCode\*\* (integer): The status code of the response.\ > \ > \- \*\*message\*\* (string): A message providing additional context about the response.\ > \ > \- \*\*response\*\* (object): Contains detailed information about the player's shot, including:\ > \ > \- \*\*player\*\* (object): Information about the player:\ > \ > \- \*\*name\*\* (string): The full name of the player.\ > \ > \- \*\*shortName\*\* (string): The short name or nickname of the player.\ > \ > \- \*\*position\*\* (string): The playing position of the player.\ > \ > \- \*\*jerseyNumber\*\* (integer): The jersey number of the player.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the player.\ > \ > \- \*\*isHome\*\* (boolean): Indicates if the player is on the home team.\ > \ > \- \*\*shotType\*\* (string): The type of shot taken (e.g., header, volley).\ > \ > \- \*\*situation\*\* (string): The game situation during the shot (e.g., open play, set piece).\ > \ > \- \*\*playerCoordinates\*\* (object): The coordinates of the player at the time of the shot:\ > \ > \- \*\*x\*\* (number): The x-coordinate.\ > \ > \- \*\*y\*\* (number): The y-coordinate.\ > \ > \- \*\*z\*\* (number): The z-coordinate (height).\ > \ > \- \*\*bodyPart\*\* (string): The body part used to take the shot (e.g., foot, head).\ > \ > \- \*\*goalMouthLocation\*\* (string): The location of the goal mouth relative to the shot.\ > \ > \- \*\*goalMouthCoordinates\*\* (object): The coordinates of the goal mouth:\ > \ > \- \*\*x\*\* (number): The x-coordinate.\ > \ > \- \*\*y\*\* (number): The y-coordinate.\ > \ > \- \*\*z\*\* (number): The z-coordinate.\ > \ > \- \*\*blockCoordinates\*\* (object): Coordinates where the shot may have been blocked:\ > \ > \- \*\*x\*\* (number): The x-coordinate.\ > \ > \- \*\*y\*\* (number): The y-coordinate.\ > \ > \- \*\*z\*\* (number): The z-coordinate.\ > \ > \- \*\*xg\*\* (number): The expected goals value for the shot.\ > \ > \- \*\*xgot\*\* (number): The expected goals on target for the shot.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the shot.\ > \ > \- \*\*time\*\* (integer): The time of the shot in the match.\ > \ > \- \*\*timeSeconds\*\* (integer): The time of the shot in seconds.\ > \ > \- \*\*draw\*\* (object): Contains drawing data for visual representation:\ > \ > \- \*\*start\*\* (object): Starting coordinates of the shot:\ > \ > \- \*\*x\*\* (number): The x-coordinate.\ > \ > \- \*\*y\*\* (number): The y-coordinate.\ > \ > \- \*\*block\*\* (object): Coordinates where the shot was blocked:\ > \ > \- \*\*x\*\* (number): The x-coordinate.\ > \ > \- \*\*y\*\* (number): The y-coordinate.\ > \ > \- \*\*end\*\* (object): Ending coordinates of the shot:\ > \ > \- \*\*x\*\* (number): The x-coordinate.\ > \ > \- \*\*y\*\* (number): The y-coordinate.\ > \ > \- \*\*goal\*\* (object): Coordinates of the goal:\ > \ > \- \*\*x\*\* (number): The x-coordinate.\ > \ > \- \*\*y\*\* (number): The y-coordinate.\ > \ > \- \*\*reversedPeriodTime\*\* (integer): The reversed period time of the shot.\ > \ > \- \*\*reversedPeriodTimeSeconds\*\* (integer): The reversed period time in seconds.\ > \ > \- \*\*periodTimeSeconds\*\* (integer): The period time in seconds.\ > \ > \- \*\*incidentType\*\* (string): The type of incident related to the shot.\ > \ > \ > This endpoint is useful for analyzing player performance and shot effectiveness during matches. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/shotmap/{id}/player/{player}":{"get":{"tags":["Match Details"],"summary":"Match Shotmap Player","description":"### Endpoint Description\n\nThis endpoint retrieves detailed information about a specific player's shot during a football match. It provides insights into the player's actions, shot characteristics, and relevant coordinates on the field.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/match/shotmap/:id/player/:player`\n \n\n#### Path Parameters\n\n- `id` (string): The unique identifier for the match.\n \n- `player` (string): The unique identifier for the player whose shot details are being requested.\n \n\n### Response\n\nThe response is a JSON object containing the following structure:\n\n- **status** (boolean): Indicates the success of the request.\n \n- **statusCode** (integer): The status code of the response.\n \n- **message** (string): A message providing additional context about the response.\n \n- **response** (object): Contains detailed information about the player's shot, including:\n \n - **player** (object): Information about the player:\n \n - **name** (string): The full name of the player.\n \n - **shortName** (string): The short name or nickname of the player.\n \n - **position** (string): The playing position of the player.\n \n - **jerseyNumber** (integer): The jersey number of the player.\n \n - **id** (integer): The unique identifier for the player.\n \n - **isHome** (boolean): Indicates if the player is on the home team.\n \n - **shotType** (string): The type of shot taken (e.g., header, volley).\n \n - **situation** (string): The game situation during the shot (e.g., open play, set piece).\n \n - **playerCoordinates** (object): The coordinates of the player at the time of the shot:\n \n - **x** (number): The x-coordinate.\n \n - **y** (number): The y-coordinate.\n \n - **z** (number): The z-coordinate (height).\n \n - **bodyPart** (string): The body part used to take the shot (e.g., foot, head).\n \n - **goalMouthLocation** (string): The location of the goal mouth relative to the shot.\n \n - **goalMouthCoordinates** (object): The coordinates of the goal mouth:\n \n - **x** (number): The x-coordinate.\n \n - **y** (number): The y-coordinate.\n \n - **z** (number): The z-coordinate.\n \n - **blockCoordinates** (object): Coordinates where the shot may have been blocked:\n \n - **x** (number): The x-coordinate.\n \n - **y** (number): The y-coordinate.\n \n - **z** (number): The z-coordinate.\n \n - **xg** (number): The expected goals value for the shot.\n \n - **xgot** (number): The expected goals on target for the shot.\n \n - **id** (integer): The unique identifier for the shot.\n \n - **time** (integer): The time of the shot in the match.\n \n - **timeSeconds** (integer): The time of the shot in seconds.\n \n - **draw** (object): Contains drawing data for visual representation:\n \n - **start** (object): Starting coordinates of the shot:\n \n - **x** (number): The x-coordinate.\n \n - **y** (number): The y-coordinate.\n \n - **block** (object): Coordinates where the shot was blocked:\n \n - **x** (number): The x-coordinate.\n \n - **y** (number): The y-coordinate.\n \n - **end** (object): Ending coordinates of the shot:\n \n - **x** (number): The x-coordinate.\n \n - **y** (number): The y-coordinate.\n \n - **goal** (object): Coordinates of the goal:\n \n - **x** (number): The x-coordinate.\n \n - **y** (number): The y-coordinate.\n \n - **reversedPeriodTime** (integer): The reversed period time of the shot.\n \n - **reversedPeriodTimeSeconds** (integer): The reversed period time in seconds.\n \n - **periodTimeSeconds** (integer): The period time in seconds.\n \n - **incidentType** (string): The type of incident related to the shot.\n \n\nThis endpoint is useful for analyzing player performance and shot effectiveness during matches.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true},{"name":"player","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Head2Head > \## Endpoint Description\ > \ > This endpoint retrieves head-to-head statistics between two football teams based on the provided match ID. It is useful for analyzing the performance of teams against each other in terms of wins, draws, and losses.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier for the match whose head-to-head statistics are being requested.\ > \ > \ > \### Response\ > \ > The response from this endpoint is a JSON object that contains the following structure:\ > \ > \- \*\*status\*\*: A boolean indicating the success of the request.\ > \ > \- \*\*statusCode\*\*: An integer representing the status code of the response.\ > \ > \- \*\*message\*\*: A string that may contain additional information about the request status.\ > \ > \- \*\*response\*\*: An object containing the detailed head-to-head statistics:\ > \ > \- \*\*teamDuel\*\*: An object representing the duel statistics between the two teams:\ > \ > \- \*\*homeWins\*\*: The number of wins for the home team.\ > \ > \- \*\*awayWins\*\*: The number of wins for the away team.\ > \ > \- \*\*draws\*\*: The number of matches that ended in a draw.\ > \ > \- \*\*managerDuel\*\*: An object representing the duel statistics between the managers of the two teams:\ > \ > \- \*\*homeWins\*\*: The number of wins for the home team's manager.\ > \ > \- \*\*awayWins\*\*: The number of wins for the away team's manager.\ > \ > \- \*\*draws\*\*: The number of matches that ended in a draw between the managers. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/head2head/{id}":{"get":{"tags":["Match Details"],"summary":"Match Head2Head","description":"## Endpoint Description\n\nThis endpoint retrieves head-to-head statistics between two football teams based on the provided match ID. It is useful for analyzing the performance of teams against each other in terms of wins, draws, and losses.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/match/head2head/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier for the match whose head-to-head statistics are being requested.\n \n\n### Response\n\nThe response from this endpoint is a JSON object that contains the following structure:\n\n- **status**: A boolean indicating the success of the request.\n \n- **statusCode**: An integer representing the status code of the response.\n \n- **message**: A string that may contain additional information about the request status.\n \n- **response**: An object containing the detailed head-to-head statistics:\n \n - **teamDuel**: An object representing the duel statistics between the two teams:\n \n - **homeWins**: The number of wins for the home team.\n \n - **awayWins**: The number of wins for the away team.\n \n - **draws**: The number of matches that ended in a draw.\n \n - **managerDuel**: An object representing the duel statistics between the managers of the two teams:\n \n - **homeWins**: The number of wins for the home team's manager.\n \n - **awayWins**: The number of wins for the away team's manager.\n \n - **draws**: The number of matches that ended in a draw between the managers.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Win Probability > \## Get Match Win Probability\ > \ > This endpoint retrieves the win probability statistics for a specific football match identified by its unique \`id\`.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \#### Path Parameters\ > \ > \- \`id\` (string): The unique identifier for the football match. This parameter is required to specify which match's win probability you want to retrieve.\ > \ > \ > \### Response\ > \ > The response will return a JSON object with the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates if the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the response.\ > \ > \- \*\*message\*\* (string): A message providing additional information about the response (if any).\ > \ > \- \*\*response\*\* (object): Contains the win probability data:\ > \ > \- \*\*homeWin\*\* (integer): The probability of the home team winning the match.\ > \ > \- \*\*awayWin\*\* (integer): The probability of the away team winning the match.\ > \ > \- \*\*draw\*\* (integer): The probability of the match ending in a draw.\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`id\` provided corresponds to a valid match to receive accurate win probability data.\ > \ > \- The probabilities returned are represented as integers, which may require conversion to a percentage format for user-friendly display. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/win-probability/{id}":{"get":{"tags":["Match Details"],"summary":"Match Win Probability","description":"## Get Match Win Probability\n\nThis endpoint retrieves the win probability statistics for a specific football match identified by its unique `id`.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/match/win-probability/:id`\n \n\n#### Path Parameters\n\n- `id` (string): The unique identifier for the football match. This parameter is required to specify which match's win probability you want to retrieve.\n \n\n### Response\n\nThe response will return a JSON object with the following structure:\n\n- **status** (boolean): Indicates if the request was successful.\n \n- **statusCode** (integer): A code representing the status of the response.\n \n- **message** (string): A message providing additional information about the response (if any).\n \n- **response** (object): Contains the win probability data:\n \n - **homeWin** (integer): The probability of the home team winning the match.\n \n - **awayWin** (integer): The probability of the away team winning the match.\n \n - **draw** (integer): The probability of the match ending in a draw.\n \n\n### Notes\n\n- Ensure that the `id` provided corresponds to a valid match to receive accurate win probability data.\n \n- The probabilities returned are represented as integers, which may require conversion to a percentage format for user-friendly display.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Teams Form > \### Get Match Teams Form\ > \ > This endpoint retrieves the form details of the teams participating in a specific match identified by the given \`id\`.\ > \ > \*\*Endpoint:\*\* \`GET > \ > \#### Request Parameters\ > \ > \- \`id\` (path parameter): The unique identifier for the match whose teams' form details you want to retrieve.\ > \ > \ > \#### Response Structure\ > \ > 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 request.\ > \ > \- \`message\` (string): A message providing additional information about the request status.\ > \ > \- \`response\` (object): Contains the details of the teams involved in the match:\ > \ > \- \`homeTeam\` (object): Information about the home team.\ > \ > \- \`avgRating\` (string): The average rating of the home team.\ > \ > \- \`position\` (integer): The current position of the home team in the league.\ > \ > \- \`value\` (string): The value of the home team.\ > \ > \- \`form\` (array): An array representing the recent form of the home team.\ > \ > \- \`awayTeam\` (object): Information about the away team.\ > \ > \- \`avgRating\` (string): The average rating of the away team.\ > \ > \- \`position\` (integer): The current position of the away team in the league.\ > \ > \- \`value\` (string): The value of the away team.\ > \ > \- \`form\` (array): An array representing the recent form of the away team.\ > \ > \- \`label\` (string): A label associated with the match.\ > \ > \ > \#### Notes\ > \ > \- Ensure that the \`id\` parameter is valid to receive the correct match details.\ > \ > \- The response provides insights into the teams' performance, which can be useful for analysis or predictions.\ > \ > \ > This endpoint retrieves the form details of the teams participating in a specific match identified by the given \`id\`.\ > \ > \#### Request Parameters\ > \ > \- \`id\` (path parameter): The unique identifier for the match whose teams' form details you want to retrieve.\ > \ > \ > \#### Response Structure\ > \ > 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 request.\ > \ > \- \`message\` (string): A message providing additional information about the request status.\ > \ > \- \`response\` (object): Contains the details of the teams involved in the match:\ > \ > \- \`homeTeam\` (object): Information about the home team.\ > \ > \- \`avgRating\` (string): The average rating of the home team.\ > \ > \- \`position\` (integer): The current position of the home team in the league.\ > \ > \- \`value\` (string): The value of the home team.\ > \ > \- \`form\` (array): An array representing the recent form of the home team.\ > \ > \- \`awayTeam\` (object): Information about the away team.\ > \ > \- \`avgRating\` (string): The average rating of the away team.\ > \ > \- \`position\` (integer): The current position of the away team in the league.\ > \ > \- \`value\` (string): The value of the away team.\ > \ > \- \`form\` (array): An array representing the recent form of the away team.\ > \ > \- \`label\` (string): A label associated with the match.\ > \ > \ > \#### Notes\ > \ > \- Ensure that the \`id\` parameter is valid to receive the correct match details.\ > \ > \- The response provides insights into the teams' performance, which can be useful for analysis or predictions. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/teams-form/{id}":{"get":{"tags":["Match Details"],"summary":"Match Teams Form","description":"### Get Match Teams Form\n\nThis endpoint retrieves the form details of the teams participating in a specific match identified by the given `id`.\n\n**Endpoint:** `GET https://apiv3.sportsapi360.com/football/api/v1/match/teams-form/:id`\n\n#### Request Parameters\n\n- `id` (path parameter): The unique identifier for the match whose teams' form details you want to retrieve.\n \n\n#### Response Structure\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 request.\n \n- `message` (string): A message providing additional information about the request status.\n \n- `response` (object): Contains the details of the teams involved in the match:\n \n - `homeTeam` (object): Information about the home team.\n \n - `avgRating` (string): The average rating of the home team.\n \n - `position` (integer): The current position of the home team in the league.\n \n - `value` (string): The value of the home team.\n \n - `form` (array): An array representing the recent form of the home team.\n \n - `awayTeam` (object): Information about the away team.\n \n - `avgRating` (string): The average rating of the away team.\n \n - `position` (integer): The current position of the away team in the league.\n \n - `value` (string): The value of the away team.\n \n - `form` (array): An array representing the recent form of the away team.\n \n - `label` (string): A label associated with the match.\n \n\n#### Notes\n\n- Ensure that the `id` parameter is valid to receive the correct match details.\n \n- The response provides insights into the teams' performance, which can be useful for analysis or predictions.\n \n\nThis endpoint retrieves the form details of the teams participating in a specific match identified by the given `id`.\n\n#### Request Parameters\n\n- `id` (path parameter): The unique identifier for the match whose teams' form details you want to retrieve.\n \n\n#### Response Structure\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 request.\n \n- `message` (string): A message providing additional information about the request status.\n \n- `response` (object): Contains the details of the teams involved in the match:\n \n - `homeTeam` (object): Information about the home team.\n \n - `avgRating` (string): The average rating of the home team.\n \n - `position` (integer): The current position of the home team in the league.\n \n - `value` (string): The value of the home team.\n \n - `form` (array): An array representing the recent form of the home team.\n \n - `awayTeam` (object): Information about the away team.\n \n - `avgRating` (string): The average rating of the away team.\n \n - `position` (integer): The current position of the away team in the league.\n \n - `value` (string): The value of the away team.\n \n - `form` (array): An array representing the recent form of the away team.\n \n - `label` (string): A label associated with the match.\n \n\n#### Notes\n\n- Ensure that the `id` parameter is valid to receive the correct match details.\n \n- The response provides insights into the teams' performance, which can be useful for analysis or predictions.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Managers > \## Get Match Manager Details\ > \ > This endpoint retrieves details about a specific match manager based on their unique identifier.\ > \ > \### Request Method\ > \ > \- \*\*GET\*\*: This method is used to request data from the specified resource.\ > \ > \ > \### Endpoint\ > \ > \- \` > \ > \ > \### Request Parameters\ > \ > \- \`id\` (path parameter): The unique identifier of the match manager. This parameter is required to specify which manager's details are being requested.\ > \ > \ > \### Expected Response Format\ > \ > The response will be in JSON format and will contain the following fields:\ > \ > \- \`status\`: A boolean indicating the success of the request.\ > \ > \- \`statusCode\`: A numerical code representing the status of the request.\ > \ > \- \`message\`: A string that may contain additional information about the request.\ > \ > \- \`response\`: An object containing details of the match managers:\ > \ > \- \`homeManager\`: An object with details about the home manager:\ > \ > \- \`name\`: The name of the home manager.\ > \ > \- \`shortName\`: The short name of the home manager.\ > \ > \- \`id\`: The unique identifier of the home manager.\ > \ > \- \`awayManager\`: An object with details about the away manager:\ > \ > \- \`name\`: The name of the away manager.\ > \ > \- \`shortName\`: The short name of the away manager.\ > \ > \- \`id\`: The unique identifier of the away manager.\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`id\` parameter is valid and corresponds to an existing match manager in the system.\ > \ > \- The response will return a \`200\` status code upon successful retrieval of the manager's details. In case of an invalid \`id\`, a \`404\` status code will be returned. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/managers/{id}":{"get":{"tags":["Match Details"],"summary":"Match Managers","description":"## Get Match Manager Details\n\nThis endpoint retrieves details about a specific match manager based on their unique identifier.\n\n### Request Method\n\n- **GET**: This method is used to request data from the specified resource.\n \n\n### Endpoint\n\n- `https://apiv3.sportsapi360.com/football/api/v1/match/managers/:id`\n \n\n### Request Parameters\n\n- `id` (path parameter): The unique identifier of the match manager. This parameter is required to specify which manager's details are being requested.\n \n\n### Expected Response Format\n\nThe response will be in JSON format and will contain the following fields:\n\n- `status`: A boolean indicating the success of the request.\n \n- `statusCode`: A numerical code representing the status of the request.\n \n- `message`: A string that may contain additional information about the request.\n \n- `response`: An object containing details of the match managers:\n \n - `homeManager`: An object with details about the home manager:\n \n - `name`: The name of the home manager.\n \n - `shortName`: The short name of the home manager.\n \n - `id`: The unique identifier of the home manager.\n \n - `awayManager`: An object with details about the away manager:\n \n - `name`: The name of the away manager.\n \n - `shortName`: The short name of the away manager.\n \n - `id`: The unique identifier of the away manager.\n \n\n### Notes\n\n- Ensure that the `id` parameter is valid and corresponds to an existing match manager in the system.\n \n- The response will return a `200` status code upon successful retrieval of the manager's details. In case of an invalid `id`, a `404` status code will be returned.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Best Players > \# Get Best Players for a Match\ > \ > This endpoint retrieves the best players from both home and away teams for a specific match identified by the provided \`id\`. It also includes the player of the match in the response.\ > \ > \## Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*Endpoint:\*\* \` > \ > \- \*\*Path Parameter:\*\*\ > \ > \- \`id\` (required): The unique identifier of the match for which the best players are being requested.\ > \ > \ > \## Response\ > \ > The response will be a JSON object containing the following fields:\ > \ > \- \`status\` (boolean): Indicates the success of the request.\ > \ > \- \`statusCode\` (integer): A code representing the status of the response.\ > \ > \- \`message\` (string): A message providing additional information about the response.\ > \ > \- \`response\` (object): Contains details about the best players:\ > \ > \- \`bestHomeTeamPlayers\` (array): A list of players from the home team, each represented by:\ > \ > \- \`value\` (string): The value associated with the player.\ > \ > \- \`label\` (string): The label for the player.\ > \ > \- \`player\` (object): Contains player details:\ > \ > \- \`name\` (string): The full name of the player.\ > \ > \- \`shortName\` (string): The abbreviated name of the player.\ > \ > \- \`position\` (string): The playing position of the player.\ > \ > \- \`jerseyNumber\` (integer): The jersey number of the player.\ > \ > \- \`height\` (integer): The height of the player in centimeters.\ > \ > \- \`id\` (integer): The unique identifier of the player.\ > \ > \- \`marketValueCurrency\` (string): The currency of the player's market value.\ > \ > \- \`dateOfBirthTimestamp\` (integer): The timestamp of the player's date of birth.\ > \ > \- \`proposedMarketValueRaw\` (object): Contains:\ > \ > \- \`value\` (integer): The proposed market value of the player.\ > \ > \- \`currency\` (string): The currency of the proposed market value.\ > \ > \- \`bestAwayTeamPlayers\` (array): A list of players from the away team with the same structure as \`bestHomeTeamPlayers\`.\ > \ > \- \`playerOfTheMatch\` (object): The player recognized as the player of the match, structured similarly to the players in the lists above.\ > \ > \ > This endpoint provides a comprehensive overview of the top-performing players in a match, facilitating insights into player performance. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/best-players/{id}":{"get":{"tags":["Match Details"],"summary":"Match Best Players","description":"# Get Best Players for a Match\n\nThis endpoint retrieves the best players from both home and away teams for a specific match identified by the provided `id`. It also includes the player of the match in the response.\n\n## Request\n\n- **Method:** GET\n \n- **Endpoint:** `https://apiv3.sportsapi360.com/football/api/v1/match/best-players/:id`\n \n- **Path Parameter:**\n \n - `id` (required): The unique identifier of the match for which the best players are being requested.\n \n\n## Response\n\nThe response will be a JSON object containing the following fields:\n\n- `status` (boolean): Indicates the success of the request.\n \n- `statusCode` (integer): A code representing the status of the response.\n \n- `message` (string): A message providing additional information about the response.\n \n- `response` (object): Contains details about the best players:\n \n - `bestHomeTeamPlayers` (array): A list of players from the home team, each represented by:\n \n - `value` (string): The value associated with the player.\n \n - `label` (string): The label for the player.\n \n - `player` (object): Contains player details:\n \n - `name` (string): The full name of the player.\n \n - `shortName` (string): The abbreviated name of the player.\n \n - `position` (string): The playing position of the player.\n \n - `jerseyNumber` (integer): The jersey number of the player.\n \n - `height` (integer): The height of the player in centimeters.\n \n - `id` (integer): The unique identifier of the player.\n \n - `marketValueCurrency` (string): The currency of the player's market value.\n \n - `dateOfBirthTimestamp` (integer): The timestamp of the player's date of birth.\n \n - `proposedMarketValueRaw` (object): Contains:\n \n - `value` (integer): The proposed market value of the player.\n \n - `currency` (string): The currency of the proposed market value.\n \n - `bestAwayTeamPlayers` (array): A list of players from the away team with the same structure as `bestHomeTeamPlayers`.\n \n - `playerOfTheMatch` (object): The player recognized as the player of the match, structured similarly to the players in the lists above.\n \n\nThis endpoint provides a comprehensive overview of the top-performing players in a match, facilitating insights into player performance.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Featured Player > \### Endpoint Description\ > \ > This endpoint retrieves featured player information for a specific football match identified by the \`id\` parameter. It provides details about the best players from both home and away teams, as well as the player of the match.\ > \ > \### Request Format\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\`: The unique identifier for the match (required).\ > \ > \ > \### Response Format\ > \ > The response will be in JSON format and includes the following structure:\ > \ > \- \*\*status\*\*: A boolean indicating the success of the request.\ > \ > \- \*\*statusCode\*\*: An integer representing the status code of the response.\ > \ > \- \*\*message\*\*: A string that may contain additional information about the response.\ > \ > \- \*\*response\*\*: An object containing:\ > \ > \- \*\*bestHomeTeamPlayers\*\*: An array of objects representing the best players from the home team. Each object includes:\ > \ > \- \*\*value\*\*: A string representing the player's value.\ > \ > \- \*\*label\*\*: A string representing the player's label.\ > \ > \- \*\*player\*\*: An object with player details including:\ > \ > \- \*\*name\*\*: The player's name.\ > \ > \- \*\*shortName\*\*: The player's short name.\ > \ > \- \*\*position\*\*: The player's position on the field.\ > \ > \- \*\*jerseyNumber\*\*: The player's jersey number.\ > \ > \- \*\*height\*\*: The player's height.\ > \ > \- \*\*id\*\*: The player's unique identifier.\ > \ > \- \*\*marketValueCurrency\*\*: The currency of the player's market value.\ > \ > \- \*\*dateOfBirthTimestamp\*\*: The player's date of birth in timestamp format.\ > \ > \- \*\*proposedMarketValueRaw\*\*: An object containing:\ > \ > \- \*\*value\*\*: The proposed market value.\ > \ > \- \*\*currency\*\*: The currency of the proposed market value.\ > \ > \- \*\*bestAwayTeamPlayers\*\*: Similar structure as \`bestHomeTeamPlayers\` for the away team.\ > \ > \- \*\*playerOfTheMatch\*\*: An object representing the player of the match, with the same structure as the players in the best players arrays. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/featured-player/{id}":{"get":{"tags":["Match Details"],"summary":"Match Featured Player","description":"### Endpoint Description\n\nThis endpoint retrieves featured player information for a specific football match identified by the `id` parameter. It provides details about the best players from both home and away teams, as well as the player of the match.\n\n### Request Format\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/match/featured-player/:id`\n \n- **Path Parameter**:\n \n - `id`: The unique identifier for the match (required).\n \n\n### Response Format\n\nThe response will be in JSON format and includes the following structure:\n\n- **status**: A boolean indicating the success of the request.\n \n- **statusCode**: An integer representing the status code of the response.\n \n- **message**: A string that may contain additional information about the response.\n \n- **response**: An object containing:\n \n - **bestHomeTeamPlayers**: An array of objects representing the best players from the home team. Each object includes:\n \n - **value**: A string representing the player's value.\n \n - **label**: A string representing the player's label.\n \n - **player**: An object with player details including:\n \n - **name**: The player's name.\n \n - **shortName**: The player's short name.\n \n - **position**: The player's position on the field.\n \n - **jerseyNumber**: The player's jersey number.\n \n - **height**: The player's height.\n \n - **id**: The player's unique identifier.\n \n - **marketValueCurrency**: The currency of the player's market value.\n \n - **dateOfBirthTimestamp**: The player's date of birth in timestamp format.\n \n - **proposedMarketValueRaw**: An object containing:\n \n - **value**: The proposed market value.\n \n - **currency**: The currency of the proposed market value.\n \n - **bestAwayTeamPlayers**: Similar structure as `bestHomeTeamPlayers` for the away team.\n \n - **playerOfTheMatch**: An object representing the player of the match, with the same structure as the players in the best players arrays.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Match Commentary > \# Get Match Commentary\ > \ > This endpoint retrieves live commentary for a specific football match identified by its unique \`id\`. It allows users to access real-time updates and insights during the match.\ > \ > \## Request Method\ > \ > \`GET\`\ > \ > \## Endpoint\ > \ > \` > \ > \## Parameters\ > \ > \- \`id\` (path parameter): The unique identifier of the match for which commentary is being requested. This should be a valid match ID.\ > \ > \ > \### Response Fields\ > \ > \- \`status\`: A boolean indicating the success of the request.\ > \ > \- \`statusCode\`: A numeric code representing the status of the response.\ > \ > \- \`message\`: A string that may contain additional information about the response.\ > \ > \- \`response\`: An array of commentary objects, each containing:\ > \ > \- \`text\`: The commentary text.\ > \ > \- \`type\`: The type of commentary (e.g., goal, foul).\ > \ > \- \`id\`: The unique identifier of the commentary entry.\ > \ > \- \`time\`: The time in the match when the commentary occurred.\ > \ > \ > \## Additional Notes\ > \ > \- Ensure that the \`id\` parameter is valid and corresponds to an ongoing match to receive meaningful commentary.\ > \ > \- The response may vary based on the match's progress and the availability of commentary updates. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Match Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/match/commentary/{id}":{"get":{"tags":["Match Details"],"summary":"Match Commentary","description":"# Get Match Commentary\n\nThis endpoint retrieves live commentary for a specific football match identified by its unique `id`. It allows users to access real-time updates and insights during the match.\n\n## Request Method\n\n`GET`\n\n## Endpoint\n\n`https://apiv3.sportsapi360.com/football/api/v1/match/commentary/:id`\n\n## Parameters\n\n- `id` (path parameter): The unique identifier of the match for which commentary is being requested. This should be a valid match ID.\n \n\n### Response Fields\n\n- `status`: A boolean indicating the success of the request.\n \n- `statusCode`: A numeric code representing the status of the response.\n \n- `message`: A string that may contain additional information about the response.\n \n- `response`: An array of commentary objects, each containing:\n \n - `text`: The commentary text.\n \n - `type`: The type of commentary (e.g., goal, foul).\n \n - `id`: The unique identifier of the commentary entry.\n \n - `time`: The time in the match when the commentary occurred.\n \n\n## Additional Notes\n\n- Ensure that the `id` parameter is valid and corresponds to an ongoing match to receive meaningful commentary.\n \n- The response may vary based on the match's progress and the availability of commentary updates.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` --- # 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/football-docs/api-collection-football/match-details.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.