# Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation This site has an agentic ask interface you may use to query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docsv3.sportsapi360.com/index.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. --- # Welcome Welcome to the SportsAPI360 API documentation. We'll briefly inform you about the features of our API and then you can explore our documentation for yourself. SportsAPI360 is a comprehensive sports data provider offering real-time and historical data for football and cricket, tailored for developers and businesses aiming to build sports applications. #### Key Features * **Real-Time Updates**: Access live scores, statistics, and play-by-play updates with minimal latency for major events. * **Historical Data**: Retrieve extensive historical data for teams, players, and competitions to support in-depth analysis. * **Global Coverage**: Data spans over 100 leagues and tournaments worldwide, including prominent football leagues like the Premier League, La Liga, Bundesliga, Serie A, Ligue 1, and the Champions League. * **Developer-Friendly API**: Offers a well-documented RESTful API with SDKs for popular programming languages, facilitating quick and easy integration. * **Reliability and Security**: Ensures 99.9% uptime with enterprise-grade security measures. * **Affordable Pricing**: Provides a free plan with 500 API calls per month, covering all matches, countries, leagues, and fixtures, making it accessible for developers and small businesses. #### API Access and Documentation Developers can access the API by registering and obtaining an API key. The API supports endpoints for both football and cricket data, with a rate limit of 100 requests per minute and an average response time of approximately 120 milliseconds. Comprehensive documentation is available to guide users through the integration and usage process. For more information or to get started, visit the [SportsAPI360 website](https://sportsapi360.com/). # Getting Started Welcome aboard! This section will guide you through the steps to quickly start using **SportsAPI360’s powerful sports data APIs**. Whether you're building an app for live cricket scores, a football results tracker, or a sports analytics dashboard, we make it easy for you to integrate real-time and historical data. #### ✅ Step 1: Sign Up Go to [sportsapi360.com](https://sportsapi360.com/) and create a free developer account.\ You'll get access to your dashboard, where you can manage your subscription, usage, and API keys. *** #### 🔐 Step 2: Get Your API Key Once logged in, go to your **Dashboard > App > API Key** section.\ This unique key identifies your account and must be included in all API requests. * Your key looks like this: `api_key=YOUR_API_KEY_HERE` * Keep it secure and don’t expose it in the frontend code. {% hint style="info" %} The Api Key has no expiration date and will remain valid until you manually delete it yourself. {% endhint %} *** #### 📦 Step 3: Choose a Subscription Plan We offer flexible pricing plans for developers, startups, and enterprises. Visit the Pricing Page for full details. *** API utilizes response codes to indicate successful and failed API requests. When making a request, a code response will always be returned. See below for a short list of possible code responses: | | | | ----- | ---------------------------------------------------------------------------------------------------------------------- | | `200` | Successful request and data was returned | | `400` | Part of the request is malformed; the exact reason can be found in the response | | `401` | The request is not authenticated | | `403` | Unauthorized request to access data from an ineligible plan | | `404` | This recond is not found. It could be that the data you're trying to access is deleted due to rescheduling. | | `429` | You have reached the response rate limit of your plan | | `500` | Internal error with our servers | # API Collection Welcome to the **SportsAPI360 API Collection**. Below is a categorized list of available endpoints for **Cricket** and **Football**. Each API is designed to deliver real-time and historical data with high accuracy and speed.
Cricket APIGet comprehensive and live cricket data with highly granular endpoints. Ideal for score updates, commentary, fantasy gaming, and analytics.Cricket APIScreenshot 2025-06-03 151739.png
Football ApiAccess comprehensive data for football leagues and tournaments worldwide, including live scores, statistics, and historical data.Football APIScreenshot 2025-06-03 151922.png
UPCOMING..!1720520339561.jpg
# Welcome Welcome to the SportsAPI360 API documentation. We'll briefly inform you about the features of our API and then you can explore our documentation for yourself. SportsAPI360 is a comprehensive sports data provider offering real-time and historical data for football and cricket, tailored for developers and businesses aiming to build sports applications. #### Key Features * **Real-Time Updates**: Access live scores, statistics, and play-by-play updates with minimal latency for major events. * **Historical Data**: Retrieve extensive historical data for teams, players, and competitions to support in-depth analysis. * **Global Coverage**: Data spans over 100 leagues and tournaments worldwide, including prominent football leagues like the Premier League, La Liga, Bundesliga, Serie A, Ligue 1, and the Champions League. * **Developer-Friendly API**: Offers a well-documented RESTful API with SDKs for popular programming languages, facilitating quick and easy integration. * **Reliability and Security**: Ensures 99.9% uptime with enterprise-grade security measures. * **Affordable Pricing**: Provides a free plan with 500 API calls per month, covering all matches, countries, leagues, and fixtures, making it accessible for developers and small businesses. #### API Access and Documentation Developers can access the API by registering and obtaining an API key. The API supports endpoints for both football and cricket data, with a rate limit of 100 requests per minute and an average response time of approximately 120 milliseconds. Comprehensive documentation is available to guide users through the integration and usage process. For more information or to get started, visit the [SportsAPI360 website](https://sportsapi360.com/). {% hint style="info" %} Please note that our entire Cricket API collection with all endpoints is available in Postman. [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://cricket-postman.sportsapi360.com/) {% endhint %} # Getting Started Welcome aboard! This section will guide you through the steps to quickly start using **SportsAPI360’s powerful sports data APIs**. Whether you're building an app for live cricket scores, a football results tracker, or a sports analytics dashboard, we make it easy for you to integrate real-time and historical data. #### ✅ Step 1: Sign Up Go to [sportsapi360.com](https://sportsapi360.com/) and create a free developer account.\ You'll get access to your dashboard, where you can manage your subscription, usage, and API keys. *** #### 🔐 Step 2: Get Your API Key Once logged in, go to your **Dashboard > App > API Key** section.\ This unique key identifies your account and must be included in all API requests. * Your key looks like this: `api_key=YOUR_API_KEY_HERE` * Keep it secure and don’t expose it in the frontend code. {% hint style="info" %} The Api Key has no expiration date and will remain valid until you manually delete it yourself. {% endhint %} *** #### 📦 Step 3: Choose a Subscription Plan We offer flexible pricing plans for developers, startups, and enterprises: * **Free Trial**: Perfect for testing and learning * **Developer Plan**: Ideal for indie projects or MVPs * **Pro & Business Plans**: High request limits, commercial rights, and priority support Visit the Pricing Page for full details. *** API utilizes response codes to indicate successful and failed API requests. When making a request, a code response will always be returned. See below for a short list of possible code responses: | | | | ----- | ---------------------------------------------------------------------------------------------------------------------- | | `200` | Successful request and data was returned | | `400` | Part of the request is malformed; the exact reason can be found in the response | | `401` | The request is not authenticated | | `403` | Unauthorized request to access data from an ineligible plan | | `404` | This recond is not found. It could be that the data you're trying to access is deleted due to rescheduling. | | `429` | You have reached the response rate limit of your plan | | `500` | Internal error with our servers | {% hint style="info" %} We recommend you use Postman for convenience. Every endpoint has an example request ready to be requested by you. Hit the button below to import our API collection. \ \ [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://cricket-postman.sportmonks.com/) {% endhint %} # API Collection Welcome to the **SportsAPI360 API Collection**. Below is a categorized list of available endpoints for **Cricket** and **Football**. Each API is designed to deliver real-time and historical data with high accuracy and speed.
Cricket APIGet comprehensive and live cricket data with highly granular endpoints. Ideal for score updates, commentary, fantasy gaming, and analytics.Screenshot 2025-06-03 151739.png
Football APIAccess comprehensive data for football leagues and tournaments worldwide, including live scores, statistics, and historical data.Screenshot 2025-06-03 151922.png
UPCOMING..!1720520339561.jpg
# Build the request Now that all prerequisites have been fulfilled, we’re ready to send our first request to the API! ## Cricket API The request consists of the following components: * The base URL * A path parameter, in this example, we use \[series] * A query string parameter, which is optional, so we leave this out for now * And finally, your API key {% tabs %} {% tab title="Base URL" %} {% code overflow="wrap" %} ```mathml https://apiv3.sportsapi360.com/ ``` {% endcode %} {% endtab %} {% endtabs %} {% tabs %} {% tab title="Base Endpoints" %} {% code overflow="wrap" %} ```mathml https://apiv3.sportsapi360.com/cricket/api/v2/ ``` {% endcode %} {% endtab %} {% endtabs %} An example of a correctly authenticated request would be: {% tabs %} {% tab title="Request" %} {% code overflow="wrap" %} ```mathml curl --location 'https://apiv3.sportsapi360.com/cricket/api/v2/series?filter=live' \ --header 'x-app-key: {{ your api key }}' ``` {% endcode %} {% endtab %} {% tab title="Response" %} ``` [{ "tourName": "Indian Premier League, 2025", "seriesSearchNameForES": "Indian Premier League, 2025, March, Mar", "tourID": "7126", "league": "IPL", "seriesStartDate": "1742652000000", "seriesEndDate": "1748979000000", "T20count": 79, "matchLevel": "domestic", "Odicount": null, "Testcount": null, "seriesStatus": "live" }, { "tourName": "ICC CWC League 2, 2023-27", "seriesSearchNameForES": "ICC CWC League 2, 2023-27, February, Feb", "tourID": "4689", "league": "ICC", "seriesStartDate": "1707968700000", "seriesEndDate": "1749742200000", "T20count": null, "matchLevel": "international", "Odicount": 79, "Testcount": null, "seriesStatus": "live" }, { "tourName": "West Indies Women tour of England, 2025", "seriesSearchNameForES": "West Indies Women tour of England, 2025, May, May", "tourID": "6986", "league": "Women's International", "seriesStartDate": "1747848600000", "seriesEndDate": "1749310200000", "T20count": 3, "matchLevel": "international-womens", "Odicount": 3, "Testcount": null, "seriesStatus": "live" }] ``` {% endtab %} {% endtabs %} This request will return all of the leagues. {% hint style="info" %} Please note that our entire Cricket API collection with all endpoints is available in Postman. [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://cricket-postman.sportsapi360.com/) {% endhint %} # All endpoints On this page you can find an overview of all the endpoints. {% hint style="info" %} Please note that our entire Cricket API collection with all endpoints is available in Postman. [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://cricket-postman.sportsapi360.com/) {% endhint %}
MethodPath
GET/cricket/api/v3/match/schedule
GET/cricket/api/v3/series
GET/cricket/api/v2/match/featured
GET/cricket/api/v2/match/schedule
GET/cricket/api/v2/match/:matchId/live
GET/cricket/api/v2/match/:matchId/details
GET/cricket/api/v2/match/:matchId/scoreboard
GET/cricket/api/v2/match/:matchId/graph
GET/cricket/api/v2/match/:matchId/last12balls
GET/cricket/api/v2/match/:matchId/highlights
GET/cricket/api/v2/match/:matchId/team-records
GET/cricket/api/v2/match/:matchId/winning-percentage
GET/cricket/api/v2/match/:matchId/team-head2head
GET/cricket/api/v2/match/:matchId/team-last-five
GET/cricket/api/v2/match/:matchId/summery
GET/cricket/api/v2/match/:matchId/team-analysis
GET/cricket/api/v2/match/:matchId/top-pick
GET/cricket/api/v2/match/:matchId/stadiumv2
GET/cricket/api/v2/match/:matchId/player-record
GET/cricket/api/v2/match/:matchId/commentary
GET/cricket/api/v2/match/:matchId/commentary/ballByBall
GET/cricket/api/v2/series
GET/cricket/api/v2/series/:seriesID/matches
GET/cricket/api/v2/series/:seriesID/point-table
GET/cricket/api/v2/series/:seriesID/squads
GET/cricket/api/v2/series/:seriesID/statics
GET/cricket/api/v2/series/:seriesID/stadiums
GET/cricket/api/v2/player/:id
GET/cricket/api/v2/player/:id/recent
GET/cricket/api/v2/player/:id/fantasy/matches
GET/cricket/api/v2/search/player
GET/cricket/api/v2/search/team
GET/cricket/api/v2/team/info/:id
GET/cricket/api/v2/team/:id
GET/cricket/api/v2/team/:id/recent
GET/cricket/api/v2/team/:id/schedule
GET/cricket/api/v2/team/:id/stats
GET/cricket/api/v2/team/:id/squads
GET/cricket/api/v2/ranking/men
GET/cricket/api/v2/ranking/women
GET/cricket/api/v2/ranking/team
GET/cricket/api/v2/stadium/:id
# Introduction to API Now that all prerequisites have been fulfilled, we’re ready to send our first request to the API! Before you are able to call our API, you need a SportMonks account. [Register now.](https://sportsapi360.com/register) To make our first request, we’ll need a way to get authenticated first. Cricket API 2.0 utilizes API tokens for the authentication of requests. You can obtain and manage your API key in the [SportsAPI360](https://sportsapi360.com/login). Example API key: \[HdoiD312ND….] The API key is only meant for your eyes and, as such, should be stored away safely. {% hint style="danger" %} API key has no expiration date and will remain valid until you manually delete it yourself. {% endhint %} ## Cricket API The request consists of the following components: * The base URL * A path parameter, in this example, we use \[series] * A query string parameter, which is optional, so we leave this out for now * And finally, your API key {% tabs %} {% tab title="Base URL" %} {% code overflow="wrap" %} ```mathml https://apiv3.sportsapi360.com/cricket/api/v2 ``` {% endcode %} {% endtab %} {% endtabs %} An example of a correctly authenticated request would be: {% tabs %} {% tab title="Request" %} {% code overflow="wrap" %} ```mathml curl --location 'https://apiv3.sportsapi360.com/cricket/api/v2/series?filter=live' \ --header 'x-app-key: {{ your api key }}' ``` {% endcode %} {% endtab %} {% tab title="Response" %} ``` [{ "tourName": "Indian Premier League, 2025", "seriesSearchNameForES": "Indian Premier League, 2025, March, Mar", "tourID": "7126", "league": "IPL", "seriesStartDate": "1742652000000", "seriesEndDate": "1748979000000", "T20count": 79, "matchLevel": "domestic", "Odicount": null, "Testcount": null, "seriesStatus": "live" }, { "tourName": "ICC CWC League 2, 2023-27", "seriesSearchNameForES": "ICC CWC League 2, 2023-27, February, Feb", "tourID": "4689", "league": "ICC", "seriesStartDate": "1707968700000", "seriesEndDate": "1749742200000", "T20count": null, "matchLevel": "international", "Odicount": 79, "Testcount": null, "seriesStatus": "live" }, { "tourName": "West Indies Women tour of England, 2025", "seriesSearchNameForES": "West Indies Women tour of England, 2025, May, May", "tourID": "6986", "league": "Women's International", "seriesStartDate": "1747848600000", "seriesEndDate": "1749310200000", "T20count": 3, "matchLevel": "international-womens", "Odicount": 3, "Testcount": null, "seriesStatus": "live" }] ``` {% endtab %} {% endtabs %} {% hint style="info" %} We recommend you use Postman for convenience. Every endpoint has an example request ready for you to use. Hit the button below to import our Cricket API collection. [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://cricket-postman.sportsapi360.com/) {% endhint %} # Matches List API ## Match Schedule (v3) > \### Get Cricket Match Schedule\ > \ > This endpoint makes an HTTP GET request to retrieve the schedule of cricket matches.\ > \ > \#### Request\ > \ > \- Endpoint: \` > \ > \- Query Parameters:\ > \ > \- type (string, required): Type of matches to retrieve (e.g. All)\ > \ > \- page (integer, required): Page number for pagination (e.g. 0)\ > \ > \ > \#### Response\ > \ > \- Status: 200\ > \ > \- Content-Type: application/json\ > \ > \- Body:\ > \ > \- An array of objects, each containing match details such as match ID, date, series ID, teams, match status, venue, match result, player of the match, match score, and more. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Matches List API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v3/match/schedule":{"get":{"tags":["Matches List API"],"summary":"Match Schedule (v3)","description":"### Get Cricket Match Schedule\n\nThis endpoint makes an HTTP GET request to retrieve the schedule of cricket matches.\n\n#### Request\n\n- Endpoint: `https://apiv3.sportsapi360.com/cricket/api/v3/match/schedule`\n \n- Query Parameters:\n \n - type (string, required): Type of matches to retrieve (e.g. All)\n \n - page (integer, required): Page number for pagination (e.g. 0)\n \n\n#### Response\n\n- Status: 200\n \n- Content-Type: application/json\n \n- Body:\n \n - An array of objects, each containing match details such as match ID, date, series ID, teams, match status, venue, match result, player of the match, match score, and more.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"type","in":"query","schema":{"type":"string"},"description":"All,International,Domestic,Leagues,Women"},{"name":"page","in":"query","schema":{"type":"integer"},"description":"-999 to 999"}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Featured Matches > \### Retrieve Featured Cricket Matches\ > \ > This endpoint makes an HTTP GET request to retrieve the details of featured cricket matches.\ > \ > \#### Request\ > \ > \- Endpoint: \` > \ > \ > \#### Response\ > \ > \- Status: 200\ > \ > \- Content-Type: application/json\ > \ > \- Body:\ > \ > \- The response contains an array of objects, each representing a featured match. Each object includes details such as display feature match scorecard, match abandonment status, home match update, series ID, current innings details, match status, match type, venue, match result, start date, player of the match, match score, and more. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Matches List API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/featured":{"get":{"tags":["Matches List API"],"summary":"Featured Matches","description":"### Retrieve Featured Cricket Matches\n\nThis endpoint makes an HTTP GET request to retrieve the details of featured cricket matches.\n\n#### Request\n\n- Endpoint: `https://apiv3.sportsapi360.com/cricket/api/v2/match/featured`\n \n\n#### Response\n\n- Status: 200\n \n- Content-Type: application/json\n \n- Body:\n \n - The response contains an array of objects, each representing a featured match. Each object includes details such as display feature match scorecard, match abandonment status, home match update, series ID, current innings details, match status, match type, venue, match result, start date, player of the match, match score, and more.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Schedule > \### Get Cricket Match Schedule\ > \ > This endpoint makes an HTTP GET request to retrieve the schedule of cricket matches.\ > \ > \#### Request\ > \ > \- Endpoint: \` > \ > \- Query Parameters:\ > \ > \- type (string, required): Type of matches to retrieve (e.g. All)\ > \ > \- page (integer, required): Page number for pagination (e.g. 0)\ > \ > \ > \#### Response\ > \ > \- Status: 200\ > \ > \- Content-Type: application/json\ > \ > \- Body:\ > \ > \- An array of objects, each containing match details such as match ID, date, series ID, teams, match status, venue, match result, player of the match, match score, and more. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Matches List API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/schedule":{"get":{"tags":["Matches List API"],"summary":"Match Schedule","description":"### Get Cricket Match Schedule\n\nThis endpoint makes an HTTP GET request to retrieve the schedule of cricket matches.\n\n#### Request\n\n- Endpoint: `https://apiv3.sportsapi360.com/cricket/api/v2/match/schedule`\n \n- Query Parameters:\n \n - type (string, required): Type of matches to retrieve (e.g. All)\n \n - page (integer, required): Page number for pagination (e.g. 0)\n \n\n#### Response\n\n- Status: 200\n \n- Content-Type: application/json\n \n- Body:\n \n - An array of objects, each containing match details such as match ID, date, series ID, teams, match status, venue, match result, player of the match, match score, and more.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"status","in":"query","schema":{"type":"string"},"description":"completed, upcoming, live"},{"name":"type","in":"query","schema":{"type":"string"},"description":"all, international, domestic, t20, women"},{"name":"page","in":"query","schema":{"type":"integer"},"description":"-999 to 999"}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` # Match Data API ## Match Live Score > \### Retrieve Live Cricket Match Details\ > \ > This endpoint makes an HTTP GET request to retrieve the live details of a specific cricket match.\ > \ > \#### Request\ > \ > \- Endpoint: \` > \ > \ > \#### Response\ > \ > \- Status: 200\ > \ > \- Content-Type: application/json\ > \ > \- Body:\ > \ > The response contains live details of the cricket match including batting and bowling statistics, partnership details, overs remaining, review details, run rate, live score URL, and more. The response also includes data about the last 12 balls bowled in the match. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/live":{"get":{"tags":["Match Data API"],"summary":"Match Live Score","description":"### Retrieve Live Cricket Match Details\n\nThis endpoint makes an HTTP GET request to retrieve the live details of a specific cricket match.\n\n#### Request\n\n- Endpoint: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/live`\n \n\n#### Response\n\n- Status: 200\n \n- Content-Type: application/json\n \n- Body:\n \n The response contains live details of the cricket match including batting and bowling statistics, partnership details, overs remaining, review details, run rate, live score URL, and more. The response also includes data about the last 12 balls bowled in the match.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Details > \### Retrieve Live Cricket Match Details\ > \ > This endpoint makes an HTTP GET request to retrieve the live details of a specific cricket match identified by the \`matchId\`. The purpose of this request is to provide comprehensive information about the match, including team details, player statistics, recent performances, and venue information.\ > \ > \#### Request\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Method\*\*: GET\ > \ > \ > \#### Response\ > \ > \- \*\*Status\*\*: 200\ > \ > \- \*\*Content-Type\*\*: application/json\ > \ > \- \*\*Body Structure\*\*:\ > \ > The response contains detailed information about the cricket match, structured as follows:\ > \ > \- \*\*seriesName\*\*: Name of the series.\ > \ > \- \*\*seriesID\*\*: Unique identifier for the series.\ > \ > \- \*\*homeTeamID\*\*: Identifier for the home team.\ > \ > \- \*\*homeTeamName\*\*: Name of the home team.\ > \ > \- \*\*homeTeamShortName\*\*: Short name for the home team.\ > \ > \- \*\*awayTeamID\*\*: Identifier for the away team.\ > \ > \- \*\*awayTeamName\*\*: Name of the away team.\ > \ > \- \*\*awayTeamShortName\*\*: Short name for the away team.\ > \ > \- \*\*date\*\*: Date of the match.\ > \ > \- \*\*matchOrder\*\*: Order of the match in the series.\ > \ > \- \*\*toss\*\*: Details of the toss.\ > \ > \- \*\*venue\*\*: Venue of the match.\ > \ > \- \*\*venueID\*\*: Identifier for the venue.\ > \ > \- \*\*type\*\*: Type of match (e.g., Test, ODI).\ > \ > \- \*\*umpires\*\*: Umpires officiating the match.\ > \ > \- \*\*thirdUmpire\*\*: Third umpire details.\ > \ > \- \*\*matchReferee\*\*: Referee details for the match.\ > \ > \- \*\*homePlayingXI\*\*: List of players in the home team, including player ID, role, club name, image, and captain status.\ > \ > \- \*\*awayPlayingXI\*\*: List of players in the away team, with similar details as above.\ > \ > \- \*\*homeTeamImage\*\*: Image URL for the home team.\ > \ > \- \*\*awayTeamImage\*\*: Image URL for the away team.\ > \ > \- \*\*recentPerformance\*\*: Recent performance statistics, including the last five matches played by the teams.\ > \ > \- \*\*head2head\*\*: Historical performance between the two teams.\ > \ > \- \*\*weatherConditions\*\*: Current weather details including humidity, temperature, visibility, and wind speed.\ > \ > \- \*\*venueDetails\*\*: Detailed information about the venue, including capacity, location, and pitch conditions.\ > \ > \- \*\*overallAgainst\*\*: Overall performance statistics against the opponent.\ > \ > \- \*\*teamHub\*\*: Team hub information (if applicable).\ > \ > \- \*\*notes\*\*: Additional notes related to the match.\ > \ > \ > This endpoint provides a comprehensive overview of the match, making it useful for fans, analysts, and stakeholders interested in cricket match statistics and details. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/details":{"get":{"tags":["Match Data API"],"summary":"Match Details","description":"### Retrieve Live Cricket Match Details\n\nThis endpoint makes an HTTP GET request to retrieve the live details of a specific cricket match identified by the `matchId`. The purpose of this request is to provide comprehensive information about the match, including team details, player statistics, recent performances, and venue information.\n\n#### Request\n\n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/details`\n \n- **Method**: GET\n \n\n#### Response\n\n- **Status**: 200\n \n- **Content-Type**: application/json\n \n- **Body Structure**:\n \n The response contains detailed information about the cricket match, structured as follows:\n \n - **seriesName**: Name of the series.\n \n - **seriesID**: Unique identifier for the series.\n \n - **homeTeamID**: Identifier for the home team.\n \n - **homeTeamName**: Name of the home team.\n \n - **homeTeamShortName**: Short name for the home team.\n \n - **awayTeamID**: Identifier for the away team.\n \n - **awayTeamName**: Name of the away team.\n \n - **awayTeamShortName**: Short name for the away team.\n \n - **date**: Date of the match.\n \n - **matchOrder**: Order of the match in the series.\n \n - **toss**: Details of the toss.\n \n - **venue**: Venue of the match.\n \n - **venueID**: Identifier for the venue.\n \n - **type**: Type of match (e.g., Test, ODI).\n \n - **umpires**: Umpires officiating the match.\n \n - **thirdUmpire**: Third umpire details.\n \n - **matchReferee**: Referee details for the match.\n \n - **homePlayingXI**: List of players in the home team, including player ID, role, club name, image, and captain status.\n \n - **awayPlayingXI**: List of players in the away team, with similar details as above.\n \n - **homeTeamImage**: Image URL for the home team.\n \n - **awayTeamImage**: Image URL for the away team.\n \n - **recentPerformance**: Recent performance statistics, including the last five matches played by the teams.\n \n - **head2head**: Historical performance between the two teams.\n \n - **weatherConditions**: Current weather details including humidity, temperature, visibility, and wind speed.\n \n - **venueDetails**: Detailed information about the venue, including capacity, location, and pitch conditions.\n \n - **overallAgainst**: Overall performance statistics against the opponent.\n \n - **teamHub**: Team hub information (if applicable).\n \n - **notes**: Additional notes related to the match.\n \n\nThis endpoint provides a comprehensive overview of the match, making it useful for fans, analysts, and stakeholders interested in cricket match statistics and details.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Scoreboard > \### Retrieve Live Cricket Match Scoreboard\ > \ > This endpoint retrieves the scoreboard for a specific cricket match identified by \`matchId\`. It provides comprehensive details about the match, including team performances, player statistics, and current match status.\ > \ > \### Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter): The unique identifier for the cricket match whose scoreboard is being requested.\ > \ > \ > \#### Request\ > \ > \- Endpoint: \` > \ > \ > \#### Response\ > \ > \- Status: 200\ > \ > \- Content-Type: application/json\ > \ > \ > \### Response Structure\ > \ > The response is a JSON array containing the following key components:\ > \ > \- \*\*Substitutes\*\*: List of players who are substitutes, including their IDs and names.\ > \ > \- \*\*impactPlayer\*\*: Array of impact players.\ > \ > \- \*\*battingTeamName\*\*: Name of the batting team.\ > \ > \- \*\*battingTeamShortName\*\*: Short name of the batting team.\ > \ > \- \*\*battingTeamID\*\*: Unique identifier for the batting team.\ > \ > \- \*\*runsScored\*\*: Total runs scored by the batting team.\ > \ > \- \*\*wickets\*\*: Number of wickets lost.\ > \ > \- \*\*overs\*\*: Total overs bowled.\ > \ > \- \*\*runRate\*\*: Current run rate.\ > \ > \- \*\*runRateProjection\*\*: Array containing projections of the run rate.\ > \ > \- \*\*nextBatsmans\*\*: List of players who are next to bat, including their statistics.\ > \ > \- \*\*batting\*\*: Detailed statistics for each player currently batting.\ > \ > \- \*\*bowling\*\*: Detailed statistics for each player currently bowling.\ > \ > \- \*\*extras\*\*: Information about extras such as byes, leg byes, no balls, and total extras.\ > \ > \- \*\*fow\*\*: List of players who have been dismissed, including their details.\ > \ > \- \*\*total\*\*: Summary of the total overs, runs scored, wickets, and run rate.\ > \ > \ > This endpoint is essential for obtaining real-time updates on match progress and player performance. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/scoreboard":{"get":{"tags":["Match Data API"],"summary":"Match Scoreboard","description":"### Retrieve Live Cricket Match Scoreboard\n\nThis endpoint retrieves the scoreboard for a specific cricket match identified by `matchId`. It provides comprehensive details about the match, including team performances, player statistics, and current match status.\n\n### Request Parameters\n\n- **matchId** (path parameter): The unique identifier for the cricket match whose scoreboard is being requested.\n \n\n#### Request\n\n- Endpoint: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/live`\n \n\n#### Response\n\n- Status: 200\n \n- Content-Type: application/json\n \n\n### Response Structure\n\nThe response is a JSON array containing the following key components:\n\n- **Substitutes**: List of players who are substitutes, including their IDs and names.\n \n- **impactPlayer**: Array of impact players.\n \n- **battingTeamName**: Name of the batting team.\n \n- **battingTeamShortName**: Short name of the batting team.\n \n- **battingTeamID**: Unique identifier for the batting team.\n \n- **runsScored**: Total runs scored by the batting team.\n \n- **wickets**: Number of wickets lost.\n \n- **overs**: Total overs bowled.\n \n- **runRate**: Current run rate.\n \n- **runRateProjection**: Array containing projections of the run rate.\n \n- **nextBatsmans**: List of players who are next to bat, including their statistics.\n \n- **batting**: Detailed statistics for each player currently batting.\n \n- **bowling**: Detailed statistics for each player currently bowling.\n \n- **extras**: Information about extras such as byes, leg byes, no balls, and total extras.\n \n- **fow**: List of players who have been dismissed, including their details.\n \n- **total**: Summary of the total overs, runs scored, wickets, and run rate.\n \n\nThis endpoint is essential for obtaining real-time updates on match progress and player performance.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Graphs > \## Get Match Graph Data\ > \ > This endpoint retrieves detailed graphical data for a specific cricket match identified by \`matchId\`. It provides insights into the match's run rate, score chart, and worm chart.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`matchId\`: The unique identifier for the cricket match whose graphical data is being requested.\ > \ > \ > \### Response\ > \ > Upon a successful request, the API returns a JSON object with the following structure:\ > \ > \- \*\*runRate\*\*: Contains information about the run rate during different phases of the innings.\ > \ > \- \*\*format\*\*: The format of the match (e.g., ODI, Test).\ > \ > \- \*\*inningsPhase\*\*: An array detailing each innings phase, including:\ > \ > \- \*\*highestRunrate\*\*: The highest run rate achieved.\ > \ > \- \*\*teamID\*\*: Identifier of the team.\ > \ > \- \*\*totalRuns\*\*: Total runs scored in that phase.\ > \ > \- \*\*innings\*\*: The innings number.\ > \ > \- \*\*totalWickets\*\*: Total wickets lost.\ > \ > \- \*\*teamShortName\*\*: Short name of the team.\ > \ > \- \*\*data\*\*: An array of objects containing:\ > \ > \- \*\*r\*\*: Runs scored.\ > \ > \- \*\*o\*\*: Overs bowled.\ > \ > \- \*\*scoreChart\*\*: Provides the score details of each innings phase.\ > \ > \- \*\*inningsPhase\*\*: An array of innings data, including:\ > \ > \- \*\*\_id\*\*: Unique identifier for the innings.\ > \ > \- \*\*teamID\*\*: Identifier of the team.\ > \ > \- \*\*teamShortName\*\*: Short name of the team.\ > \ > \- \*\*totalRuns\*\*: Total runs scored.\ > \ > \- \*\*totalWickets\*\*: Total wickets lost.\ > \ > \- \*\*data\*\*: An array of objects with:\ > \ > \- \*\*runs\*\*: Runs scored in the innings.\ > \ > \- \*\*wickets\*\*: Wickets lost.\ > \ > \- \*\*innings\*\*: The innings number.\ > \ > \- \*\*overNumber\*\*: The over number.\ > \ > \- \*\*wormChart\*\*: Displays the worm chart data for the innings.\ > \ > \- \*\*format\*\*: The format of the match.\ > \ > \- \*\*inningsPhase\*\*: An array detailing each innings phase, including:\ > \ > \- \*\*totalRuns\*\*: Total runs scored.\ > \ > \- \*\*\_id\*\*: Unique identifier.\ > \ > \- \*\*teamID\*\*: Identifier of the team.\ > \ > \- \*\*teamShortName\*\*: Short name of the team.\ > \ > \- \*\*totalWickets\*\*: Total wickets lost.\ > \ > \- \*\*data\*\*: An array of objects with:\ > \ > \- \*\*runs\*\*: Runs scored.\ > \ > \- \*\*overNumber\*\*: The over number.\ > \ > \- \*\*wickets\*\*: Wickets lost.\ > \ > \- \*\*innings\*\*: The innings number.\ > \ > \- \*\*score\*\*: The score at that point.\ > \ > \ > \### Expected Response Format\ > \ > The response will be in JSON format with a status code of \`200\` indicating success. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/graph":{"get":{"tags":["Match Data API"],"summary":"Match Graphs","description":"## Get Match Graph Data\n\nThis endpoint retrieves detailed graphical data for a specific cricket match identified by `matchId`. It provides insights into the match's run rate, score chart, and worm chart.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/graph`\n \n- **Path Parameters**:\n \n - `matchId`: The unique identifier for the cricket match whose graphical data is being requested.\n \n\n### Response\n\nUpon a successful request, the API returns a JSON object with the following structure:\n\n- **runRate**: Contains information about the run rate during different phases of the innings.\n \n - **format**: The format of the match (e.g., ODI, Test).\n \n - **inningsPhase**: An array detailing each innings phase, including:\n \n - **highestRunrate**: The highest run rate achieved.\n \n - **teamID**: Identifier of the team.\n \n - **totalRuns**: Total runs scored in that phase.\n \n - **innings**: The innings number.\n \n - **totalWickets**: Total wickets lost.\n \n - **teamShortName**: Short name of the team.\n \n - **data**: An array of objects containing:\n \n - **r**: Runs scored.\n \n - **o**: Overs bowled.\n \n- **scoreChart**: Provides the score details of each innings phase.\n \n - **inningsPhase**: An array of innings data, including:\n \n - **_id**: Unique identifier for the innings.\n \n - **teamID**: Identifier of the team.\n \n - **teamShortName**: Short name of the team.\n \n - **totalRuns**: Total runs scored.\n \n - **totalWickets**: Total wickets lost.\n \n - **data**: An array of objects with:\n \n - **runs**: Runs scored in the innings.\n \n - **wickets**: Wickets lost.\n \n - **innings**: The innings number.\n \n - **overNumber**: The over number.\n \n- **wormChart**: Displays the worm chart data for the innings.\n \n - **format**: The format of the match.\n \n - **inningsPhase**: An array detailing each innings phase, including:\n \n - **totalRuns**: Total runs scored.\n \n - **_id**: Unique identifier.\n \n - **teamID**: Identifier of the team.\n \n - **teamShortName**: Short name of the team.\n \n - **totalWickets**: Total wickets lost.\n \n - **data**: An array of objects with:\n \n - **runs**: Runs scored.\n \n - **overNumber**: The over number.\n \n - **wickets**: Wickets lost.\n \n - **innings**: The innings number.\n \n - **score**: The score at that point.\n \n\n### Expected Response Format\n\nThe response will be in JSON format with a status code of `200` indicating success.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Last12Balls > \## Get Last 12 Balls of a Cricket Match\ > \ > This endpoint retrieves the last 12 balls from a specified cricket match.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Query Parameters\*\*:\ > \ > \- \`innings\` (required): Specifies the innings number for which the last 12 balls are requested (e.g., \`1\` for the first innings).\ > \ > \ > \### Response\ > \ > On a successful request, the API returns 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 request status.\ > \ > \- \*\*response\*\*: An array containing the details of the last 12 balls, structured as follows:\ > \ > \- \*\*over\*\*: An array of objects, each representing an over, which includes:\ > \ > \- \*\*isWicket\*\*: A string indicating if a wicket fell on this ball.\ > \ > \- \*\*isBall\*\*: A string indicating if this entry is a ball.\ > \ > \- \*\*isLastBall\*\*: A string indicating if this is the last ball of the over.\ > \ > \- \*\*overNumber\*\*: A string representing the number of the over.\ > \ > \- \*\*runs\*\*: A string indicating the number of runs scored on this ball.\ > \ > \- \*\*type\*\*: A string indicating the type of delivery.\ > \ > \- \*\*overNumber\*\*: A string representing the number of the over.\ > \ > \ > Use this endpoint to get detailed information about the last 12 balls played in a specific innings of a cricket match. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/last12balls":{"get":{"tags":["Match Data API"],"summary":"Match Last12Balls","description":"## Get Last 12 Balls of a Cricket Match\n\nThis endpoint retrieves the last 12 balls from a specified cricket match.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/last12balls`\n \n- **Query Parameters**:\n \n - `innings` (required): Specifies the innings number for which the last 12 balls are requested (e.g., `1` for the first innings).\n \n\n### Response\n\nOn a successful request, the API returns 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 request status.\n \n- **response**: An array containing the details of the last 12 balls, structured as follows:\n \n - **over**: An array of objects, each representing an over, which includes:\n \n - **isWicket**: A string indicating if a wicket fell on this ball.\n \n - **isBall**: A string indicating if this entry is a ball.\n \n - **isLastBall**: A string indicating if this is the last ball of the over.\n \n - **overNumber**: A string representing the number of the over.\n \n - **runs**: A string indicating the number of runs scored on this ball.\n \n - **type**: A string indicating the type of delivery.\n \n - **overNumber**: A string representing the number of the over.\n \n\nUse this endpoint to get detailed information about the last 12 balls played in a specific innings of a cricket match.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"innings","in":"query","schema":{"type":"integer"},"description":"1 to 10"},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Team Records > \# Get Team Records for a Match\ > \ > This endpoint retrieves the team records for a specific cricket match identified by the \`matchId\`. It provides detailed statistics about both the home and away teams, including their overall performance and records when batting first or second.\ > \ > \## HTTP Request\ > \ > \*\*Method:\*\* \`GET\` \ > \*\*Endpoint:\*\* \` > \ > \## Request Headers\ > \ > \- \*\*Content-Type:\*\* \`application/json\` \ > Indicates that the request body format is JSON.\ > \ > \ > \## Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter): The unique identifier for the match for which team records are being requested.\ > \ > \ > \### Response Fields\ > \ > \- \*\*matchID\*\*: The unique identifier for the match.\ > \ > \- \*\*compType\*\*: The type of competition.\ > \ > \- \*\*teamRecords\*\*: Contains detailed records for both teams.\ > \ > \- \*\*matchType\*\*: Type of the match (e.g., ODI, T20).\ > \ > \- \*\*homeTeamID\*\*: Identifier for the home team.\ > \ > \- \*\*awayTeamID\*\*: Identifier for the away team.\ > \ > \- \*\*homeTeamShortName\*\*: Short name of the home team.\ > \ > \- \*\*awayTeamShortName\*\*: Short name of the away team.\ > \ > \- \*\*overAllRecord\*\*: Overall performance records for both teams.\ > \ > \- \*\*homeData\*\*: Statistics for the home team.\ > \ > \- \*\*awayData\*\*: Statistics for the away team.\ > \ > \- \*\*battingFirst\*\*: Records for matches where the home team batted first.\ > \ > \- \*\*battingSecond\*\*: Records for matches where the home team batted second.\ > \ > \ > \## Error Codes\ > \ > \- \*\*404 Not Found\*\*: The specified \`matchId\` does not exist.\ > \ > \- \*\*500 Internal Server Error\*\*: An unexpected error occurred on the server.\ > \ > \ > This documentation provides a comprehensive overview of the endpoint for retrieving team records for a specified match, including the request structure, expected responses, and potential error codes. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/team-records":{"get":{"tags":["Match Data API"],"summary":"Team Records","description":"# Get Team Records for a Match\n\nThis endpoint retrieves the team records for a specific cricket match identified by the `matchId`. It provides detailed statistics about both the home and away teams, including their overall performance and records when batting first or second.\n\n## HTTP Request\n\n**Method:** `GET` \n**Endpoint:** `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/team-records`\n\n## Request Headers\n\n- **Content-Type:** `application/json` \n Indicates that the request body format is JSON.\n \n\n## Request Parameters\n\n- **matchId** (path parameter): The unique identifier for the match for which team records are being requested.\n \n\n### Response Fields\n\n- **matchID**: The unique identifier for the match.\n \n- **compType**: The type of competition.\n \n- **teamRecords**: Contains detailed records for both teams.\n \n - **matchType**: Type of the match (e.g., ODI, T20).\n \n - **homeTeamID**: Identifier for the home team.\n \n - **awayTeamID**: Identifier for the away team.\n \n - **homeTeamShortName**: Short name of the home team.\n \n - **awayTeamShortName**: Short name of the away team.\n \n - **overAllRecord**: Overall performance records for both teams.\n \n - **homeData**: Statistics for the home team.\n \n - **awayData**: Statistics for the away team.\n \n - **battingFirst**: Records for matches where the home team batted first.\n \n - **battingSecond**: Records for matches where the home team batted second.\n \n\n## Error Codes\n\n- **404 Not Found**: The specified `matchId` does not exist.\n \n- **500 Internal Server Error**: An unexpected error occurred on the server.\n \n\nThis documentation provides a comprehensive overview of the endpoint for retrieving team records for a specified match, including the request structure, expected responses, and potential error codes.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Winning Percentage > \## Get Winning Percentage for a Cricket Match\ > \ > This endpoint retrieves the winning percentage for a specified cricket match identified by \`matchId\`. It provides insights into the probability of each team winning the match, as well as the likelihood of a tie.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \### Path Parameters\ > \ > \- \`matchId\` (string): The unique identifier for the cricket match whose winning percentages are being requested.\ > \ > \ > \### Response\ > \ > On a successful request, the response will be in JSON format with the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates if the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the response (0 for success).\ > \ > \- \*\*message\*\* (string): A message providing additional information about the response (if any).\ > \ > \- \*\*response\*\* (object): Contains the winning probabilities for the match.\ > \ > \- \*\*matchID\*\* (string): The ID of the match.\ > \ > \- \*\*teamsWinProbability\*\* (object): An object containing the winning probabilities.\ > \ > \- \*\*homeTeamShortName\*\* (string): The short name of the home team.\ > \ > \- \*\*homeTeamPercentage\*\* (string): The winning percentage of the home team.\ > \ > \- \*\*awayTeamShortName\*\* (string): The short name of the away team.\ > \ > \- \*\*awayTeamPercentage\*\* (string): The winning percentage of the away team.\ > \ > \- \*\*tiePercentage\*\* (string): The percentage chance of a tie.\ > \ > \ > This endpoint is useful for analyzing match outcomes and making informed predictions based on team performance probabilities. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/winning-percentage":{"get":{"tags":["Match Data API"],"summary":"Match Winning Percentage","description":"## Get Winning Percentage for a Cricket Match\n\nThis endpoint retrieves the winning percentage for a specified cricket match identified by `matchId`. It provides insights into the probability of each team winning the match, as well as the likelihood of a tie.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/winning-percentage`\n \n\n### Path Parameters\n\n- `matchId` (string): The unique identifier for the cricket match whose winning percentages are being requested.\n \n\n### Response\n\nOn a successful request, the response will be in JSON format 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 (0 for success).\n \n- **message** (string): A message providing additional information about the response (if any).\n \n- **response** (object): Contains the winning probabilities for the match.\n \n - **matchID** (string): The ID of the match.\n \n - **teamsWinProbability** (object): An object containing the winning probabilities.\n \n - **homeTeamShortName** (string): The short name of the home team.\n \n - **homeTeamPercentage** (string): The winning percentage of the home team.\n \n - **awayTeamShortName** (string): The short name of the away team.\n \n - **awayTeamPercentage** (string): The winning percentage of the away team.\n \n - **tiePercentage** (string): The percentage chance of a tie.\n \n\nThis endpoint is useful for analyzing match outcomes and making informed predictions based on team performance probabilities.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Head2Head > \## Endpoint Description\ > \ > This endpoint retrieves head-to-head statistics for two cricket teams in a specific match. It provides detailed information about the match, including team performance, venue details, and match results.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`matchId\`: The unique identifier for the match whose head-to-head statistics are being requested.\ > \ > \ > \### Response\ > \ > \- \*\*Status Code\*\*: 200 OK\ > \ > \- \*\*Content-Type\*\*: application/json\ > \ > \ > \#### Response Body\ > \ > The response will contain the following structure:\ > \ > \- \`status\`: Indicates the success of the request (boolean).\ > \ > \- \`statusCode\`: A numerical code representing the status of the response (integer).\ > \ > \- \`message\`: A message providing additional information about the response (string).\ > \ > \- \`response\`: An array containing match details, which includes:\ > \ > \- \`id\`: Unique identifier for the match (string).\ > \ > \- \`file\_name\`: Name of the file associated with the match (string).\ > \ > \- \`display\_output\`: Output to be displayed (string).\ > \ > \- \`result\`: The overall result of the match (string).\ > \ > \- \`result\_short\`: A short description of the result (string).\ > \ > \- \`venue\_id\`: Unique identifier for the venue (string).\ > \ > \- \`venue\_name\`: Name of the venue (string).\ > \ > \- \`venue\_city\`: City where the venue is located (string).\ > \ > \- \`winner\_team\_id\`: Identifier for the winning team (string).\ > \ > \- \`winner\_team\_name\`: Name of the winning team (string).\ > \ > \- \`loser\_team\_id\`: Identifier for the losing team (string).\ > \ > \- \`loser\_team\_name\`: Name of the losing team (string).\ > \ > \- \`win\_by\`: Method of victory (string).\ > \ > \- \`margin\_value\`: The margin by which the match was won (string).\ > \ > \- \`match\_player\`: Key player of the match (string).\ > \ > \- \`match\_start\_date\`: Start date of the match (string).\ > \ > \- \`match\_end\_date\`: End date of the match (string).\ > \ > \- \`against\_team\_id\`: Identifier for the opposing team (string).\ > \ > \- \`against\_team\_name\`: Name of the opposing team (string).\ > \ > \- \`against\_team\_short\_name\`: Short name of the opposing team (string).\ > \ > \- \`home\_team\_id\`: Identifier for the home team (string).\ > \ > \- \`away\_team\_id\`: Identifier for the away team (string).\ > \ > \- \`match\_number\`: The number of the match in the series (string).\ > \ > \- \`innings\`: An array containing details about each innings, which includes:\ > \ > \- \`number\`: The innings number (string).\ > \ > \- \`batting\_team\`: The team that batted (string).\ > \ > \- \`bowling\_team\`: The team that bowled (string).\ > \ > \- \`total\`: Total runs scored in the innings (string).\ > \ > \- \`wickets\`: Number of wickets lost (string).\ > \ > \- \`overs\`: Number of overs bowled (string).\ > \ > \- \`is\_declared\`: Indicates if the innings was declared (boolean).\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`matchId\` is valid and corresponds to an existing match to receive accurate results.\ > \ > \- The response structure may vary based on the match data available. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/team-head2head":{"get":{"tags":["Match Data API"],"summary":"Match Head2Head","description":"## Endpoint Description\n\nThis endpoint retrieves head-to-head statistics for two cricket teams in a specific match. It provides detailed information about the match, including team performance, venue details, and match results.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/team-head2head`\n \n- **Path Parameters**:\n \n - `matchId`: The unique identifier for the match whose head-to-head statistics are being requested.\n \n\n### Response\n\n- **Status Code**: 200 OK\n \n- **Content-Type**: application/json\n \n\n#### Response Body\n\nThe response will contain the following structure:\n\n- `status`: Indicates the success of the request (boolean).\n \n- `statusCode`: A numerical code representing the status of the response (integer).\n \n- `message`: A message providing additional information about the response (string).\n \n- `response`: An array containing match details, which includes:\n \n - `id`: Unique identifier for the match (string).\n \n - `file_name`: Name of the file associated with the match (string).\n \n - `display_output`: Output to be displayed (string).\n \n - `result`: The overall result of the match (string).\n \n - `result_short`: A short description of the result (string).\n \n - `venue_id`: Unique identifier for the venue (string).\n \n - `venue_name`: Name of the venue (string).\n \n - `venue_city`: City where the venue is located (string).\n \n - `winner_team_id`: Identifier for the winning team (string).\n \n - `winner_team_name`: Name of the winning team (string).\n \n - `loser_team_id`: Identifier for the losing team (string).\n \n - `loser_team_name`: Name of the losing team (string).\n \n - `win_by`: Method of victory (string).\n \n - `margin_value`: The margin by which the match was won (string).\n \n - `match_player`: Key player of the match (string).\n \n - `match_start_date`: Start date of the match (string).\n \n - `match_end_date`: End date of the match (string).\n \n - `against_team_id`: Identifier for the opposing team (string).\n \n - `against_team_name`: Name of the opposing team (string).\n \n - `against_team_short_name`: Short name of the opposing team (string).\n \n - `home_team_id`: Identifier for the home team (string).\n \n - `away_team_id`: Identifier for the away team (string).\n \n - `match_number`: The number of the match in the series (string).\n \n - `innings`: An array containing details about each innings, which includes:\n \n - `number`: The innings number (string).\n \n - `batting_team`: The team that batted (string).\n \n - `bowling_team`: The team that bowled (string).\n \n - `total`: Total runs scored in the innings (string).\n \n - `wickets`: Number of wickets lost (string).\n \n - `overs`: Number of overs bowled (string).\n \n - `is_declared`: Indicates if the innings was declared (boolean).\n \n\n### Notes\n\n- Ensure that the `matchId` is valid and corresponds to an existing match to receive accurate results.\n \n- The response structure may vary based on the match data available.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Team Last Five > \## Endpoint Description\ > \ > This endpoint retrieves the last five matches played by a specific cricket team in a given match. It provides detailed insights into the team's recent performance, including match results, venues, and other relevant statistics.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`matchId\`: The unique identifier for the match whose last five matches are being requested.\ > \ > \ > \### Response\ > \ > \- \*\*Status Code\*\*: 200 OK\ > \ > \- \*\*Content-Type\*\*: application/json\ > \ > \ > \#### Response Body\ > \ > The response will contain the following structure:\ > \ > \- \`status\`: Indicates the success of the request (boolean).\ > \ > \- \`statusCode\`: A numerical code representing the status of the response (integer).\ > \ > \- \`message\`: A message providing additional information about the response (string).\ > \ > \- \`response\`: An array containing match details, which includes:\ > \ > \- \`id\`: Unique identifier for the team (string).\ > \ > \- \`last\_five\_matches\`: An array of the last five matches played by the team, each containing:\ > \ > \- \`id\`: Unique identifier for the match (string).\ > \ > \- \`file\_name\`: Name of the file associated with the match (string).\ > \ > \- \`display\_output\`: Output to be displayed (string).\ > \ > \- \`result\`: The overall result of the match (string).\ > \ > \- \`result\_short\`: A short description of the result (string).\ > \ > \- \`venue\_id\`: Unique identifier for the venue (string).\ > \ > \- \`venue\_name\`: Name of the venue (string).\ > \ > \- \`venue\_city\`: City where the venue is located (string).\ > \ > \- \`winner\_team\_id\`: Identifier for the winning team (string).\ > \ > \- \`winner\_team\_name\`: Name of the winning team (string).\ > \ > \- \`loser\_team\_id\`: Identifier for the losing team (string).\ > \ > \- \`loser\_team\_name\`: Name of the losing team (string).\ > \ > \- \`win\_by\`: Method of victory (string).\ > \ > \- \`margin\_value\`: The margin by which the match was won (string).\ > \ > \- \`match\_player\`: Key player of the match (string).\ > \ > \- \`match\_start\_date\`: Start date of the match (string).\ > \ > \- \`match\_end\_date\`: End date of the match (string).\ > \ > \- \`against\_team\_id\`: Identifier for the opposing team (string).\ > \ > \- \`against\_team\_name\`: Name of the opposing team (string).\ > \ > \- \`against\_team\_short\_name\`: Short name of the opposing team (string).\ > \ > \- \`home\_team\_id\`: Identifier for the home team (string).\ > \ > \- \`away\_team\_id\`: Identifier for the away team (string).\ > \ > \- \`match\_number\`: The number of the match in the series (string).\ > \ > \- \`innings\`: An array containing details about each innings, which includes:\ > \ > \- \`number\`: The innings number (string).\ > \ > \- \`batting\_team\`: The team that batted (string).\ > \ > \- \`bowling\_team\`: The team that bowled (string).\ > \ > \- \`total\`: Total runs scored in the innings (string).\ > \ > \- \`wickets\`: Number of wickets lost (string).\ > \ > \- \`overs\`: Number of overs bowled (string).\ > \ > \- \`is\_declared\`: Indicates if the innings was declared (boolean).\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`matchId\` is valid and corresponds to an existing match to receive accurate results.\ > \ > \- The response structure may vary based on the match data available. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/team-last-five":{"get":{"tags":["Match Data API"],"summary":"Match Team Last Five","description":"## Endpoint Description\n\nThis endpoint retrieves the last five matches played by a specific cricket team in a given match. It provides detailed insights into the team's recent performance, including match results, venues, and other relevant statistics.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/team-last-five`\n \n- **Path Parameters**:\n \n - `matchId`: The unique identifier for the match whose last five matches are being requested.\n \n\n### Response\n\n- **Status Code**: 200 OK\n \n- **Content-Type**: application/json\n \n\n#### Response Body\n\nThe response will contain the following structure:\n\n- `status`: Indicates the success of the request (boolean).\n \n- `statusCode`: A numerical code representing the status of the response (integer).\n \n- `message`: A message providing additional information about the response (string).\n \n- `response`: An array containing match details, which includes:\n \n - `id`: Unique identifier for the team (string).\n \n - `last_five_matches`: An array of the last five matches played by the team, each containing:\n \n - `id`: Unique identifier for the match (string).\n \n - `file_name`: Name of the file associated with the match (string).\n \n - `display_output`: Output to be displayed (string).\n \n - `result`: The overall result of the match (string).\n \n - `result_short`: A short description of the result (string).\n \n - `venue_id`: Unique identifier for the venue (string).\n \n - `venue_name`: Name of the venue (string).\n \n - `venue_city`: City where the venue is located (string).\n \n - `winner_team_id`: Identifier for the winning team (string).\n \n - `winner_team_name`: Name of the winning team (string).\n \n - `loser_team_id`: Identifier for the losing team (string).\n \n - `loser_team_name`: Name of the losing team (string).\n \n - `win_by`: Method of victory (string).\n \n - `margin_value`: The margin by which the match was won (string).\n \n - `match_player`: Key player of the match (string).\n \n - `match_start_date`: Start date of the match (string).\n \n - `match_end_date`: End date of the match (string).\n \n - `against_team_id`: Identifier for the opposing team (string).\n \n - `against_team_name`: Name of the opposing team (string).\n \n - `against_team_short_name`: Short name of the opposing team (string).\n \n - `home_team_id`: Identifier for the home team (string).\n \n - `away_team_id`: Identifier for the away team (string).\n \n - `match_number`: The number of the match in the series (string).\n \n - `innings`: An array containing details about each innings, which includes:\n \n - `number`: The innings number (string).\n \n - `batting_team`: The team that batted (string).\n \n - `bowling_team`: The team that bowled (string).\n \n - `total`: Total runs scored in the innings (string).\n \n - `wickets`: Number of wickets lost (string).\n \n - `overs`: Number of overs bowled (string).\n \n - `is_declared`: Indicates if the innings was declared (boolean).\n \n\n### Notes\n\n- Ensure that the `matchId` is valid and corresponds to an existing match to receive accurate results.\n \n- The response structure may vary based on the match data available.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Summary > \# Get Match Summary\ > \ > This endpoint retrieves the summary of a specific cricket match identified by its \`matchId\`. The summary includes details about the innings, scores, batting and bowling performances, and the top performers of the match.\ > \ > \## Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`matchId\` (string): The unique identifier for the match whose summary is being requested.\ > \ > \ > \## Response\ > \ > The response will be in JSON format and includes the following structure:\ > \ > \- \*\*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 the detailed match summary, including:\ > \ > \- \*\*innings\*\* (array): A list of innings played in the match, where each inning includes:\ > \ > \- \*\*score\*\* (object): Contains the scoring details:\ > \ > \- \`overs\` (string): The number of overs played.\ > \ > \- \`runsScored\` (string): Total runs scored.\ > \ > \- \`wickets\` (string): Number of wickets lost.\ > \ > \- \`runRate\` (string): The run rate of the inning.\ > \ > \- \`battingTeamName\` (string): Name of the batting team.\ > \ > \- \`battingTeamID\` (string): Identifier for the batting team.\ > \ > \- \*\*battingList\*\* (array): A list of players who batted, with details for each player including:\ > \ > \- \`playerID\` (string): Unique identifier for the player.\ > \ > \- \`playerName\` (string): Name of the player.\ > \ > \- \`playerTeam\` (string): Team of the player.\ > \ > \- \`playerMatchBalls\` (string): Balls faced by the player.\ > \ > \- \`playerMatchRuns\` (string): Runs scored by the player.\ > \ > \- \`playerBattingNumber\` (string): Batting order of the player.\ > \ > \- \`playerMatchSixes\` (string): Number of sixes hit by the player.\ > \ > \- \`playerMatchFours\` (string): Number of fours hit by the player.\ > \ > \- \*\*bowlingList\*\* (array): A list of players who bowled, with details for each player including:\ > \ > \- \`playerID\` (string): Unique identifier for the player.\ > \ > \- \`playerName\` (string): Name of the player.\ > \ > \- \`playerTeam\` (string): Team of the player.\ > \ > \- \`playerDotBalls\` (string): Number of dot balls bowled.\ > \ > \- \`playerWicketsTaken\` (string): Number of wickets taken.\ > \ > \- \`playerMaidensBowled\` (string): Number of maiden overs bowled.\ > \ > \- \`playerRunsConceeded\` (string): Runs conceded by the player.\ > \ > \- \`playerOversBowled\` (string): Overs bowled by the player.\ > \ > \- \`playerEconomyRate\` (string): Economy rate of the player.\ > \ > \- \*\*topPerformer\*\* (object): Contains the top performers in the match:\ > \ > \- \*\*batsman\*\* (object): Details of the top batsman.\ > \ > \- \*\*bowler\*\* (object): Details of the top bowler.\ > \ > \ > \## Notes\ > \ > \- Ensure that the \`matchId\` is valid and corresponds to an existing match.\ > \ > \- The response will provide comprehensive details about the match, which can be useful for analysis or reporting. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/summery":{"get":{"tags":["Match Data API"],"summary":"Match Summary","description":"# Get Match Summary\n\nThis endpoint retrieves the summary of a specific cricket match identified by its `matchId`. The summary includes details about the innings, scores, batting and bowling performances, and the top performers of the match.\n\n## Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/summery`\n \n- **Path Parameters**:\n \n - `matchId` (string): The unique identifier for the match whose summary is being requested.\n \n\n## Response\n\nThe response will be in JSON format and includes the following structure:\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 the detailed match summary, including:\n \n - **innings** (array): A list of innings played in the match, where each inning includes:\n \n - **score** (object): Contains the scoring details:\n \n - `overs` (string): The number of overs played.\n \n - `runsScored` (string): Total runs scored.\n \n - `wickets` (string): Number of wickets lost.\n \n - `runRate` (string): The run rate of the inning.\n \n - `battingTeamName` (string): Name of the batting team.\n \n - `battingTeamID` (string): Identifier for the batting team.\n \n - **battingList** (array): A list of players who batted, with details for each player including:\n \n - `playerID` (string): Unique identifier for the player.\n \n - `playerName` (string): Name of the player.\n \n - `playerTeam` (string): Team of the player.\n \n - `playerMatchBalls` (string): Balls faced by the player.\n \n - `playerMatchRuns` (string): Runs scored by the player.\n \n - `playerBattingNumber` (string): Batting order of the player.\n \n - `playerMatchSixes` (string): Number of sixes hit by the player.\n \n - `playerMatchFours` (string): Number of fours hit by the player.\n \n - **bowlingList** (array): A list of players who bowled, with details for each player including:\n \n - `playerID` (string): Unique identifier for the player.\n \n - `playerName` (string): Name of the player.\n \n - `playerTeam` (string): Team of the player.\n \n - `playerDotBalls` (string): Number of dot balls bowled.\n \n - `playerWicketsTaken` (string): Number of wickets taken.\n \n - `playerMaidensBowled` (string): Number of maiden overs bowled.\n \n - `playerRunsConceeded` (string): Runs conceded by the player.\n \n - `playerOversBowled` (string): Overs bowled by the player.\n \n - `playerEconomyRate` (string): Economy rate of the player.\n \n - **topPerformer** (object): Contains the top performers in the match:\n \n - **batsman** (object): Details of the top batsman.\n \n - **bowler** (object): Details of the top bowler.\n \n\n## Notes\n\n- Ensure that the `matchId` is valid and corresponds to an existing match.\n \n- The response will provide comprehensive details about the match, which can be useful for analysis or reporting.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Team Analysis > \# Get Team Analysis for Match\ > \ > This endpoint retrieves the team analysis for a specific cricket match identified by its \`matchId\`. The analysis includes details about both teams participating in the match, such as their overall ratings, batting strengths against different types of bowling, and other relevant metrics.\ > \ > \## Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`matchId\` (string): The unique identifier for the match whose team analysis is being requested.\ > \ > \ > \## Response\ > \ > The response will be in JSON format and includes the following structure:\ > \ > \- \*\*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 the detailed team analysis, including:\ > \ > \- \*\*matchID\*\* (string): The identifier for the match.\ > \ > \- \*\*compTypeID\*\* (string): The competition type identifier.\ > \ > \- \*\*compType\*\* (string): The competition type name.\ > \ > \- \*\*teamA\*\* (object): Analysis details for Team A, including:\ > \ > \- \*\*teamID\*\* (string|null): The unique identifier for Team A.\ > \ > \- \*\*teamShortName\*\* (string|null): The short name of Team A.\ > \ > \- \*\*battingVSPace\*\* (string|null): Batting performance against pace bowling.\ > \ > \- \*\*battingVSSpin\*\* (string|null): Batting performance against spin bowling.\ > \ > \- \*\*paceBowling\*\* (string|null): Analysis of pace bowling performance.\ > \ > \- \*\*spinBowling\*\* (string|null): Analysis of spin bowling performance.\ > \ > \- \*\*battingDepth\*\* (string|null): The batting depth of Team A.\ > \ > \- \*\*overallRating\*\* (string|null): The overall rating of Team A.\ > \ > \- \*\*teamB\*\* (object): Analysis details for Team B, including:\ > \ > \- \*\*teamID\*\* (string|null): The unique identifier for Team B.\ > \ > \- \*\*teamShortName\*\* (string|null): The short name of Team B.\ > \ > \- \*\*battingVSPace\*\* (string|null): Batting performance against pace bowling.\ > \ > \- \*\*battingVSSpin\*\* (string|null): Batting performance against spin bowling.\ > \ > \- \*\*paceBowling\*\* (string|null): Analysis of pace bowling performance.\ > \ > \- \*\*spinBowling\*\* (string|null): Analysis of spin bowling performance.\ > \ > \- \*\*battingDepth\*\* (string|null): The batting depth of Team B.\ > \ > \- \*\*overallRating\*\* (string|null): The overall rating of Team B.\ > \ > \ > \## Notes\ > \ > \- Ensure that the \`matchId\` is valid and corresponds to an existing match.\ > \ > \- The response will provide comprehensive details about the team analysis, which can be useful for tactical assessments and performance evaluations. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/team-analysis":{"get":{"tags":["Match Data API"],"summary":"Match Team Analysis","description":"# Get Team Analysis for Match\n\nThis endpoint retrieves the team analysis for a specific cricket match identified by its `matchId`. The analysis includes details about both teams participating in the match, such as their overall ratings, batting strengths against different types of bowling, and other relevant metrics.\n\n## Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/team-analysis`\n \n- **Path Parameters**:\n \n - `matchId` (string): The unique identifier for the match whose team analysis is being requested.\n \n\n## Response\n\nThe response will be in JSON format and includes the following structure:\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 the detailed team analysis, including:\n \n - **matchID** (string): The identifier for the match.\n \n - **compTypeID** (string): The competition type identifier.\n \n - **compType** (string): The competition type name.\n \n - **teamA** (object): Analysis details for Team A, including:\n \n - **teamID** (string|null): The unique identifier for Team A.\n \n - **teamShortName** (string|null): The short name of Team A.\n \n - **battingVSPace** (string|null): Batting performance against pace bowling.\n \n - **battingVSSpin** (string|null): Batting performance against spin bowling.\n \n - **paceBowling** (string|null): Analysis of pace bowling performance.\n \n - **spinBowling** (string|null): Analysis of spin bowling performance.\n \n - **battingDepth** (string|null): The batting depth of Team A.\n \n - **overallRating** (string|null): The overall rating of Team A.\n \n - **teamB** (object): Analysis details for Team B, including:\n \n - **teamID** (string|null): The unique identifier for Team B.\n \n - **teamShortName** (string|null): The short name of Team B.\n \n - **battingVSPace** (string|null): Batting performance against pace bowling.\n \n - **battingVSSpin** (string|null): Batting performance against spin bowling.\n \n - **paceBowling** (string|null): Analysis of pace bowling performance.\n \n - **spinBowling** (string|null): Analysis of spin bowling performance.\n \n - **battingDepth** (string|null): The batting depth of Team B.\n \n - **overallRating** (string|null): The overall rating of Team B.\n \n\n## Notes\n\n- Ensure that the `matchId` is valid and corresponds to an existing match.\n \n- The response will provide comprehensive details about the team analysis, which can be useful for tactical assessments and performance evaluations.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Top Pick > \## Get Top Picks for a Cricket Match\ > \ > This endpoint retrieves the top picks for a specific cricket match identified by the \`matchId\`. It provides insights into the two competing teams and their respective data, which can be useful for fans and analysts alike.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*Endpoint\*\*: \` > \ > \ > \#### Path Parameters\ > \ > \- \`matchId\` (string): The unique identifier for the cricket match for which top picks are being requested.\ > \ > \ > \### Response\ > \ > The response is returned in JSON format and contains the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the request (0 indicates success).\ > \ > \- \*\*message\*\* (string): A message providing additional context about the request status (can be empty).\ > \ > \- \*\*response\*\* (object): Contains the details of the match:\ > \ > \- \*\*team1Name\*\* (string): The name of the first team.\ > \ > \- \*\*team2Name\*\* (string): The name of the second team.\ > \ > \- \*\*team1Data\*\* (array): An array containing data related to the first team.\ > \ > \- \*\*team2Data\*\* (array): An array containing data related to the second team.\ > \ > \ > This endpoint allows users to gather important information about the match, facilitating better engagement and analysis. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/top-pick":{"get":{"tags":["Match Data API"],"summary":"Match Top Pick","description":"## Get Top Picks for a Cricket Match\n\nThis endpoint retrieves the top picks for a specific cricket match identified by the `matchId`. It provides insights into the two competing teams and their respective data, which can be useful for fans and analysts alike.\n\n### Request\n\n- **Method**: GET\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/top-pick`\n \n\n#### Path Parameters\n\n- `matchId` (string): The unique identifier for the cricket match for which top picks are being requested.\n \n\n### Response\n\nThe response is returned in JSON format and contains 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 (0 indicates success).\n \n- **message** (string): A message providing additional context about the request status (can be empty).\n \n- **response** (object): Contains the details of the match:\n \n - **team1Name** (string): The name of the first team.\n \n - **team2Name** (string): The name of the second team.\n \n - **team1Data** (array): An array containing data related to the first team.\n \n - **team2Data** (array): An array containing data related to the second team.\n \n\nThis endpoint allows users to gather important information about the match, facilitating better engagement and analysis.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Stadium Data > \# Get Stadium Information for a Cricket Match\ > \ > This endpoint retrieves detailed information about the stadium where a specific cricket match is being held. It provides various statistics and characteristics related to the venue.\ > \ > \## Request\ > \ > \*\*Method:\*\* GET \ > \*\*URL:\*\* \` > \ > \### Path Parameters\ > \ > \- \`matchId\` (string): The unique identifier for the cricket match. This parameter is required to specify which match's stadium information you are requesting.\ > \ > \ > \### Request Headers\ > \ > \- \`Content-Type\`: (optional) The media type of the resource. For this request, it is typically set to \`application/json\`.\ > \ > \ > \## Response\ > \ > \*\*Status Code:\*\* 200 OK \ > \*\*Content-Type:\*\* application/json\ > \ > \### Response Body\ > \ > The response will contain a JSON object with the following fields:\ > \ > \- \`firstBattingWinPercent\` (string): The percentage of matches won by the team batting first at this venue.\ > \ > \- \`avgFirstInningScore\` (string): The average score made in the first innings at this stadium.\ > \ > \- \`highestScoreChased\` (string): The highest score successfully chased down at this venue.\ > \ > \- \`venueName\` (string): The name of the stadium.\ > \ > \- \`venueID\` (string): A unique identifier for the venue.\ > \ > \- \`paceWicket\` (string): Information regarding the pace wicket characteristics of the stadium.\ > \ > \- \`spinWicket\` (string): Information regarding the spin wicket characteristics of the stadium.\ > \ > \- \`StadiumCharacteristics\` (array of strings): An array containing various characteristics of the stadium.\ > \ > \- \`text\` (string): Additional text or notes regarding the stadium.\ > \ > \ > This endpoint is useful for analysts and fans who want to understand the performance metrics and characteristics of a cricket stadium in relation to specific matches. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/stadiumv2":{"get":{"tags":["Match Data API"],"summary":"Match Stadium Data","description":"# Get Stadium Information for a Cricket Match\n\nThis endpoint retrieves detailed information about the stadium where a specific cricket match is being held. It provides various statistics and characteristics related to the venue.\n\n## Request\n\n**Method:** GET \n**URL:** `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/stadiumv2`\n\n### Path Parameters\n\n- `matchId` (string): The unique identifier for the cricket match. This parameter is required to specify which match's stadium information you are requesting.\n \n\n### Request Headers\n\n- `Content-Type`: (optional) The media type of the resource. For this request, it is typically set to `application/json`.\n \n\n## Response\n\n**Status Code:** 200 OK \n**Content-Type:** application/json\n\n### Response Body\n\nThe response will contain a JSON object with the following fields:\n\n- `firstBattingWinPercent` (string): The percentage of matches won by the team batting first at this venue.\n \n- `avgFirstInningScore` (string): The average score made in the first innings at this stadium.\n \n- `highestScoreChased` (string): The highest score successfully chased down at this venue.\n \n- `venueName` (string): The name of the stadium.\n \n- `venueID` (string): A unique identifier for the venue.\n \n- `paceWicket` (string): Information regarding the pace wicket characteristics of the stadium.\n \n- `spinWicket` (string): Information regarding the spin wicket characteristics of the stadium.\n \n- `StadiumCharacteristics` (array of strings): An array containing various characteristics of the stadium.\n \n- `text` (string): Additional text or notes regarding the stadium.\n \n\nThis endpoint is useful for analysts and fans who want to understand the performance metrics and characteristics of a cricket stadium in relation to specific matches.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Player Record > \## Get Player Records for a Cricket Match\ > \ > This endpoint retrieves player records for a specific cricket match identified by the \`matchId\`. It provides detailed statistics for both batting and bowling performances of players participating in the match.\ > \ > \### HTTP Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*Endpoint\*\*: \` > \ > \ > \### Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter): The unique identifier for the cricket match for which player records are being requested.\ > \ > \ > \### Response Fields\ > \ > \- \*\*status\*\*: Indicates the success of the request (boolean).\ > \ > \- \*\*statusCode\*\*: A code representing the status of the response (integer).\ > \ > \- \*\*message\*\*: A message providing additional information about the response (string).\ > \ > \- \*\*response\*\*: Contains detailed player statistics for both batting and bowling, including:\ > \ > \- \*\*matchID\*\*: The ID of the match.\ > \ > \- \*\*compType\*\*: The type of competition.\ > \ > \- \*\*playerRecordBatting\*\*: Statistics related to batting performance.\ > \ > \- \*\*playerRecordBowling\*\*: Statistics related to bowling performance.\ > \ > \ > Each of the player records includes fields such as \`teamID\`, \`shortName\`, \`playerID\`, \`playerName\`, and various performance metrics.\ > \ > This endpoint is essential for retrieving comprehensive player statistics for analysis and reporting purposes. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Match Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/player-record":{"get":{"tags":["Match Data API"],"summary":"Match Player Record","description":"## Get Player Records for a Cricket Match\n\nThis endpoint retrieves player records for a specific cricket match identified by the `matchId`. It provides detailed statistics for both batting and bowling performances of players participating in the match.\n\n### HTTP Request\n\n- **Method**: GET\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/player-record`\n \n\n### Request Parameters\n\n- **matchId** (path parameter): The unique identifier for the cricket match for which player records are being requested.\n \n\n### Response Fields\n\n- **status**: Indicates the success of the request (boolean).\n \n- **statusCode**: A code representing the status of the response (integer).\n \n- **message**: A message providing additional information about the response (string).\n \n- **response**: Contains detailed player statistics for both batting and bowling, including:\n \n - **matchID**: The ID of the match.\n \n - **compType**: The type of competition.\n \n - **playerRecordBatting**: Statistics related to batting performance.\n \n - **playerRecordBowling**: Statistics related to bowling performance.\n \n\nEach of the player records includes fields such as `teamID`, `shortName`, `playerID`, `playerName`, and various performance metrics.\n\nThis endpoint is essential for retrieving comprehensive player statistics for analysis and reporting purposes.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` # Commentery ## Match Commentary > \### Get Match Commentary\ > \ > This endpoint retrieves the commentary for a specific cricket match based on the match ID provided. It delivers detailed information about each ball played in the innings, including commentary, runs scored, and wicket details.\ > \ > \#### Request Method\ > \ > \- \*\*GET\*\*\ > \ > \ > \#### Request Endpoint\ > \ > \- \` > \ > \ > \#### Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter): The unique identifier of the match for which commentary is being requested.\ > \ > \- \*\*id\*\* (query parameter): A specific identifier to retrieve next commentary details.\ > \ > \ > \#### Response Structure\ > \ > The response is returned in JSON format and contains an array of commentary objects, each including the following fields:\ > \ > \- \*\*id\*\* (integer): The unique identifier for the commentary entry.\ > \ > \- \*\*over\*\* (string): The over number in which the ball was bowled.\ > \ > \- \*\*ballType\*\* (string): The type of ball bowled.\ > \ > \- \*\*type\*\* (string): The type of commentary.\ > \ > \- \*\*isBall\*\* (boolean): Indicates if the entry is related to a ball.\ > \ > \- \*\*runs\*\* (string): The runs scored on that ball.\ > \ > \- \*\*zad\*\* (string): Additional data related to the ball.\ > \ > \- \*\*bowlerName\*\* (string): The name of the bowler.\ > \ > \- \*\*batsmanName\*\* (string): The name of the batsman.\ > \ > \- \*\*battingStyle\*\* (string): The batting style of the batsman.\ > \ > \- \*\*commentary\*\* (string): The commentary related to the ball.\ > \ > \- \*\*wicket\*\* (boolean): Indicates if a wicket fell on that ball.\ > \ > \- \*\*isLastBall\*\* (boolean): Indicates if this is the last ball of the over.\ > \ > \- \*\*batsmanID\*\* (string): The ID of the batsman.\ > \ > \- \*\*bowlerID\*\* (string): The ID of the bowler.\ > \ > \- \*\*innings\*\* (string): The innings identifier.\ > \ > \ > This endpoint is crucial for accessing live commentary during a cricket match, enhancing the experience for fans and analysts alike. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Commentery"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/commentary":{"get":{"tags":["Commentery"],"summary":"Match Commentary","description":"### Get Match Commentary\n\nThis endpoint retrieves the commentary for a specific cricket match based on the match ID provided. It delivers detailed information about each ball played in the innings, including commentary, runs scored, and wicket details.\n\n#### Request Method\n\n- **GET**\n \n\n#### Request Endpoint\n\n- `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/commentary?id=202200`\n \n\n#### Request Parameters\n\n- **matchId** (path parameter): The unique identifier of the match for which commentary is being requested.\n \n- **id** (query parameter): A specific identifier to retrieve next commentary details.\n \n\n#### Response Structure\n\nThe response is returned in JSON format and contains an array of commentary objects, each including the following fields:\n\n- **id** (integer): The unique identifier for the commentary entry.\n \n- **over** (string): The over number in which the ball was bowled.\n \n- **ballType** (string): The type of ball bowled.\n \n- **type** (string): The type of commentary.\n \n- **isBall** (boolean): Indicates if the entry is related to a ball.\n \n- **runs** (string): The runs scored on that ball.\n \n- **zad** (string): Additional data related to the ball.\n \n- **bowlerName** (string): The name of the bowler.\n \n- **batsmanName** (string): The name of the batsman.\n \n- **battingStyle** (string): The batting style of the batsman.\n \n- **commentary** (string): The commentary related to the ball.\n \n- **wicket** (boolean): Indicates if a wicket fell on that ball.\n \n- **isLastBall** (boolean): Indicates if this is the last ball of the over.\n \n- **batsmanID** (string): The ID of the batsman.\n \n- **bowlerID** (string): The ID of the bowler.\n \n- **innings** (string): The innings identifier.\n \n\nThis endpoint is crucial for accessing live commentary during a cricket match, enhancing the experience for fans and analysts alike.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"query","schema":{"type":"integer"}},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Commentary BallByBall > \### Get Ball-by-Ball Commentary for a Match\ > \ > This endpoint retrieves detailed ball-by-ball commentary for a specific cricket match during a given innings. It provides insights into each ball bowled, including commentary, runs scored, and any wickets that may have fallen.\ > \ > \#### Request Method\ > \ > \- \*\*GET\*\*\ > \ > \ > \#### Request Endpoint\ > \ > \- \` > \ > \ > \#### Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter):\ > \ > \- The unique identifier of the match for which commentary is being requested.\ > \ > \- \*\*innings\*\* (query parameter):\ > \ > \- Indicates the innings number (e.g., \`1\` for the first innings, \`2\` for the second innings).\ > \ > \ > \#### Response Structure\ > \ > The response is returned in JSON format and contains the following fields:\ > \ > \- \*\*status\*\* (boolean):\ > \ > \- Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer):\ > \ > \- A code representing the status of the response.\ > \ > \- \*\*message\*\* (string):\ > \ > \- A message providing additional context about the response, if any.\ > \ > \- \*\*response\*\* (array):\ > \ > \- An array containing commentary details for each ball, structured as follows:\ > \ > \- Each element is an array that may include various details related to the ball.\ > \ > \ > \#### Notes\ > \ > \- The endpoint is essential for accessing real-time commentary and enhances the viewing experience for cricket fans by providing detailed insights into each ball bowled.\ > \ > \- Ensure that the \`matchId\` and \`innings\` parameters are correctly specified to retrieve the desired commentary. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Commentery"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/commentary/ballByBall":{"get":{"tags":["Commentery"],"summary":"Match Commentary BallByBall","description":"### Get Ball-by-Ball Commentary for a Match\n\nThis endpoint retrieves detailed ball-by-ball commentary for a specific cricket match during a given innings. It provides insights into each ball bowled, including commentary, runs scored, and any wickets that may have fallen.\n\n#### Request Method\n\n- **GET**\n \n\n#### Request Endpoint\n\n- `https://apiv3.sportsapi360.com/cricket/api/v2/match/:matchId/commentary/ballByBall?innings=2`\n \n\n#### Request Parameters\n\n- **matchId** (path parameter):\n \n - The unique identifier of the match for which commentary is being requested.\n \n- **innings** (query parameter):\n \n - Indicates the innings number (e.g., `1` for the first innings, `2` for the second innings).\n \n\n#### Response Structure\n\nThe response is returned in JSON format and contains the following fields:\n\n- **status** (boolean):\n \n - Indicates whether the request was successful.\n \n- **statusCode** (integer):\n \n - A code representing the status of the response.\n \n- **message** (string):\n \n - A message providing additional context about the response, if any.\n \n- **response** (array):\n \n - An array containing commentary details for each ball, structured as follows:\n \n - Each element is an array that may include various details related to the ball.\n \n\n#### Notes\n\n- The endpoint is essential for accessing real-time commentary and enhances the viewing experience for cricket fans by providing detailed insights into each ball bowled.\n \n- Ensure that the `matchId` and `innings` parameters are correctly specified to retrieve the desired commentary.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"innings","in":"query","schema":{"type":"integer"},"description":"1 to 10"},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Match Highlights > \### Get Match Highlights\ > \ > This endpoint retrieves the highlights of a specific cricket match for a given innings. It provides detailed information about each ball played in the innings, including commentary, runs scored, and wicket details.\ > \ > \#### Request Parameters\ > \ > \- \*\*matchId\*\* (path parameter): The unique identifier of the match for which highlights are being requested.\ > \ > \- \*\*innings\*\* (query parameter): Indicates the innings number (e.g., \`1\` for the first innings).\ > \ > \ > \#### Response Structure\ > \ > The response is returned in JSON format and contains the following fields:\ > \ > \- \*\*status\*\* (boolean): Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the response.\ > \ > \- \*\*message\*\* (string): A message providing additional context about the response, if any.\ > \ > \- \*\*response\*\* (array): An array of highlight objects, each containing:\ > \ > \- \*\*matchID\*\* (string): The ID of the match.\ > \ > \- \*\*ballID\*\* (string): The ID of the specific ball.\ > \ > \- \*\*ballNumber\*\* (string): The number of the ball in the innings.\ > \ > \- \*\*innings\*\* (string): The innings identifier.\ > \ > \- \*\*over\*\* (string): The over number in which the ball was bowled.\ > \ > \- \*\*overNumber\*\* (string): The sequential number of the over.\ > \ > \- \*\*commentary\*\* (string): Commentary related to the ball.\ > \ > \- \*\*teamID\*\* (string): The ID of the team involved.\ > \ > \- \*\*teamName\*\* (string): The name of the team.\ > \ > \- \*\*runs\*\* (string): The runs scored on that ball.\ > \ > \- \*\*xCoordinate\*\* (integer): The x-coordinate related to the ball's delivery.\ > \ > \- \*\*yCoordinate\*\* (integer): The y-coordinate related to the ball's delivery.\ > \ > \- \*\*zad\*\* (string): Additional data related to the ball.\ > \ > \- \*\*wicket\*\* (boolean): Indicates if a wicket fell on that ball.\ > \ > \ > This endpoint is essential for accessing detailed match highlights and can be used to enhance the viewing experience for cricket fans. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Commentery"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/match/{matchId}/highlights":{"get":{"tags":["Commentery"],"summary":"Match Highlights","description":"### Get Match Highlights\n\nThis endpoint retrieves the highlights of a specific cricket match for a given innings. It provides detailed information about each ball played in the innings, including commentary, runs scored, and wicket details.\n\n#### Request Parameters\n\n- **matchId** (path parameter): The unique identifier of the match for which highlights are being requested.\n \n- **innings** (query parameter): Indicates the innings number (e.g., `1` for the first innings).\n \n\n#### Response Structure\n\nThe response is returned in JSON format and contains the following fields:\n\n- **status** (boolean): Indicates whether the request was successful.\n \n- **statusCode** (integer): A code representing the status of the response.\n \n- **message** (string): A message providing additional context about the response, if any.\n \n- **response** (array): An array of highlight objects, each containing:\n \n - **matchID** (string): The ID of the match.\n \n - **ballID** (string): The ID of the specific ball.\n \n - **ballNumber** (string): The number of the ball in the innings.\n \n - **innings** (string): The innings identifier.\n \n - **over** (string): The over number in which the ball was bowled.\n \n - **overNumber** (string): The sequential number of the over.\n \n - **commentary** (string): Commentary related to the ball.\n \n - **teamID** (string): The ID of the team involved.\n \n - **teamName** (string): The name of the team.\n \n - **runs** (string): The runs scored on that ball.\n \n - **xCoordinate** (integer): The x-coordinate related to the ball's delivery.\n \n - **yCoordinate** (integer): The y-coordinate related to the ball's delivery.\n \n - **zad** (string): Additional data related to the ball.\n \n - **wicket** (boolean): Indicates if a wicket fell on that ball.\n \n\nThis endpoint is essential for accessing detailed match highlights and can be used to enhance the viewing experience for cricket fans.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"innings","in":"query","schema":{"type":"integer"},"description":"1 to 10"},{"name":"matchId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` # Series Lists API ## Series List (v3) > \## API Endpoint: Get Cricket Series\ > \ > \### Request Method\ > \ > \`GET\`\ > \ > \### Endpoint\ > \ > \` > \ > \### Query Parameters\ > \ > \- \*\*type\*\* (required): Specifies the type of series to fetch. In this case, it should be set to \*\*All, International, Domestic, Leagues, Women\*\*.\ > \ > \- \*\*month\*\* (required): Indicates the month for which the series data is requested. For example, \`1\` represents January.\ > \ > \ > \### Expected Response Format\ > \ > The response will return a JSON object containing the following structure:\ > \ > \- \*\*title\*\*: A string representing the title of the series.\ > \ > \- \*\*month\*\*: A nullable integer indicating the month of the series.\ > \ > \- \*\*data\*\*: An array of objects, where each object contains:\ > \ > \- \*\*tourName\*\*: A string representing the name of the tour.\ > \ > \- \*\*seriesSearchNameForES\*\*: A string for search purposes.\ > \ > \- \*\*tourID\*\*: A string representing the unique identifier for the tour.\ > \ > \- \*\*teamIDs\*\*: An array of strings representing the IDs of the teams involved.\ > \ > \- \*\*seriesType\*\*: A string indicating the type of series (e.g., ODI, Test).\ > \ > \- \*\*league\*\*: A string representing the league name.\ > \ > \- \*\*matchLevel\*\*: A string indicating the level of the match.\ > \ > \- \*\*seriesStartDate\*\*: A string representing the start date of the series.\ > \ > \- \*\*seriesEndDate\*\*: A string representing the end date of the series.\ > \ > \- \*\*T20count\*\*: An integer representing the number of T20 matches.\ > \ > \- \*\*Odicount\*\*: An integer representing the number of ODI matches.\ > \ > \- \*\*Testcount\*\*: An integer representing the number of Test matches.\ > \ > \- \*\*listA\*\*: Nullable field for additional data.\ > \ > \- \*\*firstClass\*\*: Nullable field for first-class match data.\ > \ > \- \*\*seriesStatus\*\*: A string indicating the current status of the series.\ > \ > \- \*\*priorityFlag\*\*: A string indicating if the series has priority.\ > \ > \- \*\*checkStartDate\*\*: A string for date validation.\ > \ > \- \*\*checkEndDate\*\*: A string for date validation.\ > \ > \- \*\*tournamentImage\*\*: Nullable field for the tournament image URL.\ > \ > \- \*\*hasStatistics\*\*: A boolean indicating if statistics are available.\ > \ > \- \*\*hasPoints\*\*: A boolean indicating if points are available.\ > \ > \ > \### Additional Notes\ > \ > \- Ensure that the \`type\` parameter is set to \*\*All, International, Domestic, Leagues, Women\*\* to receive relevant series data.\ > \ > \- The response may include multiple series within the \`data\` array, and each series will contain detailed information about the matches and teams involved.\ > \ > \- The \`month\` parameter helps filter the series based on the specified month, allowing for more targeted queries.\ > \ > \ > This endpoint is useful for retrieving information about international cricket series scheduled for a given month. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Series Lists API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v3/series":{"get":{"tags":["Series Lists API"],"summary":"Series List (v3)","description":"## API Endpoint: Get Cricket Series\n\n### Request Method\n\n`GET`\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/cricket/api/v3/series`\n\n### Query Parameters\n\n- **type** (required): Specifies the type of series to fetch. In this case, it should be set to **All, International, Domestic, Leagues, Women**.\n \n- **month** (required): Indicates the month for which the series data is requested. For example, `1` represents January.\n \n\n### Expected Response Format\n\nThe response will return a JSON object containing the following structure:\n\n- **title**: A string representing the title of the series.\n \n- **month**: A nullable integer indicating the month of the series.\n \n- **data**: An array of objects, where each object contains:\n \n - **tourName**: A string representing the name of the tour.\n \n - **seriesSearchNameForES**: A string for search purposes.\n \n - **tourID**: A string representing the unique identifier for the tour.\n \n - **teamIDs**: An array of strings representing the IDs of the teams involved.\n \n - **seriesType**: A string indicating the type of series (e.g., ODI, Test).\n \n - **league**: A string representing the league name.\n \n - **matchLevel**: A string indicating the level of the match.\n \n - **seriesStartDate**: A string representing the start date of the series.\n \n - **seriesEndDate**: A string representing the end date of the series.\n \n - **T20count**: An integer representing the number of T20 matches.\n \n - **Odicount**: An integer representing the number of ODI matches.\n \n - **Testcount**: An integer representing the number of Test matches.\n \n - **listA**: Nullable field for additional data.\n \n - **firstClass**: Nullable field for first-class match data.\n \n - **seriesStatus**: A string indicating the current status of the series.\n \n - **priorityFlag**: A string indicating if the series has priority.\n \n - **checkStartDate**: A string for date validation.\n \n - **checkEndDate**: A string for date validation.\n \n - **tournamentImage**: Nullable field for the tournament image URL.\n \n - **hasStatistics**: A boolean indicating if statistics are available.\n \n - **hasPoints**: A boolean indicating if points are available.\n \n\n### Additional Notes\n\n- Ensure that the `type` parameter is set to **All, International, Domestic, Leagues, Women** to receive relevant series data.\n \n- The response may include multiple series within the `data` array, and each series will contain detailed information about the matches and teams involved.\n \n- The `month` parameter helps filter the series based on the specified month, allowing for more targeted queries.\n \n\nThis endpoint is useful for retrieving information about international cricket series scheduled for a given month.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"type","in":"query","schema":{"type":"string"},"description":"International, All, Domestic, Leagues, Women"},{"name":"month","in":"query","schema":{"type":"integer"},"description":"-999 to 999"}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Series List (v2) > \# Cricket Series API - Get Live Series\ > \ > This endpoint retrieves a list of live cricket series based on the specified filter and pagination.\ > \ > \## Request\ > \ > \*\*Method:\*\* \`GET\` \ > \*\*Endpoint:\*\* \` > \ > \### Query Parameters\ > \ > \- \*\*filter\*\* (string, required): Specifies the filter for the series. In this case, it is set to \`all\` to retrieve all available series. Supported value: \*\*\`all, international, domestic, leagues, women\`\*\*\ > \ > \- \*\*type\*\* (string, required): Indicates the type of series to filter. Here, it is set to \`live\` to fetch only live series. Supported Values: \*\*\`live, completed, upcoming\`\*\*\ > \ > \- \*\*page\*\* (integer, required): Denotes the page number for pagination. The default value is \`0\`, which represents the first page.\ > \ > \ > \## Response\ > \ > The response will be in JSON format and will contain an array of series objects. Each object may have the following fields:\ > \ > \- \*\*tourName\*\* (string): The name of the tour.\ > \ > \- \*\*seriesSearchNameForES\*\* (string): The search name for the series in Elasticsearch.\ > \ > \- \*\*tourID\*\* (string): The unique identifier for the tour.\ > \ > \- \*\*league\*\* (string): The league associated with the series.\ > \ > \- \*\*seriesStartDate\*\* (string): The start date of the series.\ > \ > \- \*\*seriesEndDate\*\* (string): The end date of the series.\ > \ > \- \*\*T20count\*\* (integer): The number of T20 matches in the series.\ > \ > \- \*\*matchLevel\*\* (string): The level of matches in the series (e.g., domestic, international).\ > \ > \- \*\*Odicount\*\* (integer): The number of ODI matches in the series.\ > \ > \- \*\*Testcount\*\* (integer or null): The number of Test matches in the series.\ > \ > \- \*\*seriesStatus\*\* (string): The current status of the series.\ > \ > \ > \## Summary\ > \ > This API endpoint is designed to provide users with information about live cricket series, allowing them to filter and paginate through the data effectively. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Series Lists API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/series":{"get":{"tags":["Series Lists API"],"summary":"Series List (v2)","description":"# Cricket Series API - Get Live Series\n\nThis endpoint retrieves a list of live cricket series based on the specified filter and pagination.\n\n## Request\n\n**Method:** `GET` \n**Endpoint:** `https://apiv3.sportsapi360.com/cricket/api/v2/series`\n\n### Query Parameters\n\n- **filter** (string, required): Specifies the filter for the series. In this case, it is set to `all` to retrieve all available series. Supported value: **`all, international, domestic, leagues, women`**\n \n- **type** (string, required): Indicates the type of series to filter. Here, it is set to `live` to fetch only live series. Supported Values: **`live, completed, upcoming`**\n \n- **page** (integer, required): Denotes the page number for pagination. The default value is `0`, which represents the first page.\n \n\n## Response\n\nThe response will be in JSON format and will contain an array of series objects. Each object may have the following fields:\n\n- **tourName** (string): The name of the tour.\n \n- **seriesSearchNameForES** (string): The search name for the series in Elasticsearch.\n \n- **tourID** (string): The unique identifier for the tour.\n \n- **league** (string): The league associated with the series.\n \n- **seriesStartDate** (string): The start date of the series.\n \n- **seriesEndDate** (string): The end date of the series.\n \n- **T20count** (integer): The number of T20 matches in the series.\n \n- **matchLevel** (string): The level of matches in the series (e.g., domestic, international).\n \n- **Odicount** (integer): The number of ODI matches in the series.\n \n- **Testcount** (integer or null): The number of Test matches in the series.\n \n- **seriesStatus** (string): The current status of the series.\n \n\n## Summary\n\nThis API endpoint is designed to provide users with information about live cricket series, allowing them to filter and paginate through the data effectively.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"filter","in":"query","schema":{"type":"string"},"description":"all,international,domestic,leagues,women"},{"name":"type","in":"query","schema":{"type":"string"},"description":"live, completed, upcoming"},{"name":"page","in":"query","schema":{"type":"integer"},"description":"-999 to 999"}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` # Series Data API ## Series Matches > \### Get Matches for a Cricket Series\ > \ > This endpoint retrieves the list of matches associated with a specific cricket series identified by the \`seriesId\`.\ > \ > \#### Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*Endpoint:\*\* \` > \ > \ > \#### Path Parameters\ > \ > \- \*\*seriesId\*\*: The unique identifier for the cricket series for which the matches are being requested.\ > \ > \ > \#### Response Format\ > \ > The response will be a JSON array containing match details with the following structure:\ > \ > \- \*\*isAbandoned\*\*: Boolean indicating if the match was abandoned.\ > \ > \- \*\*matchName\*\*: Name of the match.\ > \ > \- \*\*homeTeamShortName\*\*: Short name of the home team.\ > \ > \- \*\*awayTeamShortName\*\*: Short name of the away team.\ > \ > \- \*\*matchResult\*\*: Result of the match.\ > \ > \- \*\*venue\*\*: Venue where the match is held.\ > \ > \- \*\*winningTeamID\*\*: ID of the winning team.\ > \ > \- \*\*matchNumber\*\*: Number assigned to the match.\ > \ > \- \*\*matchdate\*\*: Date of the match.\ > \ > \- \*\*matchID\*\*: Unique identifier for the match.\ > \ > \- \*\*matchStatus\*\*: Current status of the match.\ > \ > \- \*\*startDate\*\*: Scheduled start date of the match.\ > \ > \- \*\*matchLevel\*\*: Level of the match (e.g., international, domestic).\ > \ > \- \*\*matchType\*\*: Type of the match (e.g., Test, ODI, T20).\ > \ > \- \*\*statusMessage\*\*: Message indicating the current status of the match.\ > \ > \- \*\*playing11Status\*\*: Boolean indicating if the playing XI has been announced.\ > \ > \- \*\*probable11Status\*\*: Boolean indicating if the probable XI has been announced.\ > \ > \- \*\*playerOfTheMatch\*\*: Name of the player of the match.\ > \ > \- \*\*playerOfTheMatchDetails\*\*: Object containing details about the player of the match.\ > \ > \- \*\*teamsWinProbability\*\*: Object containing win probabilities for both teams and tie percentage.\ > \ > \- \*\*matchScore\*\*: Array of score details for each team in the match.\ > \ > \ > This endpoint is useful for obtaining detailed information about the matches in a cricket series, including their status and scores. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Series Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/series/{seriesId}/matches":{"get":{"tags":["Series Data API"],"summary":"Series Matches","description":"### Get Matches for a Cricket Series\n\nThis endpoint retrieves the list of matches associated with a specific cricket series identified by the `seriesId`.\n\n#### Request\n\n- **Method:** GET\n \n- **Endpoint:** `https://apiv3.sportsapi360.com/cricket/api/v2/series/:seriesId/matches`\n \n\n#### Path Parameters\n\n- **seriesId**: The unique identifier for the cricket series for which the matches are being requested.\n \n\n#### Response Format\n\nThe response will be a JSON array containing match details with the following structure:\n\n- **isAbandoned**: Boolean indicating if the match was abandoned.\n \n- **matchName**: Name of the match.\n \n- **homeTeamShortName**: Short name of the home team.\n \n- **awayTeamShortName**: Short name of the away team.\n \n- **matchResult**: Result of the match.\n \n- **venue**: Venue where the match is held.\n \n- **winningTeamID**: ID of the winning team.\n \n- **matchNumber**: Number assigned to the match.\n \n- **matchdate**: Date of the match.\n \n- **matchID**: Unique identifier for the match.\n \n- **matchStatus**: Current status of the match.\n \n- **startDate**: Scheduled start date of the match.\n \n- **matchLevel**: Level of the match (e.g., international, domestic).\n \n- **matchType**: Type of the match (e.g., Test, ODI, T20).\n \n- **statusMessage**: Message indicating the current status of the match.\n \n- **playing11Status**: Boolean indicating if the playing XI has been announced.\n \n- **probable11Status**: Boolean indicating if the probable XI has been announced.\n \n- **playerOfTheMatch**: Name of the player of the match.\n \n- **playerOfTheMatchDetails**: Object containing details about the player of the match.\n \n- **teamsWinProbability**: Object containing win probabilities for both teams and tie percentage.\n \n- **matchScore**: Array of score details for each team in the match.\n \n\nThis endpoint is useful for obtaining detailed information about the matches in a cricket series, including their status and scores.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"seriesId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Series Point Table > \## Get the Point Table for the Cricket Series\ > \ > This endpoint retrieves the point table for a specific cricket series identified by \`seriesId\`.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`seriesId\` (required): The unique identifier for the cricket series whose point table you want to fetch.\ > \ > \ > \### Response\ > \ > The response will be in JSON format and includes the following structure:\ > \ > \- \*\*name\*\*: A string representing the name of the series.\ > \ > \- \*\*teams\*\*: An array of team objects, each containing:\ > \ > \- \`pos\`: The position of the team in the point table (integer).\ > \ > \- \`teamID\`: The unique identifier for the team (string).\ > \ > \- \`teamName\`: The full name of the team (string).\ > \ > \- \`teamShortName\`: The abbreviated name of the team (string).\ > \ > \- \`all\`: Total matches played by the team (string).\ > \ > \- \`wins\`: Total matches won by the team (string).\ > \ > \- \`qp\`: Total matches that resulted in a qualified position (string).\ > \ > \- \`lost\`: Total matches lost by the team (string).\ > \ > \- \`points\`: Total points accumulated by the team (string).\ > \ > \- \`nrr\`: Net Run Rate of the team (string).\ > \ > \- \`noResult\`: Total matches with no result (string).\ > \ > \- \`isQualified\`: A boolean indicating whether the team has qualified for the next stage. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Series Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/series/{seriesId}/point-table":{"get":{"tags":["Series Data API"],"summary":"Series Point Table","description":"## Get the Point Table for the Cricket Series\n\nThis endpoint retrieves the point table for a specific cricket series identified by `seriesId`.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/series/:seriesId/point-table`\n \n- **Path Parameters**:\n \n - `seriesId` (required): The unique identifier for the cricket series whose point table you want to fetch.\n \n\n### Response\n\nThe response will be in JSON format and includes the following structure:\n\n- **name**: A string representing the name of the series.\n \n- **teams**: An array of team objects, each containing:\n \n - `pos`: The position of the team in the point table (integer).\n \n - `teamID`: The unique identifier for the team (string).\n \n - `teamName`: The full name of the team (string).\n \n - `teamShortName`: The abbreviated name of the team (string).\n \n - `all`: Total matches played by the team (string).\n \n - `wins`: Total matches won by the team (string).\n \n - `qp`: Total matches that resulted in a qualified position (string).\n \n - `lost`: Total matches lost by the team (string).\n \n - `points`: Total points accumulated by the team (string).\n \n - `nrr`: Net Run Rate of the team (string).\n \n - `noResult`: Total matches with no result (string).\n \n - `isQualified`: A boolean indicating whether the team has qualified for the next stage.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"seriesId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Series Squads > \## Get Cricket Series Squads\ > \ > This endpoint retrieves the squads for a specific cricket series identified by the \`seriesId\`.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameters\*\*:\ > \ > \- \`seriesId\` (string): The unique identifier for the cricket series whose squads are being requested.\ > \ > \ > \### Response\ > \ > The response will be in JSON format and includes the following key components:\ > \ > \- \`isNewSeries\` (boolean): Indicates whether the series is new.\ > \ > \- \`displayFormats\` (array of strings): Contains the formats in which the series is displayed.\ > \ > \- \`squadData\` (array): An array of squad information, where each squad includes:\ > \ > \- \`teamID\` (string): The unique identifier for the team.\ > \ > \- \`name\` (string): The name of the team.\ > \ > \- \`squad\` (array): Contains details about the squad members, where each member includes:\ > \ > \- \`matchType\` (string): The type of match.\ > \ > \- \`playersArray\` (array): An array of player details, where each player includes:\ > \ > \- \`playerID\` (string): The unique identifier for the player.\ > \ > \- \`iswk\` (boolean): Indicates if the player is a wicketkeeper.\ > \ > \- \`iscap\` (boolean): Indicates if the player is a captain.\ > \ > \- \`playerRole\` (string): The role of the player in the team.\ > \ > \- \`playerName\` (string): The name of the player.\ > \ > \ > This structure provides a comprehensive overview of the squads participating in the specified cricket series. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Series Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/series/{seriesId}/squads":{"get":{"tags":["Series Data API"],"summary":"Series Squads","description":"## Get Cricket Series Squads\n\nThis endpoint retrieves the squads for a specific cricket series identified by the `seriesId`.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/series/:seriesId/squads`\n \n- **Path Parameters**:\n \n - `seriesId` (string): The unique identifier for the cricket series whose squads are being requested.\n \n\n### Response\n\nThe response will be in JSON format and includes the following key components:\n\n- `isNewSeries` (boolean): Indicates whether the series is new.\n \n- `displayFormats` (array of strings): Contains the formats in which the series is displayed.\n \n- `squadData` (array): An array of squad information, where each squad includes:\n \n - `teamID` (string): The unique identifier for the team.\n \n - `name` (string): The name of the team.\n \n - `squad` (array): Contains details about the squad members, where each member includes:\n \n - `matchType` (string): The type of match.\n \n - `playersArray` (array): An array of player details, where each player includes:\n \n - `playerID` (string): The unique identifier for the player.\n \n - `iswk` (boolean): Indicates if the player is a wicketkeeper.\n \n - `iscap` (boolean): Indicates if the player is a captain.\n \n - `playerRole` (string): The role of the player in the team.\n \n - `playerName` (string): The name of the player.\n \n\nThis structure provides a comprehensive overview of the squads participating in the specified cricket series.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"seriesId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Series Statics > \# Get Cricket Series Statistics\ > \ > This endpoint retrieves the statistics for a specific cricket series identified by the \`seriesId\`. It provides detailed information about the series, including various performance metrics and statistics relevant to the matches played within that series.\ > \ > \## Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \### Path Parameters\ > \ > \- \`seriesId\` (required): The unique identifier for the cricket series whose statistics are being requested.\ > \ > \ > \## Response\ > \ > The response will contain a detailed JSON object with statistics related to the specified series. The structure of the response may include various metrics such as match results, player performances, and other relevant data points.\ > \ > \### Expected Response Format\ > \ > \- \*\*Status Code\*\*: 200 OK (if the request is successful)\ > \ > \- \*\*Content-Type\*\*: application/json\ > \ > \ > \### Important Notes\ > \ > \- Ensure that the \`seriesId\` is valid and corresponds to an existing cricket series in the database.\ > \ > \- The response may vary based on the availability of data for the requested series.\ > \ > \- Handle potential errors gracefully, such as invalid \`seriesId\` or server issues, which may return appropriate error codes (e.g., 404 Not Found, 500 Internal Server Error). ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Series Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/series/{seriesId}/statics":{"get":{"tags":["Series Data API"],"summary":"Series Statics","description":"# Get Cricket Series Statistics\n\nThis endpoint retrieves the statistics for a specific cricket series identified by the `seriesId`. It provides detailed information about the series, including various performance metrics and statistics relevant to the matches played within that series.\n\n## Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/series/:seriesId/statics`\n \n\n### Path Parameters\n\n- `seriesId` (required): The unique identifier for the cricket series whose statistics are being requested.\n \n\n## Response\n\nThe response will contain a detailed JSON object with statistics related to the specified series. The structure of the response may include various metrics such as match results, player performances, and other relevant data points.\n\n### Expected Response Format\n\n- **Status Code**: 200 OK (if the request is successful)\n \n- **Content-Type**: application/json\n \n\n### Important Notes\n\n- Ensure that the `seriesId` is valid and corresponds to an existing cricket series in the database.\n \n- The response may vary based on the availability of data for the requested series.\n \n- Handle potential errors gracefully, such as invalid `seriesId` or server issues, which may return appropriate error codes (e.g., 404 Not Found, 500 Internal Server Error).","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"seriesId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Series Stadiums > \ > \# Get Stadiums by Series ID\ > \ > This endpoint retrieves a list of stadiums associated with a specific cricket series identified by the \`seriesId\`. \ > \ > \## Request Method\ > \*\*GET\*\*\ > \ > \## Endpoint\ > \` > \ > \## Path Parameters\ > \- \`seriesId\` (string): The unique identifier for the cricket series for which you want to fetch the associated stadiums.\ > \ > \## Expected Response Format\ > The response will be in JSON format and includes 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\` (array): An array of stadium objects, each containing:\ > \- \`stadiumName\` (string): The name of the stadium.\ > \- \`capacity\` (string): The seating capacity of the stadium.\ > \- \`city\` (string): The city where the stadium is located.\ > \- \`venueId\` (string): The unique identifier for the stadium.\ > \ > \### Example Response\ > \`\`\`json\ > {\ > "status": true,\ > "statusCode": 0,\ > "message": "",\ > "response": \[\ > {\ > "stadiumName": "",\ > "capacity": "",\ > "city": "",\ > "venueId": ""\ > }\ > ]\ > }\ > \`\`\`\ > \ > This endpoint is useful for applications that require information about stadiums for a particular cricket series, allowing users to view venue details and capacities.
````json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Series Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/series/{seriesId}/stadiums":{"get":{"tags":["Series Data API"],"summary":"Series Stadiums","description":"\n# Get Stadiums by Series ID\n\nThis endpoint retrieves a list of stadiums associated with a specific cricket series identified by the `seriesId`. \n\n## Request Method\n**GET**\n\n## Endpoint\n`https://apiv3.sportsapi360.com/cricket/api/v2/series/:seriesId/stadiums`\n\n## Path Parameters\n- `seriesId` (string): The unique identifier for the cricket series for which you want to fetch the associated stadiums.\n\n## Expected Response Format\nThe response will be in JSON format and includes the following fields:\n- `status` (boolean): Indicates the success of the request.\n- `statusCode` (integer): A code representing the status of the response.\n- `message` (string): A message providing additional information about the response.\n- `response` (array): An array of stadium objects, each containing:\n - `stadiumName` (string): The name of the stadium.\n - `capacity` (string): The seating capacity of the stadium.\n - `city` (string): The city where the stadium is located.\n - `venueId` (string): The unique identifier for the stadium.\n\n### Example Response\n```json\n{\n \"status\": true,\n \"statusCode\": 0,\n \"message\": \"\",\n \"response\": [\n {\n \"stadiumName\": \"\",\n \"capacity\": \"\",\n \"city\": \"\",\n \"venueId\": \"\"\n }\n ]\n}\n```\n\nThis endpoint is useful for applications that require information about stadiums for a particular cricket series, allowing users to view venue details and capacities.\n","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"seriesId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ```` # 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"}}}}}}}}} ``` # 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"}}}}}}}}} ``` # Ranking Data API V2 ## Ranking Men > \## Endpoint Description\ > \ > This endpoint retrieves the current rankings of men's cricket players across different formats, including One Day Internationals (ODI), Test matches, and T20 matches. The rankings are categorized into all-rounders, batsmen, and bowlers, providing a comprehensive overview of player performance.\ > \ > \### Request Format\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Request Body\*\*: None\ > \ > \ > \### Response Structure\ > \ > The response is a JSON object containing the rankings for men's cricket players, structured as follows:\ > \ > \- \*\*ODI\*\*:\ > \ > \- \*\*men\*\*:\ > \ > \- \*\*allrounder\*\*: Contains details about all-rounder rankings.\ > \ > \- \*\*matchType\*\*: Type of match (e.g., ODI).\ > \ > \- \*\*gender\*\*: Gender of the players (always "male" for this endpoint).\ > \ > \- \*\*rank\*\*: An array of ranking objects, each representing a player.\ > \ > \- \*\*playerName\*\*: Name of the player.\ > \ > \- \*\*playerID\*\*: Unique identifier for the player.\ > \ > \- \*\*position\*\*: Ranking position of the player.\ > \ > \- \*\*Points\*\*: Points scored by the player.\ > \ > \- \*\*teamID\*\*: Unique identifier for the team.\ > \ > \- \*\*teamName\*\*: Name of the team.\ > \ > \- \*\*bat\*\*: Similar structure as all-rounder, but for batsmen.\ > \ > \- \*\*bowl\*\*: Similar structure as all-rounder, but for bowlers.\ > \ > \- \*\*Test\*\*: Same structure as ODI, but for Test match rankings.\ > \ > \- \*\*T20\*\*: Same structure as ODI, but for T20 match rankings.\ > \ > \ > This endpoint provides a comprehensive and structured view of the rankings of men's cricket players, allowing users to access detailed performance metrics across different formats. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Ranking Data API V2"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/ranking/men":{"get":{"tags":["Ranking Data API V2"],"summary":"Ranking Men","description":"## Endpoint Description\n\nThis endpoint retrieves the current rankings of men's cricket players across different formats, including One Day Internationals (ODI), Test matches, and T20 matches. The rankings are categorized into all-rounders, batsmen, and bowlers, providing a comprehensive overview of player performance.\n\n### Request Format\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/ranking/men`\n \n- **Request Body**: None\n \n\n### Response Structure\n\nThe response is a JSON object containing the rankings for men's cricket players, structured as follows:\n\n- **ODI**:\n \n - **men**:\n \n - **allrounder**: Contains details about all-rounder rankings.\n \n - **matchType**: Type of match (e.g., ODI).\n \n - **gender**: Gender of the players (always \"male\" for this endpoint).\n \n - **rank**: An array of ranking objects, each representing a player.\n \n - **playerName**: Name of the player.\n \n - **playerID**: Unique identifier for the player.\n \n - **position**: Ranking position of the player.\n \n - **Points**: Points scored by the player.\n \n - **teamID**: Unique identifier for the team.\n \n - **teamName**: Name of the team.\n \n - **bat**: Similar structure as all-rounder, but for batsmen.\n \n - **bowl**: Similar structure as all-rounder, but for bowlers.\n \n- **Test**: Same structure as ODI, but for Test match rankings.\n \n- **T20**: Same structure as ODI, but for T20 match rankings.\n \n\nThis endpoint provides a comprehensive and structured view of the rankings of men's cricket players, allowing users to access detailed performance metrics across different formats.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Ranking Women > \### Endpoint Description\ > \ > This API endpoint retrieves the latest women's cricket rankings across different match formats including ODI, Test, and T20.\ > \ > \### Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*Endpoint:\*\* \` > \ > \ > \### Response Format\ > \ > The response will be in JSON format and contains rankings for women players categorized by match type. The structure of the response includes:\ > \ > \- \*\*ODI\*\*\ > \ > \- \*\*women\*\*\ > \ > \- \*\*allrounder\*\*\ > \ > \- \*\*matchType\*\*: (string) Type of match.\ > \ > \- \*\*gender\*\*: (string) Gender of the players.\ > \ > \- \*\*rank\*\*: (array) List of players with their ranking details.\ > \ > \- \*\*playerName\*\*: (string) Name of the player.\ > \ > \- \*\*playerID\*\*: (string) Unique identifier for the player.\ > \ > \- \*\*position\*\*: (integer) Ranking position of the player.\ > \ > \- \*\*Points\*\*: (string) Points accumulated by the player.\ > \ > \- \*\*teamID\*\*: (string) Unique identifier for the team.\ > \ > \- \*\*teamName\*\*: (string) Name of the team.\ > \ > \- \*\*bat\*\*: Similar structure as allrounder for batting rankings.\ > \ > \- \*\*bowl\*\*: Similar structure as allrounder for bowling rankings.\ > \ > \- \*\*Test\*\*\ > \ > \- Structure is similar to ODI, but may contain null values for rankings.\ > \ > \- \*\*T20\*\*\ > \ > \- Structure is similar to ODI, with rankings for allrounders, batsmen, and bowlers.\ > \ > \ > \### Notes\ > \ > \- The response may include null values for certain fields if there are no rankings available.\ > \ > \- Ensure to handle cases where rankings may not be present for all categories. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Ranking Data API V2"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/ranking/women":{"get":{"tags":["Ranking Data API V2"],"summary":"Ranking Women","description":"### Endpoint Description\n\nThis API endpoint retrieves the latest women's cricket rankings across different match formats including ODI, Test, and T20.\n\n### Request\n\n- **Method:** GET\n \n- **Endpoint:** `https://apiv3.sportsapi360.com/cricket/api/v2/ranking/women`\n \n\n### Response Format\n\nThe response will be in JSON format and contains rankings for women players categorized by match type. The structure of the response includes:\n\n- **ODI**\n \n - **women**\n \n - **allrounder**\n \n - **matchType**: (string) Type of match.\n \n - **gender**: (string) Gender of the players.\n \n - **rank**: (array) List of players with their ranking details.\n \n - **playerName**: (string) Name of the player.\n \n - **playerID**: (string) Unique identifier for the player.\n \n - **position**: (integer) Ranking position of the player.\n \n - **Points**: (string) Points accumulated by the player.\n \n - **teamID**: (string) Unique identifier for the team.\n \n - **teamName**: (string) Name of the team.\n \n - **bat**: Similar structure as allrounder for batting rankings.\n \n - **bowl**: Similar structure as allrounder for bowling rankings.\n \n- **Test**\n \n - Structure is similar to ODI, but may contain null values for rankings.\n \n- **T20**\n \n - Structure is similar to ODI, with rankings for allrounders, batsmen, and bowlers.\n \n\n### Notes\n\n- The response may include null values for certain fields if there are no rankings available.\n \n- Ensure to handle cases where rankings may not be present for all categories.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Ranking Team > \## Endpoint Description\ > \ > This API endpoint retrieves the current rankings of cricket teams across different formats (ODI, Test, T20) for both men and women.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*Endpoint\*\*: \` > \ > \ > \### Response Format\ > \ > The response will be a JSON object containing the rankings for each format of cricket. The structure of the response is as follows:\ > \ > \- \*\*ODI\*\*:\ > \ > \- \*\*men\*\*:\ > \ > \- \*\*team\*\*:\ > \ > \- \*\*matchType\*\*: (string)\ > \ > \- \*\*rank\*\*: (array of objects)\ > \ > \- \*\*position\*\*: (string)\ > \ > \- \*\*Rating\*\*: (string)\ > \ > \- \*\*teamName\*\*: (string)\ > \ > \- \*\*teamID\*\*: (string)\ > \ > \- \*\*women\*\*:\ > \ > \- \*\*team\*\*:\ > \ > \- \*\*matchType\*\*: (string)\ > \ > \- \*\*rank\*\*: (array of objects)\ > \ > \- \*\*position\*\*: (string)\ > \ > \- \*\*Rating\*\*: (string)\ > \ > \- \*\*teamName\*\*: (string)\ > \ > \- \*\*teamID\*\*: (string)\ > \ > \- \*\*Test\*\*:\ > \ > \- \*\*men\*\*:\ > \ > \- \*\*team\*\*:\ > \ > \- \*\*matchType\*\*: (string)\ > \ > \- \*\*rank\*\*: (array of objects)\ > \ > \- \*\*position\*\*: (string)\ > \ > \- \*\*Rating\*\*: (string)\ > \ > \- \*\*teamName\*\*: (string)\ > \ > \- \*\*teamID\*\*: (string)\ > \ > \- \*\*women\*\*:\ > \ > \- \*\*team\*\*:\ > \ > \- \*\*matchType\*\*: (null)\ > \ > \- \*\*rank\*\*: (null)\ > \ > \- \*\*T20\*\*:\ > \ > \- \*\*men\*\*:\ > \ > \- \*\*team\*\*:\ > \ > \- \*\*matchType\*\*: (string)\ > \ > \- \*\*rank\*\*: (array of objects)\ > \ > \- \*\*position\*\*: (string)\ > \ > \- \*\*Rating\*\*: (string)\ > \ > \- \*\*teamName\*\*: (string)\ > \ > \- \*\*teamID\*\*: (string)\ > \ > \- \*\*women\*\*:\ > \ > \- \*\*team\*\*:\ > \ > \- \*\*matchType\*\*: (string)\ > \ > \- \*\*rank\*\*: (array of objects)\ > \ > \- \*\*position\*\*: (string)\ > \ > \- \*\*Rating\*\*: (string)\ > \ > \- \*\*teamName\*\*: (string)\ > \ > \- \*\*teamID\*\*: (string)\ > \ > \ > \### Notes\ > \ > \- The \`matchType\` indicates the type of match for which the ranking is applicable.\ > \ > \- The \`rank\` array contains the ranking details for each team, including their position, rating, name, and unique identifier. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Ranking Data API V2"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/ranking/team":{"get":{"tags":["Ranking Data API V2"],"summary":"Ranking Team","description":"## Endpoint Description\n\nThis API endpoint retrieves the current rankings of cricket teams across different formats (ODI, Test, T20) for both men and women.\n\n### Request\n\n- **Method**: GET\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v2/ranking/team`\n \n\n### Response Format\n\nThe response will be a JSON object containing the rankings for each format of cricket. The structure of the response is as follows:\n\n- **ODI**:\n \n - **men**:\n \n - **team**:\n \n - **matchType**: (string)\n \n - **rank**: (array of objects)\n \n - **position**: (string)\n \n - **Rating**: (string)\n \n - **teamName**: (string)\n \n - **teamID**: (string)\n \n - **women**:\n \n - **team**:\n \n - **matchType**: (string)\n \n - **rank**: (array of objects)\n \n - **position**: (string)\n \n - **Rating**: (string)\n \n - **teamName**: (string)\n \n - **teamID**: (string)\n \n- **Test**:\n \n - **men**:\n \n - **team**:\n \n - **matchType**: (string)\n \n - **rank**: (array of objects)\n \n - **position**: (string)\n \n - **Rating**: (string)\n \n - **teamName**: (string)\n \n - **teamID**: (string)\n \n - **women**:\n \n - **team**:\n \n - **matchType**: (null)\n \n - **rank**: (null)\n \n- **T20**:\n \n - **men**:\n \n - **team**:\n \n - **matchType**: (string)\n \n - **rank**: (array of objects)\n \n - **position**: (string)\n \n - **Rating**: (string)\n \n - **teamName**: (string)\n \n - **teamID**: (string)\n \n - **women**:\n \n - **team**:\n \n - **matchType**: (string)\n \n - **rank**: (array of objects)\n \n - **position**: (string)\n \n - **Rating**: (string)\n \n - **teamName**: (string)\n \n - **teamID**: (string)\n \n\n### Notes\n\n- The `matchType` indicates the type of match for which the ranking is applicable.\n \n- The `rank` array contains the ranking details for each team, including their position, rating, name, and unique identifier.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` # Ranking Data API V3 ## Ranking Men > \# Get Men's Cricket Rankings\ > \ > This endpoint retrieves the current rankings for men's cricket across different formats including ODI, Test, and T20. The rankings are categorized based on the match type and provide detailed information about each player's rank.\ > \ > \## Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*URL:\*\* \` > \ > \ > \## Response\ > \ > The response contains a structured JSON object with the following key components:\ > \ > \- \*\*ODI:\*\* An array of objects representing the One Day International rankings.\ > \ > \- \*\*Test:\*\* An array of objects representing the Test match rankings.\ > \ > \- \*\*T20:\*\* An array of objects representing the Twenty20 rankings.\ > \ > \ > Each ranking array includes the following fields:\ > \ > \- \*\*matchType:\*\* The type of match (e.g., ODI, Test, T20).\ > \ > \- \*\*gender:\*\* The gender category of the ranking (in this case, it will always be male).\ > \ > \- \*\*rankType:\*\* The type of ranking (e.g., player, team).\ > \ > \- \*\*updatedAt:\*\* The timestamp of the last update to the rankings.\ > \ > \- \*\*rank:\*\* An array of player ranking details, where each object includes:\ > \ > \- \*\*position:\*\* The player's current rank position.\ > \ > \- \*\*change:\*\* The change in rank since the last update.\ > \ > \- \*\*PlayerName:\*\* The name of the player.\ > \ > \- \*\*playerID:\*\* A unique identifier for the player.\ > \ > \- \*\*CountryId:\*\* The unique identifier for the player's country.\ > \ > \- \*\*CountryName:\*\* The name of the country.\ > \ > \- \*\*Country:\*\* The abbreviated name of the country.\ > \ > \- \*\*teamId:\*\* The unique identifier for the team.\ > \ > \- \*\*teamName:\*\* The name of the team.\ > \ > \- \*\*Points:\*\* The points accumulated by the player.\ > \ > \- \*\*careerbest:\*\* The player's best career ranking.\ > \ > \- \*\*rankdate:\*\* The date of the current ranking.\ > \ > \ > \## Notes\ > \ > \- Ensure that the base URL is correctly set before making the request.\ > \ > \- The response may vary based on the latest rankings and updates in the cricket world. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Ranking Data API V3"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v3/ranking/men":{"get":{"tags":["Ranking Data API V3"],"summary":"Ranking Men","description":"# Get Men's Cricket Rankings\n\nThis endpoint retrieves the current rankings for men's cricket across different formats including ODI, Test, and T20. The rankings are categorized based on the match type and provide detailed information about each player's rank.\n\n## Request\n\n- **Method:** GET\n \n- **URL:** `https://apiv3.sportsapi360.com/cricket/api/v3/ranking/men`\n \n\n## Response\n\nThe response contains a structured JSON object with the following key components:\n\n- **ODI:** An array of objects representing the One Day International rankings.\n \n- **Test:** An array of objects representing the Test match rankings.\n \n- **T20:** An array of objects representing the Twenty20 rankings.\n \n\nEach ranking array includes the following fields:\n\n- **matchType:** The type of match (e.g., ODI, Test, T20).\n \n- **gender:** The gender category of the ranking (in this case, it will always be male).\n \n- **rankType:** The type of ranking (e.g., player, team).\n \n- **updatedAt:** The timestamp of the last update to the rankings.\n \n- **rank:** An array of player ranking details, where each object includes:\n \n - **position:** The player's current rank position.\n \n - **change:** The change in rank since the last update.\n \n - **PlayerName:** The name of the player.\n \n - **playerID:** A unique identifier for the player.\n \n - **CountryId:** The unique identifier for the player's country.\n \n - **CountryName:** The name of the country.\n \n - **Country:** The abbreviated name of the country.\n \n - **teamId:** The unique identifier for the team.\n \n - **teamName:** The name of the team.\n \n - **Points:** The points accumulated by the player.\n \n - **careerbest:** The player's best career ranking.\n \n - **rankdate:** The date of the current ranking.\n \n\n## Notes\n\n- Ensure that the base URL is correctly set before making the request.\n \n- The response may vary based on the latest rankings and updates in the cricket world.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Ranking Women > \### Endpoint Description\ > \ > This endpoint retrieves the current rankings for women's cricket across different formats, specifically One Day Internationals (ODI) and Twenty20 (T20).\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \ > \### Response\ > \ > The response is a JSON object containing the rankings for women in two formats: ODI and T20. Each format includes the following structure:\ > \ > \- \*\*ODI\*\*: An array of objects representing the rankings in One Day Internationals.\ > \ > \- \*\*T20\*\*: An array of objects representing the rankings in Twenty20 matches.\ > \ > \ > \#### Response Format\ > \ > The response for both formats includes the following fields:\ > \ > \- \*\*matchType\*\*: Type of match (string).\ > \ > \- \*\*gender\*\*: Gender of the players (string).\ > \ > \- \*\*rankType\*\*: Type of ranking (string).\ > \ > \- \*\*updatedAt\*\*: Timestamp of the last update (string).\ > \ > \- \*\*rank\*\*: An array of player ranking details, where each entry includes:\ > \ > \- \*\*position\*\*: The player's rank position (string).\ > \ > \- \*\*change\*\*: The change in rank (string).\ > \ > \- \*\*PlayerName\*\*: Name of the player (string).\ > \ > \- \*\*playerID\*\*: Unique identifier for the player (string).\ > \ > \- \*\*CountryId\*\*: Identifier for the country (string).\ > \ > \- \*\*CountryName\*\*: Name of the country (string).\ > \ > \- \*\*Country\*\*: Country abbreviation (string).\ > \ > \- \*\*teamId\*\*: Identifier for the team (string).\ > \ > \- \*\*teamName\*\*: Name of the team (string).\ > \ > \- \*\*Points\*\*: Points accumulated by the player (string).\ > \ > \- \*\*careerbest\*\*: Career best ranking (string).\ > \ > \- \*\*rankdate\*\*: Date of the rank (string).\ > \ > \ > This structured response allows consumers of the API to easily access and utilize the ranking information for women's cricket. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Ranking Data API V3"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v3/ranking/women":{"get":{"tags":["Ranking Data API V3"],"summary":"Ranking Women","description":"### Endpoint Description\n\nThis endpoint retrieves the current rankings for women's cricket across different formats, specifically One Day Internationals (ODI) and Twenty20 (T20).\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/cricket/api/v3/ranking/women`\n \n\n### Response\n\nThe response is a JSON object containing the rankings for women in two formats: ODI and T20. Each format includes the following structure:\n\n- **ODI**: An array of objects representing the rankings in One Day Internationals.\n \n- **T20**: An array of objects representing the rankings in Twenty20 matches.\n \n\n#### Response Format\n\nThe response for both formats includes the following fields:\n\n- **matchType**: Type of match (string).\n \n- **gender**: Gender of the players (string).\n \n- **rankType**: Type of ranking (string).\n \n- **updatedAt**: Timestamp of the last update (string).\n \n- **rank**: An array of player ranking details, where each entry includes:\n \n - **position**: The player's rank position (string).\n \n - **change**: The change in rank (string).\n \n - **PlayerName**: Name of the player (string).\n \n - **playerID**: Unique identifier for the player (string).\n \n - **CountryId**: Identifier for the country (string).\n \n - **CountryName**: Name of the country (string).\n \n - **Country**: Country abbreviation (string).\n \n - **teamId**: Identifier for the team (string).\n \n - **teamName**: Name of the team (string).\n \n - **Points**: Points accumulated by the player (string).\n \n - **careerbest**: Career best ranking (string).\n \n - **rankdate**: Date of the rank (string).\n \n\nThis structured response allows consumers of the API to easily access and utilize the ranking information for women's cricket.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Ranking Men Team > \# Get Men's Cricket Team Rankings\ > \ > This endpoint retrieves the current rankings of men's cricket teams across different formats: ODI, T20, and Test.\ > \ > \## Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \## Response\ > \ > The response is structured in JSON format and contains the rankings for the following match types:\ > \ > \- \*\*ODI\*\*:\ > \ > \- An array of ranking details for One Day Internationals.\ > \ > \- \*\*T20\*\*:\ > \ > \- An array of ranking details for Twenty20 matches.\ > \ > \- \*\*Test\*\*:\ > \ > \- An array of ranking details for Test matches.\ > \ > \ > \### Response Structure\ > \ > Each match type contains the following fields:\ > \ > \- \*\*matchType\*\*: Type of the match (e.g., ODI, T20, Test).\ > \ > \- \*\*gender\*\*: Gender of the teams (e.g., male).\ > \ > \- \*\*rankType\*\*: Type of ranking.\ > \ > \- \*\*updatedAt\*\*: Timestamp of the last update.\ > \ > \- \*\*rank\*\*: An array of ranking details for each team, which includes:\ > \ > \- \*\*position\*\*: Current rank position of the team.\ > \ > \- \*\*change\*\*: Change in rank position.\ > \ > \- \*\*CountryId\*\*: Unique identifier for the country.\ > \ > \- \*\*Country\*\*: Name of the country.\ > \ > \- \*\*shortname\*\*: Abbreviated name of the team.\ > \ > \- \*\*teamId\*\*: Unique identifier for the team.\ > \ > \- \*\*teamName\*\*: Full name of the team.\ > \ > \- \*\*Matches\*\*: Number of matches played.\ > \ > \- \*\*Points\*\*: Total points accumulated.\ > \ > \- \*\*Rating\*\*: Average rating based on performance.\ > \ > \- \*\*rankdate\*\*: Date of the ranking.\ > \ > \ > \## Notes\ > \ > \- Ensure that the base URL is correctly set before making the request.\ > \ > \- The response may vary based on the latest rankings and updates in the cricket world. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Ranking Data API V3"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v3/ranking/team/men":{"get":{"tags":["Ranking Data API V3"],"summary":"Ranking Men Team","description":"# Get Men's Cricket Team Rankings\n\nThis endpoint retrieves the current rankings of men's cricket teams across different formats: ODI, T20, and Test.\n\n## Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v3/ranking/team/men`\n \n\n## Response\n\nThe response is structured in JSON format and contains the rankings for the following match types:\n\n- **ODI**:\n \n - An array of ranking details for One Day Internationals.\n \n- **T20**:\n \n - An array of ranking details for Twenty20 matches.\n \n- **Test**:\n \n - An array of ranking details for Test matches.\n \n\n### Response Structure\n\nEach match type contains the following fields:\n\n- **matchType**: Type of the match (e.g., ODI, T20, Test).\n \n- **gender**: Gender of the teams (e.g., male).\n \n- **rankType**: Type of ranking.\n \n- **updatedAt**: Timestamp of the last update.\n \n- **rank**: An array of ranking details for each team, which includes:\n \n - **position**: Current rank position of the team.\n \n - **change**: Change in rank position.\n \n - **CountryId**: Unique identifier for the country.\n \n - **Country**: Name of the country.\n \n - **shortname**: Abbreviated name of the team.\n \n - **teamId**: Unique identifier for the team.\n \n - **teamName**: Full name of the team.\n \n - **Matches**: Number of matches played.\n \n - **Points**: Total points accumulated.\n \n - **Rating**: Average rating based on performance.\n \n - **rankdate**: Date of the ranking.\n \n\n## Notes\n\n- Ensure that the base URL is correctly set before making the request.\n \n- The response may vary based on the latest rankings and updates in the cricket world.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Ranking Women Team > \## Endpoint Description\ > \ > This endpoint retrieves the current rankings of women's cricket teams. It provides information about the teams' positions in various formats, specifically One Day Internationals (ODI) and Twenty20 (T20) matches.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Request Body\*\*: No request body is required for this GET request.\ > \ > \ > \### Response Fields\ > \ > \- \*\*ODI\*\*: An array containing the rankings for One Day Internationals.\ > \ > \- \*\*matchType\*\*: Type of the match.\ > \ > \- \*\*gender\*\*: Gender category of the ranking.\ > \ > \- \*\*rankType\*\*: Type of ranking.\ > \ > \- \*\*updatedAt\*\*: Timestamp of the last update.\ > \ > \- \*\*rank\*\*: An array of ranking details for each team.\ > \ > \- \*\*position\*\*: Current rank position.\ > \ > \- \*\*change\*\*: Change in rank position.\ > \ > \- \*\*CountryId\*\*: Identifier for the country.\ > \ > \- \*\*Country\*\*: Name of the country.\ > \ > \- \*\*shortname\*\*: Abbreviated name of the country.\ > \ > \- \*\*teamId\*\*: Identifier for the team.\ > \ > \- \*\*teamName\*\*: Name of the team.\ > \ > \- \*\*Matches\*\*: Number of matches played.\ > \ > \- \*\*Points\*\*: Points accumulated.\ > \ > \- \*\*Rating\*\*: Rating based on performance.\ > \ > \- \*\*rankdate\*\*: Date of the ranking.\ > \ > \- \*\*T20\*\*: An array containing the rankings for Twenty20 matches, structured similarly to the ODI rankings.\ > \ > \ > This endpoint is essential for applications that need to display or utilize the latest rankings of women's cricket teams. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Ranking Data API V3"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v3/ranking/team/women":{"get":{"tags":["Ranking Data API V3"],"summary":"Ranking Women Team","description":"## Endpoint Description\n\nThis endpoint retrieves the current rankings of women's cricket teams. It provides information about the teams' positions in various formats, specifically One Day Internationals (ODI) and Twenty20 (T20) matches.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v3/ranking/team/women`\n \n- **Request Body**: No request body is required for this GET request.\n \n\n### Response Fields\n\n- **ODI**: An array containing the rankings for One Day Internationals.\n \n - **matchType**: Type of the match.\n \n - **gender**: Gender category of the ranking.\n \n - **rankType**: Type of ranking.\n \n - **updatedAt**: Timestamp of the last update.\n \n - **rank**: An array of ranking details for each team.\n \n - **position**: Current rank position.\n \n - **change**: Change in rank position.\n \n - **CountryId**: Identifier for the country.\n \n - **Country**: Name of the country.\n \n - **shortname**: Abbreviated name of the country.\n \n - **teamId**: Identifier for the team.\n \n - **teamName**: Name of the team.\n \n - **Matches**: Number of matches played.\n \n - **Points**: Points accumulated.\n \n - **Rating**: Rating based on performance.\n \n - **rankdate**: Date of the ranking.\n \n- **T20**: An array containing the rankings for Twenty20 matches, structured similarly to the ODI rankings.\n \n\nThis endpoint is essential for applications that need to display or utilize the latest rankings of women's cricket teams.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` # Search Data API ## Player Search > \## Endpoint Description\ > \ > This endpoint allows users to search for cricket players by their name. It retrieves player information based on the query parameter provided in the request.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Query Parameters\*\*:\ > \ > \- \`query\` (string): The name of the player to search for. For example, \`Virat Kohli\`.\ > \ > \ > \### Response\ > \ > The response will return a JSON array containing player details that match the search query. Each player object in the response may include the following fields:\ > \ > \- \`name\`: The name of the player.\ > \ > \- \`fullName\`: The full name of the player.\ > \ > \- \`playerID\`: A unique identifier for the player.\ > \ > \- \`birthPlace\`: The birthplace of the player.\ > \ > \- \`playerRank\`: The rank of the player (if available).\ > \ > \- \`image\`: A URL to the player's image.\ > \ > \ > \### Notes\ > \ > \- Ensure that the \`query\` parameter is properly encoded if it contains spaces or special characters.\ > \ > \- The response may contain multiple player objects or none, depending on the search results.\ > \ > \- Some fields in the response may be empty or null if the information is not available.\ > \ > \ > This endpoint is useful for applications that require player information for display or analytics purposes. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Search Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/search/player":{"get":{"tags":["Search Data API"],"summary":"Player Search","description":"## Endpoint Description\n\nThis endpoint allows users to search for cricket players by their name. It retrieves player information based on the query parameter provided in the request.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/search/player`\n \n- **Query Parameters**:\n \n - `query` (string): The name of the player to search for. For example, `Virat Kohli`.\n \n\n### Response\n\nThe response will return a JSON array containing player details that match the search query. Each player object in the response may include the following fields:\n\n- `name`: The name of the player.\n \n- `fullName`: The full name of the player.\n \n- `playerID`: A unique identifier for the player.\n \n- `birthPlace`: The birthplace of the player.\n \n- `playerRank`: The rank of the player (if available).\n \n- `image`: A URL to the player's image.\n \n\n### Notes\n\n- Ensure that the `query` parameter is properly encoded if it contains spaces or special characters.\n \n- The response may contain multiple player objects or none, depending on the search results.\n \n- Some fields in the response may be empty or null if the information is not available.\n \n\nThis endpoint is useful for applications that require player information for display or analytics purposes.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"query","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` ## Team Search > \## API Endpoint: Search Team\ > \ > \### Purpose\ > \ > This endpoint allows users to search for cricket teams based on a specified query. It is particularly useful for retrieving team information, such as the team's name, ID, short name, and associated image.\ > \ > \### Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*URL:\*\* \` > \ > \ > \#### Query Parameters\ > \ > \- \*\*query\*\* (string, required): The name or part of the name of the cricket team you want to search for. For example, to search for the England cricket team, you would use \`query=England\`.\ > \ > \ > \### Expected Response Format\ > \ > The response will be a JSON array containing objects that represent the teams matching the search criteria. Each object will include the following fields:\ > \ > \- \*\*name\*\* (string): The full name of the cricket team.\ > \ > \- \*\*teamID\*\* (string): A unique identifier for the team.\ > \ > \- \*\*shortName\*\* (string): A shorter version of the team's name.\ > \ > \- \*\*image\*\* (string): A URL or path to an image representing the team.\ > \ > \ > \### Additional Notes\ > \ > \- Ensure that the \`query\` parameter is URL-encoded if it contains special characters.\ > \ > \- The response may return an empty array if no teams match the search criteria.\ > \ > \- This endpoint is useful for applications that require dynamic team information based on user input. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Search Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/search/team":{"get":{"tags":["Search Data API"],"summary":"Team Search","description":"## API Endpoint: Search Team\n\n### Purpose\n\nThis endpoint allows users to search for cricket teams based on a specified query. It is particularly useful for retrieving team information, such as the team's name, ID, short name, and associated image.\n\n### Request\n\n- **Method:** GET\n \n- **URL:** `https://apiv3.sportsapi360.com/cricket/api/v2/search/team`\n \n\n#### Query Parameters\n\n- **query** (string, required): The name or part of the name of the cricket team you want to search for. For example, to search for the England cricket team, you would use `query=England`.\n \n\n### Expected Response Format\n\nThe response will be a JSON array containing objects that represent the teams matching the search criteria. Each object will include the following fields:\n\n- **name** (string): The full name of the cricket team.\n \n- **teamID** (string): A unique identifier for the team.\n \n- **shortName** (string): A shorter version of the team's name.\n \n- **image** (string): A URL or path to an image representing the team.\n \n\n### Additional Notes\n\n- Ensure that the `query` parameter is URL-encoded if it contains special characters.\n \n- The response may return an empty array if no teams match the search criteria.\n \n- This endpoint is useful for applications that require dynamic team information based on user input.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"query","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` # Stadium Data API ## Stadium Details > \### API Endpoint: Get Stadium Details\ > \ > This endpoint retrieves detailed information about a specific cricket stadium based on the provided stadium ID. It is useful for obtaining various statistics and attributes related to the stadium.\ > \ > \#### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`stadiumId\` (string): The unique identifier for the stadium whose details are to be fetched.\ > \ > \ > \#### Response\ > \ > The response will return a JSON object containing the following structure:\ > \ > \- \`image\` (string): URL or path to an image of the stadium.\ > \ > \- \`venueID\` (string): Unique identifier for the venue.\ > \ > \- \`fullName\` (string): Full name of the stadium.\ > \ > \- \`capacity\` (string): Seating capacity of the stadium.\ > \ > \- \`city\` (string): City where the stadium is located.\ > \ > \- \`country\` (string): Country where the stadium is located.\ > \ > \- \`bowlingEnds\` (string): Description of the bowling ends.\ > \ > \- \`floodlight\` (string): Information regarding floodlight availability.\ > \ > \ > Additionally, the response includes \`venueStats\`, which contains detailed statistics for different formats of cricket:\ > \ > \- \`odiDetails\`: Statistics for One Day Internationals.\ > \ > \- \`avgIstInningScore\` (string): Average score in the first innings.\ > \ > \- \`firstBattingWin\` (integer): Number of times the first batting team won.\ > \ > \- \`firstMatch\`, \`lastMatch\`, \`highestScoreMatch\`, \`lowestScoreMatch\`: Objects containing details about specific matches (e.g., match name, status, score, start date).\ > \ > \- \`testDetails\`: Statistics for Test matches (same structure as \`odiDetails\`).\ > \ > \- \`t20Details\`: Statistics for T20 matches (same structure as \`odiDetails\`).\ > \ > \ > This structured response allows consumers of the API to easily access and utilize stadium-related information for various cricket formats. ```json {"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Stadium Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/stadium/{stadiumId}":{"get":{"tags":["Stadium Data API"],"summary":"Stadium Details","description":"### API Endpoint: Get Stadium Details\n\nThis endpoint retrieves detailed information about a specific cricket stadium based on the provided stadium ID. It is useful for obtaining various statistics and attributes related to the stadium.\n\n#### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/stadium/:stadiumId`\n \n- **Path Parameter**:\n \n - `stadiumId` (string): The unique identifier for the stadium whose details are to be fetched.\n \n\n#### Response\n\nThe response will return a JSON object containing the following structure:\n\n- `image` (string): URL or path to an image of the stadium.\n \n- `venueID` (string): Unique identifier for the venue.\n \n- `fullName` (string): Full name of the stadium.\n \n- `capacity` (string): Seating capacity of the stadium.\n \n- `city` (string): City where the stadium is located.\n \n- `country` (string): Country where the stadium is located.\n \n- `bowlingEnds` (string): Description of the bowling ends.\n \n- `floodlight` (string): Information regarding floodlight availability.\n \n\nAdditionally, the response includes `venueStats`, which contains detailed statistics for different formats of cricket:\n\n- `odiDetails`: Statistics for One Day Internationals.\n \n - `avgIstInningScore` (string): Average score in the first innings.\n \n - `firstBattingWin` (integer): Number of times the first batting team won.\n \n - `firstMatch`, `lastMatch`, `highestScoreMatch`, `lowestScoreMatch`: Objects containing details about specific matches (e.g., match name, status, score, start date).\n \n- `testDetails`: Statistics for Test matches (same structure as `odiDetails`).\n \n- `t20Details`: Statistics for T20 matches (same structure as `odiDetails`).\n \n\nThis structured response allows consumers of the API to easily access and utilize stadium-related information for various cricket formats.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"stadiumId","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}} ``` # Welcome Welcome to the SportsAPI360 API documentation. We'll briefly inform you about the features of our API and then you can explore our documentation for yourself. SportsAPI360 is a comprehensive sports data provider offering real-time and historical data for football and cricket, tailored for developers and businesses aiming to build sports applications. #### Key Features * **Real-Time Updates**: Access live scores, statistics, and play-by-play updates with minimal latency for major events. * **Historical Data**: Retrieve extensive historical data for teams, players, and competitions to support in-depth analysis. * **Global Coverage**: Data spans over 100 leagues and tournaments worldwide, including prominent football leagues like the Premier League, La Liga, Bundesliga, Serie A, Ligue 1, and the Champions League. * **Developer-Friendly API**: Offers a well-documented RESTful API with SDKs for popular programming languages, facilitating quick and easy integration. * **Reliability and Security**: Ensures 99.9% uptime with enterprise-grade security measures. * **Affordable Pricing**: Provides a free plan with 500 API calls per month, covering all matches, countries, leagues, and fixtures, making it accessible for developers and small businesses. #### API Access and Documentation Developers can access the API by registering and obtaining an API key. The API supports endpoints for both football and cricket data, with a rate limit of 100 requests per minute and an average response time of approximately 120 milliseconds. Comprehensive documentation is available to guide users through the integration and usage process. For more information or to get started, visit the [SportsAPI360 website](https://sportsapi360.com/). {% hint style="info" %} Please note that our entire Cricket API collection with all endpoints is available in Postman. [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://football-postman.sportsapi360.com/) {% endhint %} # Getting Started Welcome aboard! This section will guide you through the steps to quickly start using **SportsAPI360’s powerful sports data APIs**. Whether you're building an app for live cricket scores, a football results tracker, or a sports analytics dashboard, we make it easy for you to integrate real-time and historical data. #### ✅ Step 1: Sign Up Go to [sportsapi360.com](https://sportsapi360.com/) and create a free developer account.\ You'll get access to your dashboard, where you can manage your subscription, usage, and API keys. *** #### 🔐 Step 2: Get Your API Key Once logged in, go to your **Dashboard > App > API Key** section.\ This unique key identifies your account and must be included in all API requests. * Your key looks like this: `api_key=YOUR_API_KEY_HERE` * Keep it secure and don’t expose it in the frontend code. {% hint style="info" %} The Api Key has no expiration date and will remain valid until you manually delete it yourself. {% endhint %} *** #### 📦 Step 3: Choose a Subscription Plan We offer flexible pricing plans for developers, startups, and enterprises: * **Free Trial**: Perfect for testing and learning * **Developer Plan**: Ideal for indie projects or MVPs * **Pro & Business Plans**: High request limits, commercial rights, and priority support Visit the Pricing Page for full details. *** API utilizes response codes to indicate successful and failed API requests. When making a request, a code response will always be returned. See below for a short list of possible code responses: | | | | ----- | ---------------------------------------------------------------------------------------------------------------------- | | `200` | Successful request and data was returned | | `400` | Part of the request is malformed; the exact reason can be found in the response | | `401` | The request is not authenticated | | `403` | Unauthorized request to access data from an ineligible plan | | `404` | This recond is not found. It could be that the data you're trying to access is deleted due to rescheduling. | | `429` | You have reached the response rate limit of your plan | | `500` | Internal error with our servers | {% hint style="info" %} We recommend you use Postman for convenience. Every endpoint has an example request ready to be requested by you. Hit the button below to import our API collection. \ \ [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://cricket-postman.sportmonks.com/) {% endhint %} # API Collection Welcome to the **SportsAPI360 API Collection**. Below is a categorized list of available endpoints for **Cricket** and **Football**. Each API is designed to deliver real-time and historical data with high accuracy and speed.
Cricket APIGet comprehensive and live cricket data with highly granular endpoints. Ideal for score updates, commentary, fantasy gaming, and analytics.Screenshot 2025-06-03 151739.png
Football APIAccess comprehensive data for football leagues and tournaments worldwide, including live scores, statistics, and historical data.Screenshot 2025-06-03 151922.png
UPCOMING..!1720520339561.jpg
# Build the request Now that all prerequisites have been fulfilled, we’re ready to send our first request to the API! ## Football API The request consists of the following components: * The base URL * A path parameter, in this example, we use \[series] * A query string parameter, which is optional, so we leave this out for now * And finally, your API key {% tabs %} {% tab title="Base URL" %} {% code overflow="wrap" %} ```mathml https://apiv3.sportsapi360.com/ ``` {% endcode %} {% endtab %} {% endtabs %} {% tabs %} {% tab title="Base Endpoints" %} {% code overflow="wrap" %} ```mathml https://apiv3.sportsapi360.com/football/api/v1/ ``` {% endcode %} {% endtab %} {% endtabs %} An example of a correctly authenticated request would be: {% tabs %} {% tab title="Request" %} {% code overflow="wrap" %} ```mathml curl --location 'https://apiv3.sportsapi360.com/football/api/v1/matches/live' \ --header 'x-app-key: {{ your api key }}' ``` {% endcode %} {% endtab %} {% tab title="Response" %} ``` [{ "tourName": "Indian Premier League, 2025", "seriesSearchNameForES": "Indian Premier League, 2025, March, Mar", "tourID": "7126", "league": "IPL", "seriesStartDate": "1742652000000", "seriesEndDate": "1748979000000", "T20count": 79, "matchLevel": "domestic", "Odicount": null, "Testcount": null, "seriesStatus": "live" }, { "tourName": "ICC CWC League 2, 2023-27", "seriesSearchNameForES": "ICC CWC League 2, 2023-27, February, Feb", "tourID": "4689", "league": "ICC", "seriesStartDate": "1707968700000", "seriesEndDate": "1749742200000", "T20count": null, "matchLevel": "international", "Odicount": 79, "Testcount": null, "seriesStatus": "live" }, { "tourName": "West Indies Women tour of England, 2025", "seriesSearchNameForES": "West Indies Women tour of England, 2025, May, May", "tourID": "6986", "league": "Women's International", "seriesStartDate": "1747848600000", "seriesEndDate": "1749310200000", "T20count": 3, "matchLevel": "international-womens", "Odicount": 3, "Testcount": null, "seriesStatus": "live" }] ``` {% endtab %} {% endtabs %} This request will return all of the leagues. {% hint style="info" %} Please note that our entire Football API collection with all endpoints is available in Postman. [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://football-postman.sportsapi360.com/) {% endhint %} # All endpoints On this page you can find an overview of all the endpoints. {% hint style="info" %} Please note that our entire Football API collection with all endpoints is available in Postman. [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://football-postman.sportsapi360.com/) {% endhint %}
MethodPath
GET/football/api/v1/matches/live
GET/football/api/v1/matches/schedule
GET/football/api/v1/match/:id
GET/football/api/v1/match/statistics/:id
GET/football/api/v1/match/lineups/:id
GET/football/api/v1/match/incidents/:id
GET/football/api/v1/match/graphs/:id
GET/football/api/v1/match/shotmap/:id
GET/football/api/v1/match/commentary/:id
GET/football/api/v1/match/shotmap/:id/player/:player
GET/football/api/v1/match/head2head/:id
GET/football/api/v1/match/win-probability/:id
GET/football/api/v1/match/teams-form/:id
GET/football/api/v1/match/managers/:id
GET/football/api/v1/match/best-players/:id
GET/football/api/v1/match/featured-player/:id
GET/football/api/v1/competitions/categories
GET/football/api/v1/competitions/categories/:cid
GET/football/api/v1/competitions/default/
GET/football/api/v1/competitions/top/
GET/football/api/v1/competitions/:tid
GET/football/api/v1/competitions/:tid/featured
GET/football/api/v1/competitions/:tid/season/:sid/info
GET/football/api/v1/competitions/:tid/season/:sid/matches
GET/football/api/v1/competitions/:tid/season/:sid/standings
GET/football/api/v1/competitions/:tid/season/:sid/top-players
GET/football/api/v1/competitions/:tid/season/:sid/top-teams
GET/football/api/v1/competitions/:tid/season/:sid/rounds
GET/football/api/v1/competitions/:tid/season/:sid/rounds/matches
GET/football/api/v1/player/:id
GET/football/api/v1/player/national-team-statistics/:id
GET/football/api/v1/player/attribute/:id
GET/football/api/v1/player/recent/matches/:id
GET/football/api/v1/player/recent/summary/:id
GET/football/api/v1/player/season/statistics/:id
GET/football/api/v1/player/statistics/:id
GET/football/api/v1/player/transfer/:id
GET/football/api/v1/player/:id/tournament/:tid/season/:sid/statistics
GET/football/api/v1/team/:id
GET/football/api/v1/team/details/:id
GET/football/api/v1/team/tournaments/:id
GET/football/api/v1/team/recent/matches/:id
GET/football/api/v1/team/next/matches/:id
GET/football/api/v1/team/squads/:id
GET/football/api/v1/team/rankings/fifa
GET/football/api/v1/team/rankings/uefa/national
GET/football/api/v1/team/rankings/uefa/club
GET/football/api/v1/manager/:id
GET/football/api/v1/manager/career/:id
GET/football/api/v1/global/search
GET/football/api/v1/image/team/:id
GET/football/api/v1/image/player/:id
GET/football/api/v1/image/manager/:id
GET/football/api/v1/image/flags/:name
GET/football/api/v1/image/tournament/unique/:id/:theme?
# Introduction to API Now that all prerequisites have been fulfilled, we’re ready to send our first request to the API! Before you are able to call our API, you need a SportsAPI360 account. [Register now.](https://sportsapi360.com/register) To make our first request, we’ll need a way to get authenticated first. **Football API 1.0** utilizes API tokens for authenticating requests. You can obtain and manage your API key in the [SportsAPI360](https://sportsapi360.com/login). Example API key: \[HdoiD312ND….] The API key is intended for your eyes only and, as such, should be stored securely. {% hint style="danger" %} API key has no expiration date and will remain valid until you manually delete it yourself. {% endhint %} ## Cricket API The request consists of the following components: * The base URL * A path parameter, in this example, we use \[series] * A query string parameter, which is optional, so we leave this out for now * And finally, your API key {% tabs %} {% tab title="Base URL" %} {% code overflow="wrap" %} ```mathml https://apiv3.sportsapi360.com/football/api/v1 ``` {% endcode %} {% endtab %} {% endtabs %} An example of a correctly authenticated request would be: {% tabs %} {% tab title="Request" %} {% code overflow="wrap" %} ```mathml curl --location 'https://apiv3.sportsapi360.com/football/api/v1/matches/live' \ --header 'x-app-key: {{ your api key }}' ``` {% endcode %} {% endtab %} {% tab title="Response" %} ``` [{ "tourName": "Indian Premier League, 2025", "seriesSearchNameForES": "Indian Premier League, 2025, March, Mar", "tourID": "7126", "league": "IPL", "seriesStartDate": "1742652000000", "seriesEndDate": "1748979000000", "T20count": 79, "matchLevel": "domestic", "Odicount": null, "Testcount": null, "seriesStatus": "live" }, { "tourName": "ICC CWC League 2, 2023-27", "seriesSearchNameForES": "ICC CWC League 2, 2023-27, February, Feb", "tourID": "4689", "league": "ICC", "seriesStartDate": "1707968700000", "seriesEndDate": "1749742200000", "T20count": null, "matchLevel": "international", "Odicount": 79, "Testcount": null, "seriesStatus": "live" }, { "tourName": "West Indies Women tour of England, 2025", "seriesSearchNameForES": "West Indies Women tour of England, 2025, May, May", "tourID": "6986", "league": "Women's International", "seriesStartDate": "1747848600000", "seriesEndDate": "1749310200000", "T20count": 3, "matchLevel": "international-womens", "Odicount": 3, "Testcount": null, "seriesStatus": "live" }] ``` {% endtab %} {% endtabs %} {% hint style="info" %} We recommend you use Postman for convenience. Every endpoint has an example request ready for you to use. Hit the button below to import our **Football API** collection. [![Run in Postman](https://docs.sportmonks.com/~gitbook/image?url=https%3A%2F%2Frun.pstmn.io%2Fbutton.svg\&width=300\&dpr=4\&quality=100\&sign=5f4dbf4c\&sv=2)](https://football-postman.sportsapi360.com/) {% endhint %} # Matches ## Live Matches > \## API Endpoint: Get Live Football Matches\ > \ > \### Purpose\ > \ > This endpoint retrieves the current live football matches along with their tournament details. It provides real-time information about ongoing matches, including team scores and tournament specifics.\ > \ > \### Request Format\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Request Body\*\*: This endpoint does not require a request body.\ > \ > \ > \### Response Structure\ > \ > The response from this endpoint will be in JSON format and includes the following key components:\ > \ > \- \*\*status\*\*: A boolean indicating the success of the request.\ > \ > \- \*\*statusCode\*\*: An integer representing the status code of the response.\ > \ > \- \*\*message\*\*: A string for any additional message related to the response.\ > \ > \- \*\*response\*\*: An array containing details of live matches. Each match object includes:\ > \ > \- \*\*tournamentId\*\*: The unique identifier for the tournament.\ > \ > \- \*\*tournament\*\*: An object containing tournament details:\ > \ > \- \*\*id\*\*: The unique identifier for the tournament.\ > \ > \- \*\*name\*\*: The name of the tournament.\ > \ > \- \*\*category\*\*: An object with category details including:\ > \ > \- \*\*name\*\*: The name of the category.\ > \ > \- \*\*id\*\*: The unique identifier for the category.\ > \ > \- \*\*country\*\*: An object with country details including:\ > \ > \- \*\*alpha2\*\*: The two-letter country code.\ > \ > \- \*\*alpha3\*\*: The three-letter country code.\ > \ > \- \*\*name\*\*: The name of the country.\ > \ > \- \*\*details\*\*: Additional tournament details including:\ > \ > \- \*\*name\*\*: The name of the tournament.\ > \ > \- \*\*category\*\*: The category details.\ > \ > \- \*\*hasPerformanceGraphFeature\*\*: A boolean indicating if performance graphs are available.\ > \ > \- \*\*id\*\*: The unique identifier for the details.\ > \ > \- \*\*country\*\*: Country details.\ > \ > \- \*\*hasEventPlayerStatistics\*\*: A boolean indicating if player statistics are available.\ > \ > \- \*\*displayInverseHomeAwayTeams\*\*: A boolean indicating if home and away teams are displayed inversely.\ > \ > \- \*\*matches\*\*: An array of match objects, each containing:\ > \ > \- \*\*tournamentId\*\*: The unique identifier for the tournament.\ > \ > \- \*\*id\*\*: The unique identifier for the match.\ > \ > \- \*\*startTimestamp\*\*: The start time of the match in timestamp format.\ > \ > \- \*\*detailId\*\*: The detail identifier for the match.\ > \ > \- \*\*season\*\*: An object with season details including:\ > \ > \- \*\*name\*\*: The name of the season.\ > \ > \- \*\*year\*\*: The year of the season.\ > \ > \- \*\*id\*\*: The unique identifier for the season.\ > \ > \- \*\*roundInfo\*\*: An object containing round information.\ > \ > \- \*\*status\*\*: An object with status details including:\ > \ > \- \*\*code\*\*: Status code.\ > \ > \- \*\*description\*\*: Description of the status.\ > \ > \- \*\*type\*\*: Type of status.\ > \ > \- \*\*statusTime\*\*: An object detailing the status time.\ > \ > \- \*\*homeTeam\*\*: An object containing details of the home team.\ > \ > \- \*\*homeScore\*\*: An object with the current score of the home team.\ > \ > \- \*\*awayTeam\*\*: An object containing details of the away team.\ > \ > \- \*\*awayScore\*\*: An object with the current score of the away team.\ > \ > \- \*\*time\*\*: An object detailing the match time.\ > \ > \- \*\*tournament\*\*: An object with tournament details (similar to the tournament object above).\ > \ > \ > This structure allows clients to easily parse and display live match information, facilitating real-time updates for users. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Matches"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/matches/live":{"get":{"tags":["Matches"],"summary":"Live Matches","description":"## API Endpoint: Get Live Football Matches\n\n### Purpose\n\nThis endpoint retrieves the current live football matches along with their tournament details. It provides real-time information about ongoing matches, including team scores and tournament specifics.\n\n### Request Format\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/matches/live`\n \n- **Request Body**: This endpoint does not require a request body.\n \n\n### Response Structure\n\nThe response from this endpoint will be in JSON format and includes the following key components:\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 for any additional message related to the response.\n \n- **response**: An array containing details of live matches. Each match object includes:\n \n - **tournamentId**: The unique identifier for the tournament.\n \n - **tournament**: An object containing tournament details:\n \n - **id**: The unique identifier for the tournament.\n \n - **name**: The name of the tournament.\n \n - **category**: An object with category details including:\n \n - **name**: The name of the category.\n \n - **id**: The unique identifier for the category.\n \n - **country**: An object with country details including:\n \n - **alpha2**: The two-letter country code.\n \n - **alpha3**: The three-letter country code.\n \n - **name**: The name of the country.\n \n - **details**: Additional tournament details including:\n \n - **name**: The name of the tournament.\n \n - **category**: The category details.\n \n - **hasPerformanceGraphFeature**: A boolean indicating if performance graphs are available.\n \n - **id**: The unique identifier for the details.\n \n - **country**: Country details.\n \n - **hasEventPlayerStatistics**: A boolean indicating if player statistics are available.\n \n - **displayInverseHomeAwayTeams**: A boolean indicating if home and away teams are displayed inversely.\n \n - **matches**: An array of match objects, each containing:\n \n - **tournamentId**: The unique identifier for the tournament.\n \n - **id**: The unique identifier for the match.\n \n - **startTimestamp**: The start time of the match in timestamp format.\n \n - **detailId**: The detail identifier for the match.\n \n - **season**: An object with season details including:\n \n - **name**: The name of the season.\n \n - **year**: The year of the season.\n \n - **id**: The unique identifier for the season.\n \n - **roundInfo**: An object containing round information.\n \n - **status**: An object with status details including:\n \n - **code**: Status code.\n \n - **description**: Description of the status.\n \n - **type**: Type of status.\n \n - **statusTime**: An object detailing the status time.\n \n - **homeTeam**: An object containing details of the home team.\n \n - **homeScore**: An object with the current score of the home team.\n \n - **awayTeam**: An object containing details of the away team.\n \n - **awayScore**: An object with the current score of the away team.\n \n - **time**: An object detailing the match time.\n \n - **tournament**: An object with tournament details (similar to the tournament object above).\n \n\nThis structure allows clients to easily parse and display live match information, facilitating real-time updates for users.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Scheduled Matches > \## Get Match Schedule\ > \ > This endpoint retrieves the scheduled matches for a specific date in the football tournament calendar. The request allows users to specify a date to fetch all matches scheduled for that day.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Query Parameters\*\*:\ > \ > \- \`date\` (string, required): The date for which the match schedule is requested, formatted as \`YYYY-MM-DD\`.\ > \ > \ > \### Response Structure\ > \ > The response will return a JSON object containing the following fields:\ > \ > \- \`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 request status.\ > \ > \- \`response\` (array): An array of match schedules, where each match object includes:\ > \ > \- \`tournamentId\` (integer): The ID of the tournament.\ > \ > \- \`tournament\` (object): Details about the tournament, including:\ > \ > \- \`id\` (integer): Tournament ID.\ > \ > \- \`name\` (string): Name of the tournament.\ > \ > \- \`category\` (object): Category details including:\ > \ > \- \`name\` (string): Name of the category.\ > \ > \- \`id\` (integer): Category ID.\ > \ > \- \`country\` (object): Country details including:\ > \ > \- \`alpha2\` (string): Alpha-2 country code.\ > \ > \- \`alpha3\` (string): Alpha-3 country code.\ > \ > \- \`name\` (string): Name of the country.\ > \ > \- \`flag\` (string): URL or path to the country flag.\ > \ > \- \`matches\` (array): An array of match objects, where each match includes:\ > \ > \- \`id\` (integer): Unique match ID.\ > \ > \- \`startTimestamp\` (integer): The start time of the match in UNIX timestamp format.\ > \ > \- \`homeTeam\` (object): Details about the home team, including:\ > \ > \- \`name\` (string): Team name.\ > \ > \- \`shortName\` (string): Short name of the team.\ > \ > \- \`gender\` (string): Gender category of the team.\ > \ > \- \`country\` (object): Country details of the team.\ > \ > \- \`homeScore\` (object): Current score and breakdown of the home team's scoring.\ > \ > \- \`awayTeam\` (object): Details about the away team, structured similarly to \`homeTeam\`.\ > \ > \- \`awayScore\` (object): Current score and breakdown of the away team's scoring.\ > \ > \- \`time\` (object): Timing details including injury time.\ > \ > \- \`tournament\` (object): Tournament details associated with the match.\ > \ > \ > \### Example Response\ > \ > \`\`\` json\ > {\ > "status": true,\ > "statusCode": 0,\ > "message": "",\ > "response": \[\ > {\ > "tournamentId": 0,\ > "tournament": {\ > "id": 0,\ > "name": "",\ > "category": {\ > "name": "",\ > "id": 0,\ > "country": {\ > "alpha2": "",\ > "alpha3": "",\ > "name": ""\ > },\ > "flag": "",\ > "alpha2": ""\ > },\ > "details": {\ > "name": "",\ > "category": {\ > "name": "",\ > "id": 0,\ > "country": {\ > "alpha2": "",\ > "alpha3": "",\ > "name": ""\ > },\ > "flag": "",\ > "alpha2": ""\ > },\ > "hasPerformanceGraphFeature": true,\ > "id": 0,\ > "hasEventPlayerStatistics": true,\ > "displayInverseHomeAwayTeams": true\ > }\ > },\ > "matches": \[\ > {\ > "tournamentId": 0,\ > "id": 0,\ > "startTimestamp": 0,\ > "homeTeam": {\ > "name": "",\ > "shortName": "",\ > "gender": "",\ > "country": {\ > "alpha2": "",\ > "alpha3": "",\ > "name": ""\ > }\ > },\ > "homeScore": {\ > "current": 0,\ > "display": 0\ > },\ > "awayTeam": {\ > "name": "",\ > "shortName": "",\ > "gender": "",\ > "country": {\ > "alpha2": "",\ > "alpha3": "",\ > "name": ""\ > }\ > },\ > "awayScore": {\ > "current": 0,\ > "display": 0\ > },\ > "time": {\ > "injuryTime1": 0,\ > "injuryTime2": 0\ > }\ > }\ > ]\ > }\ > ]\ > }\ > \ > \`\`\` ````json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Matches"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/matches/schedule":{"get":{"tags":["Matches"],"summary":"Scheduled Matches","description":"## Get Match Schedule\n\nThis endpoint retrieves the scheduled matches for a specific date in the football tournament calendar. The request allows users to specify a date to fetch all matches scheduled for that day.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/matches/schedule`\n \n- **Query Parameters**:\n \n - `date` (string, required): The date for which the match schedule is requested, formatted as `YYYY-MM-DD`.\n \n\n### Response Structure\n\nThe response will return a JSON object containing the following fields:\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 request status.\n \n- `response` (array): An array of match schedules, where each match object includes:\n \n - `tournamentId` (integer): The ID of the tournament.\n \n - `tournament` (object): Details about the tournament, including:\n \n - `id` (integer): Tournament ID.\n \n - `name` (string): Name of the tournament.\n \n - `category` (object): Category details including:\n \n - `name` (string): Name of the category.\n \n - `id` (integer): Category ID.\n \n - `country` (object): Country details including:\n \n - `alpha2` (string): Alpha-2 country code.\n \n - `alpha3` (string): Alpha-3 country code.\n \n - `name` (string): Name of the country.\n \n - `flag` (string): URL or path to the country flag.\n \n - `matches` (array): An array of match objects, where each match includes:\n \n - `id` (integer): Unique match ID.\n \n - `startTimestamp` (integer): The start time of the match in UNIX timestamp format.\n \n - `homeTeam` (object): Details about the home team, including:\n \n - `name` (string): Team name.\n \n - `shortName` (string): Short name of the team.\n \n - `gender` (string): Gender category of the team.\n \n - `country` (object): Country details of the team.\n \n - `homeScore` (object): Current score and breakdown of the home team's scoring.\n \n - `awayTeam` (object): Details about the away team, structured similarly to `homeTeam`.\n \n - `awayScore` (object): Current score and breakdown of the away team's scoring.\n \n - `time` (object): Timing details including injury time.\n \n - `tournament` (object): Tournament details associated with the match.\n \n\n### Example Response\n\n``` json\n{\n \"status\": true,\n \"statusCode\": 0,\n \"message\": \"\",\n \"response\": [\n {\n \"tournamentId\": 0,\n \"tournament\": {\n \"id\": 0,\n \"name\": \"\",\n \"category\": {\n \"name\": \"\",\n \"id\": 0,\n \"country\": {\n \"alpha2\": \"\",\n \"alpha3\": \"\",\n \"name\": \"\"\n },\n \"flag\": \"\",\n \"alpha2\": \"\"\n },\n \"details\": {\n \"name\": \"\",\n \"category\": {\n \"name\": \"\",\n \"id\": 0,\n \"country\": {\n \"alpha2\": \"\",\n \"alpha3\": \"\",\n \"name\": \"\"\n },\n \"flag\": \"\",\n \"alpha2\": \"\"\n },\n \"hasPerformanceGraphFeature\": true,\n \"id\": 0,\n \"hasEventPlayerStatistics\": true,\n \"displayInverseHomeAwayTeams\": true\n }\n },\n \"matches\": [\n {\n \"tournamentId\": 0,\n \"id\": 0,\n \"startTimestamp\": 0,\n \"homeTeam\": {\n \"name\": \"\",\n \"shortName\": \"\",\n \"gender\": \"\",\n \"country\": {\n \"alpha2\": \"\",\n \"alpha3\": \"\",\n \"name\": \"\"\n }\n },\n \"homeScore\": {\n \"current\": 0,\n \"display\": 0\n },\n \"awayTeam\": {\n \"name\": \"\",\n \"shortName\": \"\",\n \"gender\": \"\",\n \"country\": {\n \"alpha2\": \"\",\n \"alpha3\": \"\",\n \"name\": \"\"\n }\n },\n \"awayScore\": {\n \"current\": 0,\n \"display\": 0\n },\n \"time\": {\n \"injuryTime1\": 0,\n \"injuryTime2\": 0\n }\n }\n ]\n }\n ]\n}\n\n ```","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"date","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ```` # 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"}}}}}}}}} ``` # Competitions ## Competitions Categories > \## Get Competition Categories\ > \ > This endpoint retrieves a list of competition categories in the football API. It allows users to access various categories associated with football competitions.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \### Response\ > \ > The response from this endpoint will be in JSON format and contains the following structure:\ > \ > \- \*\*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 request.\ > \ > \- \*\*response\*\* (array): An array of competition category objects, each containing:\ > \ > \- \*\*name\*\* (string): The name of the competition category.\ > \ > \- \*\*slug\*\* (string): A URL-friendly version of the category name.\ > \ > \- \*\*id\*\* (integer): A unique identifier for the category.\ > \ > \- \*\*flag\*\* (string): A URL or path to the flag associated with the category.\ > \ > \- \*\*alpha2\*\* (string): The two-letter country code associated with the category.\ > \ > \ > This endpoint does not require any request body, as it is a simple GET request to retrieve data. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competitions"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/categories":{"get":{"tags":["Competitions"],"summary":"Competitions Categories","description":"## Get Competition Categories\n\nThis endpoint retrieves a list of competition categories in the football API. It allows users to access various categories associated with football competitions.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/competitions/categories`\n \n\n### Response\n\nThe response from this endpoint will be in JSON format and contains the following structure:\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 request.\n \n- **response** (array): An array of competition category objects, each containing:\n \n - **name** (string): The name of the competition category.\n \n - **slug** (string): A URL-friendly version of the category name.\n \n - **id** (integer): A unique identifier for the category.\n \n - **flag** (string): A URL or path to the flag associated with the category.\n \n - **alpha2** (string): The two-letter country code associated with the category.\n \n\nThis endpoint does not require any request body, as it is a simple GET request to retrieve data.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Default Competitions > \## Get Competitions by Country\ > \ > This endpoint retrieves a list of football competitions based on the specified country.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Query Parameters\*\*:\ > \ > \- \`country\` (string): The country code for which to fetch the competitions. For example, \`ES\` for Spain.\ > \ > \ > \### Response\ > \ > The response will return a JSON object with the following structure:\ > \ > \- \*\*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\*\* (array): An array of competition objects, each containing:\ > \ > \- \*\*name\*\* (string): The name of the competition.\ > \ > \- \*\*category\*\* (object): An object containing details about the competition category:\ > \ > \- \*\*name\*\* (string): The name of the category.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the category.\ > \ > \- \*\*flag\*\* (string): The URL or path to the flag image associated with the category.\ > \ > \- \*\*alpha2\*\* (string): The two-letter country code for the category.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the competition.\ > \ > \- \*\*displayInverseHomeAwayTeams\*\* (boolean): A flag indicating whether to display teams in an inverse home/away format.\ > \ > \ > This endpoint is useful for applications that need to display or utilize information about football competitions in a specific country. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competitions"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/default":{"get":{"tags":["Competitions"],"summary":"Default Competitions","description":"## Get Competitions by Country\n\nThis endpoint retrieves a list of football competitions based on the specified country.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/football/api/v1/competitions/default`\n \n- **Query Parameters**:\n \n - `country` (string): The country code for which to fetch the competitions. For example, `ES` for Spain.\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): A code representing the status of the response.\n \n- **message** (string): A message providing additional information about the response.\n \n- **response** (array): An array of competition objects, each containing:\n \n - **name** (string): The name of the competition.\n \n - **category** (object): An object containing details about the competition category:\n \n - **name** (string): The name of the category.\n \n - **id** (integer): The unique identifier for the category.\n \n - **flag** (string): The URL or path to the flag image associated with the category.\n \n - **alpha2** (string): The two-letter country code for the category.\n \n - **id** (integer): The unique identifier for the competition.\n \n - **displayInverseHomeAwayTeams** (boolean): A flag indicating whether to display teams in an inverse home/away format.\n \n\nThis endpoint is useful for applications that need to display or utilize information about football competitions in a specific country.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"country","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Top Competitions > \## API Request Description\ > \ > \### Method\ > \ > \*\*GET\*\*\ > \ > \### Endpoint\ > \ > \` > \ > \### Query Parameters\ > \ > \- \*\*country\*\* (string): The country code for which to retrieve the top football competitions. In this example, the value is \`ES\` for Spain.\ > \ > \ > \### Expected Response Format\ > \ > The response will be in JSON format and includes 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\*\* (array): An array of objects containing details about the top competitions, where each object includes:\ > \ > \- \*\*name\*\* (string): The name of the competition.\ > \ > \- \*\*category\*\* (object): An object containing:\ > \ > \- \*\*name\*\* (string): The name of the category.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the category.\ > \ > \- \*\*flag\*\* (string): A URL or identifier for the category's flag.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the competition.\ > \ > \- \*\*displayInverseHomeAwayTeams\*\* (boolean): A flag indicating if the home and away teams should be displayed inversely.\ > \ > \ > This endpoint allows users to retrieve a list of the top football competitions for a specified country, along with relevant details about each competition. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competitions"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/top":{"get":{"tags":["Competitions"],"summary":"Top Competitions","description":"## API Request Description\n\n### Method\n\n**GET**\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/football/api/v1/competitions/top`\n\n### Query Parameters\n\n- **country** (string): The country code for which to retrieve the top football competitions. In this example, the value is `ES` for Spain.\n \n\n### Expected Response Format\n\nThe response will be in JSON format and includes 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** (array): An array of objects containing details about the top competitions, where each object includes:\n \n - **name** (string): The name of the competition.\n \n - **category** (object): An object containing:\n \n - **name** (string): The name of the category.\n \n - **id** (integer): The unique identifier for the category.\n \n - **flag** (string): A URL or identifier for the category's flag.\n \n - **id** (integer): The unique identifier for the competition.\n \n - **displayInverseHomeAwayTeams** (boolean): A flag indicating if the home and away teams should be displayed inversely.\n \n\nThis endpoint allows users to retrieve a list of the top football competitions for a specified country, along with relevant details about each competition.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"country","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` # Competition Details ## Competition Details > \## Endpoint Description\ > \ > This API endpoint retrieves detailed information about a specific football competition based on the provided tournament identifier (\`:tid\`).\ > \ > \### HTTP Method\ > \ > \`GET\`\ > \ > \### Endpoint\ > \ > \` > \ > \### Request Parameters\ > \ > \- \`:tid\` (Path Parameter): The unique identifier for the tournament you want to retrieve information for. This should be replaced with the actual tournament ID.\ > \ > \ > \### Response Fields\ > \ > \- \`status\`: Indicates the success of the request.\ > \ > \- \`statusCode\`: A numerical code representing the status of the response.\ > \ > \- \`message\`: Additional information about the response.\ > \ > \- \`response\`: Contains detailed information about the competition, including:\ > \ > \- \`name\`: Name of the competition.\ > \ > \- \`category\`: Details about the category of the competition.\ > \ > \- \`titleHolder\`: Information about the current title holder.\ > \ > \- \`mostTitlesTeams\`: Teams with the most titles in the competition.\ > \ > \- \`seasons\`: List of seasons associated with the competition.\ > \ > \- \`featuredMatch\`: Details of featured matches within the competition.\ > \ > \ > This endpoint provides comprehensive details about a specific football competition, including its structure, title holders, historical data, and current season information. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}":{"get":{"tags":["Competition Details"],"summary":"Competition Details","description":"## Endpoint Description\n\nThis API endpoint retrieves detailed information about a specific football competition based on the provided tournament identifier (`:tid`).\n\n### HTTP Method\n\n`GET`\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid`\n\n### Request Parameters\n\n- `:tid` (Path Parameter): The unique identifier for the tournament you want to retrieve information for. This should be replaced with the actual tournament ID.\n \n\n### Response Fields\n\n- `status`: Indicates the success of the request.\n \n- `statusCode`: A numerical code representing the status of the response.\n \n- `message`: Additional information about the response.\n \n- `response`: Contains detailed information about the competition, including:\n \n - `name`: Name of the competition.\n \n - `category`: Details about the category of the competition.\n \n - `titleHolder`: Information about the current title holder.\n \n - `mostTitlesTeams`: Teams with the most titles in the competition.\n \n - `seasons`: List of seasons associated with the competition.\n \n - `featuredMatch`: Details of featured matches within the competition.\n \n\nThis endpoint provides comprehensive details about a specific football competition, including its structure, title holders, historical data, and current season information.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Competition Featured > \## Endpoint Description\ > \ > This endpoint retrieves featured matches for a specific tournament in the football API. It allows users to access detailed information about ongoing or upcoming matches within a specified tournament.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \### Path Parameters\ > \ > \- \`:tid\` (required): The unique identifier for the tournament. This parameter specifies which tournament's featured matches are being requested.\ > \ > \ > \### Expected Response\ > \ > The response will return a JSON object containing 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 request status (if any).\ > \ > \- \*\*response\*\*: An array of featured match objects, each containing:\ > \ > \- \*\*tournamentId\*\*: The ID of the tournament.\ > \ > \- \*\*id\*\*: The unique ID of the match.\ > \ > \- \*\*startTimestamp\*\*: The start time of the match in Unix timestamp format.\ > \ > \- \*\*detailId\*\*: An identifier for detailed match information.\ > \ > \- \*\*season\*\*: An object containing:\ > \ > \- \*\*name\*\*: The name of the season.\ > \ > \- \*\*year\*\*: The year of the season.\ > \ > \- \*\*id\*\*: The ID of the season.\ > \ > \- \*\*roundInfo\*\*: An object providing details about the round:\ > \ > \- \*\*round\*\*: The round number.\ > \ > \- \*\*name\*\*: The name of the round.\ > \ > \- \*\*status\*\*: An object with match status details:\ > \ > \- \*\*code\*\*: The status code.\ > \ > \- \*\*description\*\*: A textual description of the status.\ > \ > \- \*\*type\*\*: The type of status.\ > \ > \- \*\*homeTeam\*\*: An object containing details about the home team, including:\ > \ > \- \*\*name\*\*: The name of the team.\ > \ > \- \*\*shortName\*\*: The abbreviated name of the team.\ > \ > \- \*\*gender\*\*: The gender category of the team.\ > \ > \- \*\*nameCode\*\*: The code used for the team's name.\ > \ > \- \*\*disabled\*\*: A boolean indicating if the team is disabled.\ > \ > \- \*\*national\*\*: A boolean indicating if the team is a national team.\ > \ > \- \*\*type\*\*: The type of team (e.g., club, national).\ > \ > \- \*\*id\*\*: The unique ID of the team.\ > \ > \- \*\*country\*\*: An object containing country details.\ > \ > \- \*\*subTeams\*\*: An array of sub-teams, if applicable.\ > \ > \- \*\*homeScore\*\*: An object containing aggregated score information for the home team.\ > \ > \- \*\*awayTeam\*\*: Similar structure as homeTeam, but for the away team.\ > \ > \- \*\*awayScore\*\*: An object containing aggregated score information for the away team.\ > \ > \- \*\*time\*\*: An object with timing information for the match.\ > \ > \- \*\*tournament\*\*: An object containing tournament details, including:\ > \ > \- \*\*id\*\*: The ID of the tournament.\ > \ > \- \*\*name\*\*: The name of the tournament.\ > \ > \- \*\*category\*\*: An object with category details.\ > \ > \- \*\*details\*\*: An object with additional tournament details.\ > \ > \ > \### Additional Notes\ > \ > \- Ensure that the \`:tid\` parameter is correctly replaced with a valid tournament ID to receive the appropriate data.\ > \ > \- The response may include multiple featured matches, depending on the tournament and its scheduling. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}/featured":{"get":{"tags":["Competition Details"],"summary":"Competition Featured","description":"## Endpoint Description\n\nThis endpoint retrieves featured matches for a specific tournament in the football API. It allows users to access detailed information about ongoing or upcoming matches within a specified tournament.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid/featured`\n \n\n### Path Parameters\n\n- `:tid` (required): The unique identifier for the tournament. This parameter specifies which tournament's featured matches are being requested.\n \n\n### Expected Response\n\nThe response will return a JSON object containing 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 request status (if any).\n \n- **response**: An array of featured match objects, each containing:\n \n - **tournamentId**: The ID of the tournament.\n \n - **id**: The unique ID of the match.\n \n - **startTimestamp**: The start time of the match in Unix timestamp format.\n \n - **detailId**: An identifier for detailed match information.\n \n - **season**: An object containing:\n \n - **name**: The name of the season.\n \n - **year**: The year of the season.\n \n - **id**: The ID of the season.\n \n - **roundInfo**: An object providing details about the round:\n \n - **round**: The round number.\n \n - **name**: The name of the round.\n \n - **status**: An object with match status details:\n \n - **code**: The status code.\n \n - **description**: A textual description of the status.\n \n - **type**: The type of status.\n \n - **homeTeam**: An object containing details about the home team, including:\n \n - **name**: The name of the team.\n \n - **shortName**: The abbreviated name of the team.\n \n - **gender**: The gender category of the team.\n \n - **nameCode**: The code used for the team's name.\n \n - **disabled**: A boolean indicating if the team is disabled.\n \n - **national**: A boolean indicating if the team is a national team.\n \n - **type**: The type of team (e.g., club, national).\n \n - **id**: The unique ID of the team.\n \n - **country**: An object containing country details.\n \n - **subTeams**: An array of sub-teams, if applicable.\n \n - **homeScore**: An object containing aggregated score information for the home team.\n \n - **awayTeam**: Similar structure as homeTeam, but for the away team.\n \n - **awayScore**: An object containing aggregated score information for the away team.\n \n - **time**: An object with timing information for the match.\n \n - **tournament**: An object containing tournament details, including:\n \n - **id**: The ID of the tournament.\n \n - **name**: The name of the tournament.\n \n - **category**: An object with category details.\n \n - **details**: An object with additional tournament details.\n \n\n### Additional Notes\n\n- Ensure that the `:tid` parameter is correctly replaced with a valid tournament ID to receive the appropriate data.\n \n- The response may include multiple featured matches, depending on the tournament and its scheduling.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Competition Season Info > \### Endpoint Description\ > \ > This endpoint retrieves detailed information about a specific football competition for a given season. It allows users to access various statistics related to the competition, including team performance metrics.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \#### Path Parameters\ > \ > \- \`:tid\` (string): The unique identifier for the tournament.\ > \ > \- \`:sid\` (string): The unique identifier for the season.\ > \ > \ > \### 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 related to the request status.\ > \ > \- \*\*response\*\* (object): Contains detailed statistics for the competition:\ > \ > \- \*\*goals\*\* (integer): Total number of goals scored.\ > \ > \- \*\*homeTeamWins\*\* (integer): Total number of wins by home teams.\ > \ > \- \*\*awayTeamWins\*\* (integer): Total number of wins by away teams.\ > \ > \- \*\*draws\*\* (integer): Total number of drawn matches.\ > \ > \- \*\*yellowCards\*\* (integer): Total number of yellow cards issued.\ > \ > \- \*\*redCards\*\* (integer): Total number of red cards issued.\ > \ > \- \*\*newcomersUpperDivision\*\* (array): List of newcomers in the upper division.\ > \ > \- \*\*newcomersLowerDivision\*\* (array): List of newcomers in the lower division.\ > \ > \- \*\*newcomersOther\*\* (array): List of newcomers in other divisions.\ > \ > \- \*\*numberOfCompetitors\*\* (integer): Total number of competitors in the competition.\ > \ > \- \*\*id\*\* (integer): Unique identifier for the competition.\ > \ > \- \*\*hostCountries\*\* (array): List of countries hosting the competition.\ > \ > \ > This structure allows clients to easily interpret the competition's performance and statistics for the specified season. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}/season/{sid}/info":{"get":{"tags":["Competition Details"],"summary":"Competition Season Info","description":"### Endpoint Description\n\nThis endpoint retrieves detailed information about a specific football competition for a given season. It allows users to access various statistics related to the competition, including team performance metrics.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid/season/:sid/info`\n \n\n#### Path Parameters\n\n- `:tid` (string): The unique identifier for the tournament.\n \n- `:sid` (string): The unique identifier for the season.\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 related to the request status.\n \n- **response** (object): Contains detailed statistics for the competition:\n \n - **goals** (integer): Total number of goals scored.\n \n - **homeTeamWins** (integer): Total number of wins by home teams.\n \n - **awayTeamWins** (integer): Total number of wins by away teams.\n \n - **draws** (integer): Total number of drawn matches.\n \n - **yellowCards** (integer): Total number of yellow cards issued.\n \n - **redCards** (integer): Total number of red cards issued.\n \n - **newcomersUpperDivision** (array): List of newcomers in the upper division.\n \n - **newcomersLowerDivision** (array): List of newcomers in the lower division.\n \n - **newcomersOther** (array): List of newcomers in other divisions.\n \n - **numberOfCompetitors** (integer): Total number of competitors in the competition.\n \n - **id** (integer): Unique identifier for the competition.\n \n - **hostCountries** (array): List of countries hosting the competition.\n \n\nThis structure allows clients to easily interpret the competition's performance and statistics for the specified season.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true},{"name":"sid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Competition Season Matches > \## Endpoint Description\ > \ > This endpoint retrieves a list of matches for a specific tournament and season in the football API. It provides detailed information about each match, including team details, scores, and tournament information.\ > \ > \### Request\ > \ > \*\*HTTP Method:\*\* GET \ > \*\*Endpoint:\*\* \` > \ > \#### Path Parameters\ > \ > \- \`:tid\` (Tournament ID): The unique identifier for the tournament.\ > \ > \- \`:sid\` (Season ID): The unique identifier for the season within the tournament.\ > \ > \ > \### Response\ > \ > The response will return a JSON object containing the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates the success of the request.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the request.\ > \ > \- \*\*message\*\* (string): A message providing additional information about the request.\ > \ > \- \*\*response\*\* (array): An array of match objects, each containing:\ > \ > \- \*\*tournamentId\*\* (integer): The ID of the tournament.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the match.\ > \ > \- \*\*startTimestamp\*\* (integer): The start time of the match in timestamp format.\ > \ > \- \*\*detailId\*\* (integer): An identifier for match details.\ > \ > \- \*\*season\*\* (object): Contains season information including:\ > \ > \- \*\*name\*\* (string): The name of the season.\ > \ > \- \*\*year\*\* (string): The year of the season.\ > \ > \- \*\*seasonCoverageInfo\*\* (object): Additional coverage information for the season.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the season.\ > \ > \- \*\*roundInfo\*\* (object): Information about the round of the match including:\ > \ > \- \*\*round\*\* (integer): The round number.\ > \ > \- \*\*name\*\* (string): The name of the round.\ > \ > \- \*\*status\*\* (object): Current status of the match including:\ > \ > \- \*\*code\*\* (integer): Status code.\ > \ > \- \*\*description\*\* (string): Description of the status.\ > \ > \- \*\*type\*\* (string): Type of status.\ > \ > \- \*\*homeTeam\*\* (object): Details of the home team including:\ > \ > \- \*\*name\*\*, \*\*shortName\*\*, \*\*gender\*\*, \*\*nameCode\*\*, \*\*disabled\*\*, \*\*national\*\*, \*\*type\*\*, \*\*id\*\*, \*\*country\*\* (object), \*\*subTeams\*\* (array).\ > \ > \- \*\*homeScore\*\* (object): Current score details for the home team including:\ > \ > \- \*\*current\*\*, \*\*display\*\*, \*\*period1\*\*, \*\*period2\*\*, \*\*normaltime\*\* (all integers).\ > \ > \- \*\*awayTeam\*\* (object): Details of the away team (same structure as homeTeam).\ > \ > \- \*\*awayScore\*\* (object): Current score details for the away team (same structure as homeScore).\ > \ > \- \*\*time\*\* (object): Information about the current period start timestamp.\ > \ > \- \*\*tournament\*\* (object): Information about the tournament including:\ > \ > \- \*\*id\*\*, \*\*name\*\*, \*\*category\*\* (object), \*\*details\*\* (object). ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}/season/{sid}/matches":{"get":{"tags":["Competition Details"],"summary":"Competition Season Matches","description":"## Endpoint Description\n\nThis endpoint retrieves a list of matches for a specific tournament and season in the football API. It provides detailed information about each match, including team details, scores, and tournament information.\n\n### Request\n\n**HTTP Method:** GET \n**Endpoint:** `https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid/season/:sid/matches`\n\n#### Path Parameters\n\n- `:tid` (Tournament ID): The unique identifier for the tournament.\n \n- `:sid` (Season ID): The unique identifier for the season within the tournament.\n \n\n### Response\n\nThe response will return a JSON object containing the following structure:\n\n- **status** (boolean): Indicates the success of the request.\n \n- **statusCode** (integer): A code representing the status of the request.\n \n- **message** (string): A message providing additional information about the request.\n \n- **response** (array): An array of match objects, each containing:\n \n - **tournamentId** (integer): The ID of the tournament.\n \n - **id** (integer): The unique identifier for the match.\n \n - **startTimestamp** (integer): The start time of the match in timestamp format.\n \n - **detailId** (integer): An identifier for match details.\n \n - **season** (object): Contains season information including:\n \n - **name** (string): The name of the season.\n \n - **year** (string): The year of the season.\n \n - **seasonCoverageInfo** (object): Additional coverage information for the season.\n \n - **id** (integer): The unique identifier for the season.\n \n - **roundInfo** (object): Information about the round of the match including:\n \n - **round** (integer): The round number.\n \n - **name** (string): The name of the round.\n \n - **status** (object): Current status of the match including:\n \n - **code** (integer): Status code.\n \n - **description** (string): Description of the status.\n \n - **type** (string): Type of status.\n \n - **homeTeam** (object): Details of the home team including:\n \n - **name**, **shortName**, **gender**, **nameCode**, **disabled**, **national**, **type**, **id**, **country** (object), **subTeams** (array).\n \n - **homeScore** (object): Current score details for the home team including:\n \n - **current**, **display**, **period1**, **period2**, **normaltime** (all integers).\n \n - **awayTeam** (object): Details of the away team (same structure as homeTeam).\n \n - **awayScore** (object): Current score details for the away team (same structure as homeScore).\n \n - **time** (object): Information about the current period start timestamp.\n \n - **tournament** (object): Information about the tournament including:\n \n - **id**, **name**, **category** (object), **details** (object).","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true},{"name":"sid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Competition Season Standings > \## Endpoint Description\ > \ > This endpoint retrieves the standings for a specific tournament and season in football. It provides detailed information about the teams participating in the tournament, including their performance metrics.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \#### Path Parameters\ > \ > \- \`:tid\` (Tournament ID): The unique identifier for the tournament whose standings are being requested.\ > \ > \- \`:sid\` (Season ID): The unique identifier for the season of the tournament.\ > \ > \ > \### Response\ > \ > The response is a JSON object containing the following structure:\ > \ > \- \`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.\ > \ > \- \`response\` (array): An array containing the standings for the specified tournament and season, structured as follows:\ > \ > \- \`id\` (integer): The unique identifier for the standings entry.\ > \ > \- \`type\` (string): The type of standings.\ > \ > \- \`name\` (string): The name of the standings.\ > \ > \- \`standings\` (array): An array of team standings, with each entry containing:\ > \ > \- \`team\` (object): Information about the team, including:\ > \ > \- \`name\` (string): The full name of the team.\ > \ > \- \`shortName\` (string): The abbreviated name of the team.\ > \ > \- \`gender\` (string): The gender category of the team.\ > \ > \- \`nameCode\` (string): A code representing the team name.\ > \ > \- \`disabled\` (boolean): Indicates if the team is disabled.\ > \ > \- \`national\` (boolean): Indicates if the team is a national team.\ > \ > \- \`type\` (integer): The type of team.\ > \ > \- \`id\` (integer): The unique identifier for the team.\ > \ > \- \`country\` (object): Information about the team's country, including:\ > \ > \- \`alpha2\` (string): The 2-letter country code.\ > \ > \- \`alpha3\` (string): The 3-letter country code.\ > \ > \- \`name\` (string): The name of the country.\ > \ > \- \`descriptions\` (array): Additional descriptions related to the team's standings.\ > \ > \- \`promotion\` (object): Information about promotion, including:\ > \ > \- \`text\` (string): Text related to promotion.\ > \ > \- \`id\` (integer): The identifier for the promotion.\ > \ > \- \`position\` (integer): The position of the team in the standings.\ > \ > \- \`matches\` (integer): The number of matches played.\ > \ > \- \`wins\` (integer): The number of wins.\ > \ > \- \`scoresFor\` (integer): The total scores for the team.\ > \ > \- \`scoresAgainst\` (integer): The total scores against the team.\ > \ > \- \`id\` (integer): The unique identifier for the standings entry.\ > \ > \- \`losses\` (integer): The number of losses.\ > \ > \- \`draws\` (integer): The number of draws.\ > \ > \- \`points\` (integer): The total points accumulated.\ > \ > \- \`scoreDiffFormatted\` (string): A formatted string representing the score difference.\ > \ > \- \`tournament\` (object): Information about the tournament, including:\ > \ > \- \`id\` (integer): The unique identifier for the tournament.\ > \ > \- \`name\` (string): The name of the tournament.\ > \ > \- \`category\` (object): Information about the category of the tournament, including:\ > \ > \- \`name\` (string): The name of the category.\ > \ > \- \`id\` (integer): The unique identifier for the category.\ > \ > \- \`country\` (object): Information about the country associated with the category.\ > \ > \- \`flag\` (string): The flag associated with the category.\ > \ > \- \`details\` (object): Additional details about the tournament, including:\ > \ > \- \`name\` (string): The name of the tournament details.\ > \ > \- \`category\` (object): The category information.\ > \ > \- \`hasPerformanceGraphFeature\` (boolean): Indicates if the tournament has a performance graph feature.\ > \ > \- \`id\` (integer): The unique identifier for the tournament details.\ > \ > \- \`country\` (object): Information about the country associated with the tournament.\ > \ > \- \`displayInverseHomeAwayTeams\` (boolean): Indicates if home and away teams should be displayed inversely.\ > \ > \- \`updatedAtTimestamp\` (integer): The timestamp of the last update for the standings.\ > \ > \ > This endpoint is essential for retrieving current standings and performance metrics for teams in a specified tournament and season. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}/season/{sid}/standings":{"get":{"tags":["Competition Details"],"summary":"Competition Season Standings","description":"## Endpoint Description\n\nThis endpoint retrieves the standings for a specific tournament and season in football. It provides detailed information about the teams participating in the tournament, including their performance metrics.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid/season/:sid/standings`\n \n\n#### Path Parameters\n\n- `:tid` (Tournament ID): The unique identifier for the tournament whose standings are being requested.\n \n- `:sid` (Season ID): The unique identifier for the season of the tournament.\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): The status code of the response.\n \n- `message` (string): A message providing additional information about the request.\n \n- `response` (array): An array containing the standings for the specified tournament and season, structured as follows:\n \n - `id` (integer): The unique identifier for the standings entry.\n \n - `type` (string): The type of standings.\n \n - `name` (string): The name of the standings.\n \n - `standings` (array): An array of team standings, with each entry containing:\n \n - `team` (object): Information about the team, including:\n \n - `name` (string): The full name of the team.\n \n - `shortName` (string): The abbreviated name of the team.\n \n - `gender` (string): The gender category of the team.\n \n - `nameCode` (string): A code representing the team name.\n \n - `disabled` (boolean): Indicates if the team is disabled.\n \n - `national` (boolean): Indicates if the team is a national team.\n \n - `type` (integer): The type of team.\n \n - `id` (integer): The unique identifier for the team.\n \n - `country` (object): Information about the team's country, including:\n \n - `alpha2` (string): The 2-letter country code.\n \n - `alpha3` (string): The 3-letter country code.\n \n - `name` (string): The name of the country.\n \n - `descriptions` (array): Additional descriptions related to the team's standings.\n \n - `promotion` (object): Information about promotion, including:\n \n - `text` (string): Text related to promotion.\n \n - `id` (integer): The identifier for the promotion.\n \n - `position` (integer): The position of the team in the standings.\n \n - `matches` (integer): The number of matches played.\n \n - `wins` (integer): The number of wins.\n \n - `scoresFor` (integer): The total scores for the team.\n \n - `scoresAgainst` (integer): The total scores against the team.\n \n - `id` (integer): The unique identifier for the standings entry.\n \n - `losses` (integer): The number of losses.\n \n - `draws` (integer): The number of draws.\n \n - `points` (integer): The total points accumulated.\n \n - `scoreDiffFormatted` (string): A formatted string representing the score difference.\n \n - `tournament` (object): Information about the tournament, including:\n \n - `id` (integer): The unique identifier for the tournament.\n \n - `name` (string): The name of the tournament.\n \n - `category` (object): Information about the category of the tournament, including:\n \n - `name` (string): The name of the category.\n \n - `id` (integer): The unique identifier for the category.\n \n - `country` (object): Information about the country associated with the category.\n \n - `flag` (string): The flag associated with the category.\n \n - `details` (object): Additional details about the tournament, including:\n \n - `name` (string): The name of the tournament details.\n \n - `category` (object): The category information.\n \n - `hasPerformanceGraphFeature` (boolean): Indicates if the tournament has a performance graph feature.\n \n - `id` (integer): The unique identifier for the tournament details.\n \n - `country` (object): Information about the country associated with the tournament.\n \n - `displayInverseHomeAwayTeams` (boolean): Indicates if home and away teams should be displayed inversely.\n \n - `updatedAtTimestamp` (integer): The timestamp of the last update for the standings.\n \n\nThis endpoint is essential for retrieving current standings and performance metrics for teams in a specified tournament and season.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true},{"name":"sid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Competition Season Top Players > \## Get Top Players by Competition and Season\ > \ > This endpoint retrieves a list of top players for a specific football competition and season.\ > \ > \### Request Method\ > \ > \`GET\`\ > \ > \### Endpoint\ > \ > \` > \ > \### Path Parameters\ > \ > \- \`:tid\` (string): The unique identifier for the football competition.\ > \ > \- \`:sid\` (string): The unique identifier for the season of the competition.\ > \ > \ > \### Expected Response Format\ > \ > On a successful request, the API will return a JSON object containing the top players for the specified competition and season. The response will include details such as player names, positions, and performance statistics. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}/season/{sid}/top-players":{"get":{"tags":["Competition Details"],"summary":"Competition Season Top Players","description":"## Get Top Players by Competition and Season\n\nThis endpoint retrieves a list of top players for a specific football competition and season.\n\n### Request Method\n\n`GET`\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid/season/:sid/top-players`\n\n### Path Parameters\n\n- `:tid` (string): The unique identifier for the football competition.\n \n- `:sid` (string): The unique identifier for the season of the competition.\n \n\n### Expected Response Format\n\nOn a successful request, the API will return a JSON object containing the top players for the specified competition and season. The response will include details such as player names, positions, and performance statistics.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true},{"name":"sid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Competition Season Top Teams > \## Get Top Teams in a Specific Competition Season\ > \ > This endpoint retrieves a list of top teams for a specified competition and season. It is useful for obtaining insights into the performance of teams within a particular league or tournament.\ > \ > \### Request Method\ > \ > \`GET\`\ > \ > \### Endpoint\ > \ > \` > \ > \### Path Parameters\ > \ > \- \`:tid\` (string): The unique identifier for the competition (e.g., league or tournament).\ > \ > \- \`:sid\` (string): The unique identifier for the season within the specified competition.\ > \ > \ > \### Expected Response Format\ > \ > The response will be in JSON format and will typically include:\ > \ > \- A list of top teams, each containing:\ > \ > \- \`teamId\`: The unique identifier for the team.\ > \ > \- \`teamName\`: The name of the team.\ > \ > \- \`points\`: The total points accumulated by the team in the specified season.\ > \ > \- \`matchesPlayed\`: The total number of matches played by the team.\ > \ > \ > \### Additional Notes\ > \ > \- Ensure that the values for \`:tid\` and \`:sid\` are valid to receive accurate results.\ > \ > \- This endpoint is particularly useful for sports analysts, fans, and developers looking to integrate team performance data into their applications. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}/season/{sid}/top-teams":{"get":{"tags":["Competition Details"],"summary":"Competition Season Top Teams","description":"## Get Top Teams in a Specific Competition Season\n\nThis endpoint retrieves a list of top teams for a specified competition and season. It is useful for obtaining insights into the performance of teams within a particular league or tournament.\n\n### Request Method\n\n`GET`\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid/season/:sid/top-teams`\n\n### Path Parameters\n\n- `:tid` (string): The unique identifier for the competition (e.g., league or tournament).\n \n- `:sid` (string): The unique identifier for the season within the specified competition.\n \n\n### Expected Response Format\n\nThe response will be in JSON format and will typically include:\n\n- A list of top teams, each containing:\n \n - `teamId`: The unique identifier for the team.\n \n - `teamName`: The name of the team.\n \n - `points`: The total points accumulated by the team in the specified season.\n \n - `matchesPlayed`: The total number of matches played by the team.\n \n\n### Additional Notes\n\n- Ensure that the values for `:tid` and `:sid` are valid to receive accurate results.\n \n- This endpoint is particularly useful for sports analysts, fans, and developers looking to integrate team performance data into their applications.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true},{"name":"sid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Competition Season Rounds > \## Get Competition Rounds\ > \ > This endpoint retrieves the rounds of a specific season for a given competition in football.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \ > \### Path Parameters\ > \ > \- \`:tid\` (string): The unique identifier for the competition.\ > \ > \- \`:sid\` (string): The unique identifier for the season.\ > \ > \ > \### Response Format\ > \ > The response will be in JSON format and includes the following fields:\ > \ > \- \`status\` (boolean): Indicates if the request was successful.\ > \ > \- \`statusCode\` (integer): The status code of the response.\ > \ > \- \`message\` (string): A message providing additional information about the request.\ > \ > \- \`response\` (array): An array of objects containing details about each round, where each object includes:\ > \ > \- \`round\` (integer): The round number.\ > \ > \- \`name\` (string): The name of the round.\ > \ > \- \`prefix\` (string): A prefix associated with the round.\ > \ > \- \`current\` (boolean): Indicates if this is the current round.\ > \ > \ > This endpoint is useful for obtaining the structure of competition rounds within a specified season. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}/season/{sid}/rounds":{"get":{"tags":["Competition Details"],"summary":"Competition Season Rounds","description":"## Get Competition Rounds\n\nThis endpoint retrieves the rounds of a specific season for a given competition in football.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid/season/:sid/rounds`\n \n\n### Path Parameters\n\n- `:tid` (string): The unique identifier for the competition.\n \n- `:sid` (string): The unique identifier for the season.\n \n\n### Response Format\n\nThe response will be in JSON format and includes the following fields:\n\n- `status` (boolean): Indicates if 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.\n \n- `response` (array): An array of objects containing details about each round, where each object includes:\n \n - `round` (integer): The round number.\n \n - `name` (string): The name of the round.\n \n - `prefix` (string): A prefix associated with the round.\n \n - `current` (boolean): Indicates if this is the current round.\n \n\nThis endpoint is useful for obtaining the structure of competition rounds within a specified season.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true},{"name":"sid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Competition Season Rounds Matches > \## Endpoint Description\ > \ > This API endpoint retrieves the matches for a specific round of a tournament in a given season. It provides detailed information about each match, including team details, scores, and tournament information.\ > \ > \### HTTP Method\ > \ > \`GET\`\ > \ > \### Endpoint\ > \ > \` > \ > \### URL Parameters\ > \ > \- \`:tid\` (Tournament ID): The unique identifier for the tournament.\ > \ > \- \`:sid\` (Season ID): The unique identifier for the season.\ > \ > \ > \### Expected Response Format\ > \ > The response will be a JSON object containing the following structure:\ > \ > \- \`status\` (boolean): Indicates the success of the request.\ > \ > \- \`statusCode\` (integer): A code representing the status of the response.\ > \ > \- \`message\` (string): A message providing additional context about the response.\ > \ > \- \`response\` (array): An array of match details for the specified round, each containing:\ > \ > \- \`round\` (integer): The round number.\ > \ > \- \`name\` (string): The name of the round.\ > \ > \- \`matches\` (array): An array of match objects, each with:\ > \ > \- \`tournamentId\` (integer): The ID of the tournament.\ > \ > \- \`id\` (integer): The unique identifier for the match.\ > \ > \- \`startTimestamp\` (integer): The timestamp when the match starts.\ > \ > \- \`detailId\` (integer): The ID for detailed match information.\ > \ > \- \`season\` (object): Contains season details including:\ > \ > \- \`name\` (string): The name of the season.\ > \ > \- \`year\` (integer): The year of the season.\ > \ > \- \`seasonCoverageInfo\` (object): Additional coverage information.\ > \ > \- \`id\` (integer): The ID of the season.\ > \ > \- \`roundInfo\` (object): Information about the round including:\ > \ > \- \`round\` (integer): The round number.\ > \ > \- \`name\` (string): The name of the round.\ > \ > \- \`status\` (object): Current status of the match including:\ > \ > \- \`code\` (integer): Status code.\ > \ > \- \`description\` (string): Description of the status.\ > \ > \- \`type\` (string): Type of status.\ > \ > \- \`homeTeam\` (object): Details about the home team, including:\ > \ > \- \`name\` (string): Team name.\ > \ > \- \`shortName\` (string): Short name of the team.\ > \ > \- \`gender\` (string): Gender category of the team.\ > \ > \- \`disabled\` (boolean): Indicates if the team is disabled.\ > \ > \- \`national\` (boolean): Indicates if the team is national.\ > \ > \- \`country\` (object): Country details of the team.\ > \ > \- \`homeScore\` (object): Current score details for the home team.\ > \ > \- \`awayTeam\` (object): Details about the away team (similar structure to \`homeTeam\`).\ > \ > \- \`awayScore\` (object): Current score details for the away team.\ > \ > \- \`time\` (object): Information about the current period of the match.\ > \ > \- \`tournament\` (object): Details about the tournament including:\ > \ > \- \`id\` (integer): Tournament ID.\ > \ > \- \`name\` (string): Name of the tournament.\ > \ > \- \`category\` (object): Category details of the tournament.\ > \ > \ > \### Additional Notes\ > \ > \- Ensure to replace \`:tid\` and \`:sid\` with the appropriate tournament and season IDs when making the request.\ > \ > \- The response will provide comprehensive details for each match, which can be useful for applications displaying match schedules or statistics. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Competition Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/competitions/{tid}/season/{sid}/rounds/matches":{"get":{"tags":["Competition Details"],"summary":"Competition Season Rounds Matches","description":"## Endpoint Description\n\nThis API endpoint retrieves the matches for a specific round of a tournament in a given season. It provides detailed information about each match, including team details, scores, and tournament information.\n\n### HTTP Method\n\n`GET`\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/football/api/v1/competitions/:tid/season/:sid/rounds/matches`\n\n### URL Parameters\n\n- `:tid` (Tournament ID): The unique identifier for the tournament.\n \n- `:sid` (Season ID): The unique identifier for the season.\n \n\n### Expected Response Format\n\nThe response will be a JSON object containing the following structure:\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 context about the response.\n \n- `response` (array): An array of match details for the specified round, each containing:\n \n - `round` (integer): The round number.\n \n - `name` (string): The name of the round.\n \n - `matches` (array): An array of match objects, each with:\n \n - `tournamentId` (integer): The ID of the tournament.\n \n - `id` (integer): The unique identifier for the match.\n \n - `startTimestamp` (integer): The timestamp when the match starts.\n \n - `detailId` (integer): The ID for detailed match information.\n \n - `season` (object): Contains season details including:\n \n - `name` (string): The name of the season.\n \n - `year` (integer): The year of the season.\n \n - `seasonCoverageInfo` (object): Additional coverage information.\n \n - `id` (integer): The ID of the season.\n \n - `roundInfo` (object): Information about the round including:\n \n - `round` (integer): The round number.\n \n - `name` (string): The name of the round.\n \n - `status` (object): Current status of the match including:\n \n - `code` (integer): Status code.\n \n - `description` (string): Description of the status.\n \n - `type` (string): Type of status.\n \n - `homeTeam` (object): Details about the home team, including:\n \n - `name` (string): Team name.\n \n - `shortName` (string): Short name of the team.\n \n - `gender` (string): Gender category of the team.\n \n - `disabled` (boolean): Indicates if the team is disabled.\n \n - `national` (boolean): Indicates if the team is national.\n \n - `country` (object): Country details of the team.\n \n - `homeScore` (object): Current score details for the home team.\n \n - `awayTeam` (object): Details about the away team (similar structure to `homeTeam`).\n \n - `awayScore` (object): Current score details for the away team.\n \n - `time` (object): Information about the current period of the match.\n \n - `tournament` (object): Details about the tournament including:\n \n - `id` (integer): Tournament ID.\n \n - `name` (string): Name of the tournament.\n \n - `category` (object): Category details of the tournament.\n \n\n### Additional Notes\n\n- Ensure to replace `:tid` and `:sid` with the appropriate tournament and season IDs when making the request.\n \n- The response will provide comprehensive details for each match, which can be useful for applications displaying match schedules or statistics.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true},{"name":"sid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` # Player Details ## Player Details > \## Get Player Details\ > \ > This endpoint retrieves detailed information about a specific football player based on their unique identifier (\`id\`).\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier of the player whose details are being requested.\ > \ > \ > \### Response\ > \ > The response will return a JSON object containing the following fields:\ > \ > \- \*\*status\*\*: Indicates the success of the request (boolean).\ > \ > \- \*\*statusCode\*\*: A code representing the status of the request (integer).\ > \ > \- \*\*message\*\*: A message providing additional information (string).\ > \ > \- \*\*response\*\*: An object containing detailed information about the player:\ > \ > \- \`id\`: The unique identifier of the player (integer).\ > \ > \- \`name\`: The full name of the player (string).\ > \ > \- \`shortName\`: The abbreviated name of the player (string).\ > \ > \- \`gender\`: The gender of the player (string).\ > \ > \- \`shirtNumber\`: The player's shirt number (integer).\ > \ > \- \`dateOfBirthTimestamp\`: The timestamp of the player's date of birth (integer).\ > \ > \- \`height\`: The height of the player in centimeters (integer).\ > \ > \- \`jerseyNumber\`: The jersey number worn by the player (string).\ > \ > \- \`position\`: The playing position of the player (string).\ > \ > \- \`preferredFoot\`: The player's preferred foot (string).\ > \ > \- \`country\`: An object containing details about the player's country:\ > \ > \- \`alpha2\`: The two-letter country code (string).\ > \ > \- \`alpha3\`: The three-letter country code (string).\ > \ > \- \`name\`: The name of the country (string).\ > \ > \- \`contractUntilTimestamp\`: The timestamp indicating until when the player is under contract (integer).\ > \ > \- \`proposedMarketValue\`: The proposed market value of the player (integer).\ > \ > \- \`team\`: An object containing details about the player's current team:\ > \ > \- \`name\`: The name of the team (string).\ > \ > \- \`shortName\`: The abbreviated name of the team (string).\ > \ > \- \`gender\`: The gender of the team (string).\ > \ > \- \`tournament\`: An object containing details about the tournament the team is participating in.\ > \ > \- \`isLive\`: Indicates if the team is currently active (boolean).\ > \ > \- \`id\`: The unique identifier of the team (integer).\ > \ > \- \`primaryUniqueTournament\`: An object containing details about the primary tournament associated with the player.\ > \ > \- \`about\`: Additional information about the player (string).\ > \ > \- \`nationalTeam\`: An array of objects representing the player's national team appearances, including:\ > \ > \- \`team\`: An object with details about the national team.\ > \ > \- \`appearances\`: The number of appearances for the national team (integer).\ > \ > \- \`goals\`: The number of goals scored for the national team (integer).\ > \ > \- \`debutTimestamp\`: The timestamp of the player's debut for the national team (integer).\ > \ > \- \`transferHistory\`: An array of objects detailing the player's transfer history, including:\ > \ > \- \`player\`: An object with details about the player.\ > \ > \- \`transferFrom\`: An object with details about the team the player transferred from.\ > \ > \- \`transferTo\`: An object with details about the team the player transferred to.\ > \ > \- \`fromTeamName\`: The name of the team the player transferred from (string).\ > \ > \- \`toTeamName\`: The name of the team the player transferred to (string).\ > \ > \- \`type\`: The type of transfer (integer).\ > \ > \- \`transferFee\`: The fee associated with the transfer (integer).\ > \ > \- \`transferFeeDescription\`: A description of the transfer fee (string).\ > \ > \- \`transferDateTimestamp\`: The timestamp of the transfer date (integer).\ > \ > \- \`transferFeeRaw\`: An object containing the raw transfer fee details.\ > \ > \ > \### Notes\ > \ > \- Ensure the \`id\` parameter is valid to retrieve the correct player details.\ > \ > \- The response will provide comprehensive information about the player, including their current team, national team contributions, and transfer history. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/{id}":{"get":{"tags":["Player Details"],"summary":"Player Details","description":"## Get Player Details\n\nThis endpoint retrieves detailed information about a specific football player based on their unique identifier (`id`).\n\n### Request\n\n- **Method**: GET\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/football/api/v1/player/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier of the player whose details are being requested.\n \n\n### Response\n\nThe response will return a JSON object containing the following fields:\n\n- **status**: Indicates the success of the request (boolean).\n \n- **statusCode**: A code representing the status of the request (integer).\n \n- **message**: A message providing additional information (string).\n \n- **response**: An object containing detailed information about the player:\n \n - `id`: The unique identifier of the player (integer).\n \n - `name`: The full name of the player (string).\n \n - `shortName`: The abbreviated name of the player (string).\n \n - `gender`: The gender of the player (string).\n \n - `shirtNumber`: The player's shirt number (integer).\n \n - `dateOfBirthTimestamp`: The timestamp of the player's date of birth (integer).\n \n - `height`: The height of the player in centimeters (integer).\n \n - `jerseyNumber`: The jersey number worn by the player (string).\n \n - `position`: The playing position of the player (string).\n \n - `preferredFoot`: The player's preferred foot (string).\n \n - `country`: An object containing details about the player's country:\n \n - `alpha2`: The two-letter country code (string).\n \n - `alpha3`: The three-letter country code (string).\n \n - `name`: The name of the country (string).\n \n - `contractUntilTimestamp`: The timestamp indicating until when the player is under contract (integer).\n \n - `proposedMarketValue`: The proposed market value of the player (integer).\n \n - `team`: An object containing details about the player's current team:\n \n - `name`: The name of the team (string).\n \n - `shortName`: The abbreviated name of the team (string).\n \n - `gender`: The gender of the team (string).\n \n - `tournament`: An object containing details about the tournament the team is participating in.\n \n - `isLive`: Indicates if the team is currently active (boolean).\n \n - `id`: The unique identifier of the team (integer).\n \n - `primaryUniqueTournament`: An object containing details about the primary tournament associated with the player.\n \n - `about`: Additional information about the player (string).\n \n - `nationalTeam`: An array of objects representing the player's national team appearances, including:\n \n - `team`: An object with details about the national team.\n \n - `appearances`: The number of appearances for the national team (integer).\n \n - `goals`: The number of goals scored for the national team (integer).\n \n - `debutTimestamp`: The timestamp of the player's debut for the national team (integer).\n \n - `transferHistory`: An array of objects detailing the player's transfer history, including:\n \n - `player`: An object with details about the player.\n \n - `transferFrom`: An object with details about the team the player transferred from.\n \n - `transferTo`: An object with details about the team the player transferred to.\n \n - `fromTeamName`: The name of the team the player transferred from (string).\n \n - `toTeamName`: The name of the team the player transferred to (string).\n \n - `type`: The type of transfer (integer).\n \n - `transferFee`: The fee associated with the transfer (integer).\n \n - `transferFeeDescription`: A description of the transfer fee (string).\n \n - `transferDateTimestamp`: The timestamp of the transfer date (integer).\n \n - `transferFeeRaw`: An object containing the raw transfer fee details.\n \n\n### Notes\n\n- Ensure the `id` parameter is valid to retrieve the correct player details.\n \n- The response will provide comprehensive information about the player, including their current team, national team contributions, and transfer history.","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"}}}}}}}}} ``` ## Player National Team Statistics > \## Get Player National Team Statistics\ > \ > This endpoint retrieves the national team statistics for a specific player identified by their unique ID.\ > \ > \### Request Method\ > \ > \*\*GET\*\*\ > \ > \### Endpoint\ > \ > \` > \ > \### Path Parameters\ > \ > \- \`id\` (required): The unique identifier of the player whose national team statistics are being requested.\ > \ > \ > \### Expected Response Format\ > \ > 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 context about the response.\ > \ > \- \*\*response\*\* (object): An object containing the player's national team statistics, which includes:\ > \ > \- \*\*team\*\* (object): Information about the national team, containing:\ > \ > \- \*\*name\*\* (string): The full name of the team.\ > \ > \- \*\*shortName\*\* (string): The abbreviated name of the team.\ > \ > \- \*\*gender\*\* (string): The gender category of the team.\ > \ > \- \*\*nameCode\*\* (string): The code representing the name of the team.\ > \ > \- \*\*ranking\*\* (integer): The current ranking of the national team.\ > \ > \- \*\*national\*\* (boolean): Indicates if the team is a national team.\ > \ > \- \*\*type\*\* (integer): The type of the team.\ > \ > \- \*\*id\*\* (integer): The unique identifier of the team.\ > \ > \- \*\*appearances\*\* (integer): The number of appearances the player has made for the national team.\ > \ > \- \*\*goals\*\* (integer): The total number of goals scored by the player for the national team.\ > \ > \- \*\*debutTimestamp\*\* (integer): The timestamp of the player's debut for the national team. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/national-team-statistics/{id}":{"get":{"tags":["Player Details"],"summary":"Player National Team Statistics","description":"## Get Player National Team Statistics\n\nThis endpoint retrieves the national team statistics for a specific player identified by their unique ID.\n\n### Request Method\n\n**GET**\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/football/api/v1/player/national-team-statistics/:id`\n\n### Path Parameters\n\n- `id` (required): The unique identifier of the player whose national team statistics are being requested.\n \n\n### Expected Response Format\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 context about the response.\n \n- **response** (object): An object containing the player's national team statistics, which includes:\n \n - **team** (object): Information about the national team, containing:\n \n - **name** (string): The full name of the team.\n \n - **shortName** (string): The abbreviated name of the team.\n \n - **gender** (string): The gender category of the team.\n \n - **nameCode** (string): The code representing the name of the team.\n \n - **ranking** (integer): The current ranking of the national team.\n \n - **national** (boolean): Indicates if the team is a national team.\n \n - **type** (integer): The type of the team.\n \n - **id** (integer): The unique identifier of the team.\n \n - **appearances** (integer): The number of appearances the player has made for the national team.\n \n - **goals** (integer): The total number of goals scored by the player for the national team.\n \n - **debutTimestamp** (integer): The timestamp of the player's debut for the national team.","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"}}}}}}}}} ``` ## Player Attribute Details > \## Endpoint Description\ > \ > This endpoint retrieves player attribute information for a specific player identified by their unique \`id\`. It provides insights into various attributes that define a player's performance, including attacking, technical, tactical, defending, and creativity skills.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier of the player whose attributes are being requested.\ > \ > \ > \### Response\ > \ > The response is a JSON object containing the following structure:\ > \ > \- \*\*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 request.\ > \ > \- \*\*response\*\*: An object containing two arrays:\ > \ > \- \*\*playerAttributeOverviews\*\*: An array of objects, each representing the attributes of the player. Each object contains:\ > \ > \- \`attacking\`: Numeric value representing the player's attacking skill.\ > \ > \- \`technical\`: Numeric value representing the player's technical skill.\ > \ > \- \`tactical\`: Numeric value representing the player's tactical skill.\ > \ > \- \`defending\`: Numeric value representing the player's defending skill.\ > \ > \- \`creativity\`: Numeric value representing the player's creativity skill.\ > \ > \- \`position\`: A string indicating the player's position on the field.\ > \ > \- \`yearShift\`: A numeric value indicating the year shift for the attributes.\ > \ > \- \`id\`: The unique identifier for the attribute overview.\ > \ > \- \*\*averageAttributeOverviews\*\*: An array similar to \`playerAttributeOverviews\`, but represents the average attributes across players.\ > \ > \ > This structure allows clients to easily interpret the player's attributes and compare them with average values. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/attribute/{id}":{"get":{"tags":["Player Details"],"summary":"Player Attribute Details","description":"## Endpoint Description\n\nThis endpoint retrieves player attribute information for a specific player identified by their unique `id`. It provides insights into various attributes that define a player's performance, including attacking, technical, tactical, defending, and creativity skills.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/player/attribute/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier of the player whose attributes are being requested.\n \n\n### Response\n\nThe response is a JSON object containing the following structure:\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 request.\n \n- **response**: An object containing two arrays:\n \n - **playerAttributeOverviews**: An array of objects, each representing the attributes of the player. Each object contains:\n \n - `attacking`: Numeric value representing the player's attacking skill.\n \n - `technical`: Numeric value representing the player's technical skill.\n \n - `tactical`: Numeric value representing the player's tactical skill.\n \n - `defending`: Numeric value representing the player's defending skill.\n \n - `creativity`: Numeric value representing the player's creativity skill.\n \n - `position`: A string indicating the player's position on the field.\n \n - `yearShift`: A numeric value indicating the year shift for the attributes.\n \n - `id`: The unique identifier for the attribute overview.\n \n - **averageAttributeOverviews**: An array similar to `playerAttributeOverviews`, but represents the average attributes across players.\n \n\nThis structure allows clients to easily interpret the player's attributes and compare them with average values.","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"}}}}}}}}} ``` ## Player Recent Matches > \### Endpoint Description\ > \ > This endpoint retrieves recent match details for a specific player identified by their unique ID.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier for the player whose recent matches are being queried.\ > \ > \ > \### Response\ > \ > The response will return 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\` (array): An array of match objects, each containing:\ > \ > \- \`tournamentId\` (integer): The ID of the tournament.\ > \ > \- \`id\` (integer): The unique ID of the match.\ > \ > \- \`startTimestamp\` (integer): The start time of the match in timestamp format.\ > \ > \- \`detailId\` (integer): The detail ID of the match.\ > \ > \- \`season\` (object): Contains information about the season (name, year, ID).\ > \ > \- \`roundInfo\` (object): Provides information about the round of the match.\ > \ > \- \`status\` (object): Contains status information (code, description, type).\ > \ > \- \`homeTeam\` (object): Contains details about the home team (name, short name, gender, etc.).\ > \ > \- \`homeScore\` (object): Contains the score details for the home team.\ > \ > \- \`awayTeam\` (object): Contains details about the away team (name, short name, gender, etc.).\ > \ > \- \`awayScore\` (object): Contains the score details for the away team.\ > \ > \- \`time\` (object): Contains information about the match timing, including injury time.\ > \ > \- \`tournament\` (object): Contains details about the tournament (ID, name, category, etc.).\ > \ > \ > \### Notes\ > \ > \- Ensure that the player ID provided in the request is valid to receive accurate match details.\ > \ > \- The response may include multiple match objects if the player has participated in several recent matches. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/recent/matches/{id}":{"get":{"tags":["Player Details"],"summary":"Player Recent Matches","description":"### Endpoint Description\n\nThis endpoint retrieves recent match details for a specific player identified by their unique ID.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/player/recent/matches/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier for the player whose recent matches are being queried.\n \n\n### Response\n\nThe response will return 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` (array): An array of match objects, each containing:\n \n - `tournamentId` (integer): The ID of the tournament.\n \n - `id` (integer): The unique ID of the match.\n \n - `startTimestamp` (integer): The start time of the match in timestamp format.\n \n - `detailId` (integer): The detail ID of the match.\n \n - `season` (object): Contains information about the season (name, year, ID).\n \n - `roundInfo` (object): Provides information about the round of the match.\n \n - `status` (object): Contains status information (code, description, type).\n \n - `homeTeam` (object): Contains details about the home team (name, short name, gender, etc.).\n \n - `homeScore` (object): Contains the score details for the home team.\n \n - `awayTeam` (object): Contains details about the away team (name, short name, gender, etc.).\n \n - `awayScore` (object): Contains the score details for the away team.\n \n - `time` (object): Contains information about the match timing, including injury time.\n \n - `tournament` (object): Contains details about the tournament (ID, name, category, etc.).\n \n\n### Notes\n\n- Ensure that the player ID provided in the request is valid to receive accurate match details.\n \n- The response may include multiple match objects if the player has participated in several recent matches.","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"}}}}}}}}} ``` ## Player Recent Summary > \### Endpoint Description\ > \ > This endpoint retrieves a summary of recent player performance based on the provided player ID. It is useful for obtaining quick insights into a player's recent activities and performance metrics in various tournaments.\ > \ > \### Request Format\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier for the player whose summary is being requested.\ > \ > \ > \### 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 following nested properties:\ > \ > \- \*\*summary\*\* (array): An array of objects, each representing a summary entry with:\ > \ > \- \*\*type\*\* (string): The type of summary entry.\ > \ > \- \*\*timestamp\*\* (integer): The time at which the summary entry was recorded.\ > \ > \- \*\*value\*\* (string): The value associated with the summary entry.\ > \ > \- \*\*uniqueTournamentId\*\* (integer): The unique identifier for the tournament related to the summary entry.\ > \ > \- \*\*uniqueTournamentsMap\*\* (object): A mapping of unique tournament IDs to their respective details, including:\ > \ > \- \*\*name\*\* (string): The name of the tournament.\ > \ > \- \*\*category\*\* (object): Contains details about the tournament category, including:\ > \ > \- \*\*name\*\* (string): The name of the category.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the category.\ > \ > \- \*\*flag\*\* (string): The flag associated with the category.\ > \ > \- \*\*alpha2\*\* (string, optional): The two-letter country code for the category (if applicable).\ > \ > \- \*\*id\*\* (integer): The unique identifier for the tournament.\ > \ > \- \*\*displayInverseHomeAwayTeams\*\* (boolean): Indicates whether to display home and away teams inversely. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/recent/summary/{id}":{"get":{"tags":["Player Details"],"summary":"Player Recent Summary","description":"### Endpoint Description\n\nThis endpoint retrieves a summary of recent player performance based on the provided player ID. It is useful for obtaining quick insights into a player's recent activities and performance metrics in various tournaments.\n\n### Request Format\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/player/recent/summary/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier for the player whose summary is being requested.\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 following nested properties:\n \n - **summary** (array): An array of objects, each representing a summary entry with:\n \n - **type** (string): The type of summary entry.\n \n - **timestamp** (integer): The time at which the summary entry was recorded.\n \n - **value** (string): The value associated with the summary entry.\n \n - **uniqueTournamentId** (integer): The unique identifier for the tournament related to the summary entry.\n \n - **uniqueTournamentsMap** (object): A mapping of unique tournament IDs to their respective details, including:\n \n - **name** (string): The name of the tournament.\n \n - **category** (object): Contains details about the tournament category, including:\n \n - **name** (string): The name of the category.\n \n - **id** (integer): The unique identifier for the category.\n \n - **flag** (string): The flag associated with the category.\n \n - **alpha2** (string, optional): The two-letter country code for the category (if applicable).\n \n - **id** (integer): The unique identifier for the tournament.\n \n - **displayInverseHomeAwayTeams** (boolean): Indicates whether to display home and away teams inversely.","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"}}}}}}}}} ``` ## Player Season Statistics > \### Get Player Season Statistics\ > \ > This endpoint retrieves the season statistics for a specific player identified by their unique ID. It provides detailed information about the tournaments the player participated in during the specified season.\ > \ > \#### Request Format\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*Endpoint:\*\* \` > \ > \- \*\*Path Parameter:\*\*\ > \ > \- \`id\` (required): The unique identifier for the player whose statistics are being requested.\ > \ > \ > \#### Response Structure\ > \ > The response is 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.\ > \ > \- \`response\` (array): An array containing the player's tournament statistics, with each element including:\ > \ > \- \`uniqueTournament\`: An object with tournament details:\ > \ > \- \`name\` (string): The name of the tournament.\ > \ > \- \`category\`: An object containing:\ > \ > \- \`name\` (string): The name of the category.\ > \ > \- \`id\` (integer): The unique identifier for the category.\ > \ > \- \`flag\` (string): The flag associated with the category.\ > \ > \- \`id\` (integer): The unique identifier for the tournament.\ > \ > \- \`displayInverseHomeAwayTeams\` (boolean): Indicates whether to display home and away teams inversely.\ > \ > \- \`seasons\` (array): An array of objects representing the seasons, each containing:\ > \ > \- \`name\` (string): The name of the season.\ > \ > \- \`year\` (string): The year of the season.\ > \ > \- \`id\` (integer): The unique identifier for the season. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/season/statistics/{id}":{"get":{"tags":["Player Details"],"summary":"Player Season Statistics","description":"### Get Player Season Statistics\n\nThis endpoint retrieves the season statistics for a specific player identified by their unique ID. It provides detailed information about the tournaments the player participated in during the specified season.\n\n#### Request Format\n\n- **Method:** GET\n \n- **Endpoint:** `https://apiv3.sportsapi360.com/football/api/v1/player/season/statistics/:id`\n \n- **Path Parameter:**\n \n - `id` (required): The unique identifier for the player whose statistics are being requested.\n \n\n#### Response Structure\n\nThe response is 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.\n \n- `response` (array): An array containing the player's tournament statistics, with each element including:\n \n - `uniqueTournament`: An object with tournament details:\n \n - `name` (string): The name of the tournament.\n \n - `category`: An object containing:\n \n - `name` (string): The name of the category.\n \n - `id` (integer): The unique identifier for the category.\n \n - `flag` (string): The flag associated with the category.\n \n - `id` (integer): The unique identifier for the tournament.\n \n - `displayInverseHomeAwayTeams` (boolean): Indicates whether to display home and away teams inversely.\n \n - `seasons` (array): An array of objects representing the seasons, each containing:\n \n - `name` (string): The name of the season.\n \n - `year` (string): The year of the season.\n \n - `id` (integer): The unique identifier for the season.","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"}}}}}}}}} ``` ## Player Statistics > \### Get Player Statistics\ > \ > This endpoint retrieves detailed statistics for a specific football player identified by their unique \`id\`.\ > \ > \#### Request Method\ > \ > \- \*\*GET\*\*\ > \ > \ > \#### Endpoint\ > \ > \- \` > \ > \ > \#### URL Parameters\ > \ > \- \`id\` (required): The unique identifier for the player whose statistics are being requested.\ > \ > \ > \#### Expected Response Format\ > \ > The response will return a JSON object containing the following structure:\ > \ > \- \*\*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\*\* (array): An array of player statistics objects, each containing:\ > \ > \- \*\*statistics\*\* (object): Detailed statistics for the player, including:\ > \ > \- \`accurateCrosses\`, \`accurateCrossesPercentage\`, \`accurateLongBalls\`, \`accurateLongBallsPercentage\`, \`accuratePasses\`, \`accuratePassesPercentage\`, \`aerialDuelsWon\`, \`assists\`, \`bigChancesCreated\`, \`bigChancesMissed\`, \`blockedShots\`, \`cleanSheet\`, \`dribbledPast\`, \`errorLeadToGoal\`, \`goals\`, \`goalsAssistsSum\`, \`goalsConceded\`, \`interceptions\`, \`keyPasses\`, \`minutesPlayed\`, \`passToAssist\`, \`rating\`, \`redCards\`, \`saves\`, \`shotsOnTarget\`, \`successfulDribbles\`, \`tackles\`, \`totalShots\`, \`yellowCards\`, \`totalRating\`, \`countRating\`, \`totalLongBalls\`, \`totalCross\`, \`totalPasses\`, \`shotsFromInsideTheBox\`, \`appearances\`, \`type\`, \`id\`.\ > \ > \- \*\*year\*\* (string): The year of the statistics.\ > \ > \- \*\*startYear\*\* (integer): The starting year of the statistics.\ > \ > \- \*\*endYear\*\* (integer): The ending year of the statistics.\ > \ > \- \*\*team\*\* (object): Information about the team, including:\ > \ > \- \`name\`, \`shortName\`, \`gender\`, \`nameCode\`, \`ranking\`, \`national\`, \`type\`, \`id\`.\ > \ > \- \*\*uniqueTournament\*\* (object): Details about the tournament, including:\ > \ > \- \`name\`, \`category\` (object with \`name\`, \`id\`, \`flag\`), \`id\`, \`displayInverseHomeAwayTeams\`, \`competitionType\`.\ > \ > \- \*\*season\*\* (object): Information about the season, including:\ > \ > \- \`name\`, \`year\`, \`id\`.\ > \ > \ > This endpoint is useful for obtaining comprehensive performance metrics for players in various football competitions. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/statistics/{id}":{"get":{"tags":["Player Details"],"summary":"Player Statistics","description":"### Get Player Statistics\n\nThis endpoint retrieves detailed statistics for a specific football player identified by their unique `id`.\n\n#### Request Method\n\n- **GET**\n \n\n#### Endpoint\n\n- `https://apiv3.sportsapi360.com/football/api/v1/player/statistics/:id`\n \n\n#### URL Parameters\n\n- `id` (required): The unique identifier for the player whose statistics are being requested.\n \n\n#### Expected Response Format\n\nThe response will return a JSON object containing the following structure:\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** (array): An array of player statistics objects, each containing:\n \n - **statistics** (object): Detailed statistics for the player, including:\n \n - `accurateCrosses`, `accurateCrossesPercentage`, `accurateLongBalls`, `accurateLongBallsPercentage`, `accuratePasses`, `accuratePassesPercentage`, `aerialDuelsWon`, `assists`, `bigChancesCreated`, `bigChancesMissed`, `blockedShots`, `cleanSheet`, `dribbledPast`, `errorLeadToGoal`, `goals`, `goalsAssistsSum`, `goalsConceded`, `interceptions`, `keyPasses`, `minutesPlayed`, `passToAssist`, `rating`, `redCards`, `saves`, `shotsOnTarget`, `successfulDribbles`, `tackles`, `totalShots`, `yellowCards`, `totalRating`, `countRating`, `totalLongBalls`, `totalCross`, `totalPasses`, `shotsFromInsideTheBox`, `appearances`, `type`, `id`.\n \n - **year** (string): The year of the statistics.\n \n - **startYear** (integer): The starting year of the statistics.\n \n - **endYear** (integer): The ending year of the statistics.\n \n - **team** (object): Information about the team, including:\n \n - `name`, `shortName`, `gender`, `nameCode`, `ranking`, `national`, `type`, `id`.\n \n - **uniqueTournament** (object): Details about the tournament, including:\n \n - `name`, `category` (object with `name`, `id`, `flag`), `id`, `displayInverseHomeAwayTeams`, `competitionType`.\n \n - **season** (object): Information about the season, including:\n \n - `name`, `year`, `id`.\n \n\nThis endpoint is useful for obtaining comprehensive performance metrics for players in various football competitions.","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"}}}}}}}}} ``` ## Player Transfer History > \### Endpoint Description\ > \ > This endpoint retrieves information about a specific player transfer in football by providing the player's unique identifier.\ > \ > \### Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*URL:\*\* \` > \ > \- \*\*Path Parameter:\*\*\ > \ > \- \`id\` (integer): The unique identifier of the player whose transfer details are being requested.\ > \ > \ > \### Response\ > \ > The response will return a JSON object containing the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates the success of the request.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the response.\ > \ > \- \*\*message\*\* (string): Any additional message regarding the request.\ > \ > \- \*\*response\*\* (array): An array containing transfer details for the player. Each object in the array includes:\ > \ > \- \*\*player\*\* (object): Information about the player involved in the transfer.\ > \ > \- \*\*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.\ > \ > \- \*\*sofascoreId\*\* (string): The unique identifier for the player in the SofaScore database.\ > \ > \- \*\*id\*\* (integer): The unique identifier of the player.\ > \ > \- \*\*transferFrom\*\* (object): Details about the team the player is transferring from.\ > \ > \- \*\*name\*\* (string): Name of the team.\ > \ > \- \*\*shortName\*\* (string): Abbreviated name of the team.\ > \ > \- \*\*gender\*\* (string): Gender of the team (if applicable).\ > \ > \- \*\*nameCode\*\* (string): Code representing the team name.\ > \ > \- \*\*disabled\*\* (boolean): Indicates if the team is disabled.\ > \ > \- \*\*national\*\* (boolean): Indicates if the team is a national team.\ > \ > \- \*\*type\*\* (integer): Type of the team.\ > \ > \- \*\*id\*\* (integer): Unique identifier of the team.\ > \ > \- \*\*transferTo\*\* (object): Details about the team the player is transferring to.\ > \ > \- Same structure as \`transferFrom\`.\ > \ > \- \*\*fromTeamName\*\* (string): The name of the team the player is leaving.\ > \ > \- \*\*toTeamName\*\* (string): The name of the team the player is joining.\ > \ > \- \*\*type\*\* (integer): The type of transfer.\ > \ > \- \*\*transferFee\*\* (float): The fee associated with the transfer.\ > \ > \- \*\*transferFeeDescription\*\* (string): Description of the transfer fee.\ > \ > \- \*\*id\*\* (integer): Unique identifier for the transfer record.\ > \ > \- \*\*transferDateTimestamp\*\* (integer): The timestamp of the transfer date.\ > \ > \- \*\*transferFeeRaw\*\* (object): Raw details of the transfer fee.\ > \ > \- \*\*value\*\* (float): The numerical value of the transfer fee.\ > \ > \- \*\*currency\*\* (string): The currency in which the transfer fee is denominated.\ > \ > \ > This endpoint is useful for obtaining detailed information about a player's transfer history, including the teams involved and financial details. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/transfer/{id}":{"get":{"tags":["Player Details"],"summary":"Player Transfer History","description":"### Endpoint Description\n\nThis endpoint retrieves information about a specific player transfer in football by providing the player's unique identifier.\n\n### Request\n\n- **Method:** GET\n \n- **URL:** `https://apiv3.sportsapi360.com/football/api/v1/player/transfer/:id`\n \n- **Path Parameter:**\n \n - `id` (integer): The unique identifier of the player whose transfer details are being requested.\n \n\n### Response\n\nThe response will return a JSON object containing the following structure:\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): Any additional message regarding the request.\n \n- **response** (array): An array containing transfer details for the player. Each object in the array includes:\n \n - **player** (object): Information about the player involved in the transfer.\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 - **sofascoreId** (string): The unique identifier for the player in the SofaScore database.\n \n - **id** (integer): The unique identifier of the player.\n \n - **transferFrom** (object): Details about the team the player is transferring from.\n \n - **name** (string): Name of the team.\n \n - **shortName** (string): Abbreviated name of the team.\n \n - **gender** (string): Gender of the team (if applicable).\n \n - **nameCode** (string): Code representing the team name.\n \n - **disabled** (boolean): Indicates if the team is disabled.\n \n - **national** (boolean): Indicates if the team is a national team.\n \n - **type** (integer): Type of the team.\n \n - **id** (integer): Unique identifier of the team.\n \n - **transferTo** (object): Details about the team the player is transferring to.\n \n - Same structure as `transferFrom`.\n \n - **fromTeamName** (string): The name of the team the player is leaving.\n \n - **toTeamName** (string): The name of the team the player is joining.\n \n - **type** (integer): The type of transfer.\n \n - **transferFee** (float): The fee associated with the transfer.\n \n - **transferFeeDescription** (string): Description of the transfer fee.\n \n - **id** (integer): Unique identifier for the transfer record.\n \n - **transferDateTimestamp** (integer): The timestamp of the transfer date.\n \n - **transferFeeRaw** (object): Raw details of the transfer fee.\n \n - **value** (float): The numerical value of the transfer fee.\n \n - **currency** (string): The currency in which the transfer fee is denominated.\n \n\nThis endpoint is useful for obtaining detailed information about a player's transfer history, including the teams involved and financial details.","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"}}}}}}}}} ``` ## Player Tournament Season Statistics > \## Get Player Tournament Season Statistics\ > \ > This endpoint retrieves the statistical data for a specific player in a given tournament and season. It provides detailed performance metrics that can be used for analysis or reporting purposes.\ > \ > \### Request Method\ > \ > \`GET\`\ > \ > \### Endpoint URL\ > \ > \` > \ > \### Request Parameters\ > \ > \- \`id\` (path parameter): The unique identifier of the player whose statistics are being requested.\ > \ > \- \`tid\` (path parameter): The unique identifier of the tournament for which the statistics are being fetched.\ > \ > \- \`sid\` (path parameter): The unique identifier of the season during which the statistics are recorded.\ > \ > \ > \### Additional Notes\ > \ > \- The \`status\` field indicates whether the request was successful.\ > \ > \- The \`statusCode\` provides further information about the request's outcome.\ > \ > \- The \`response\` object contains two main sections: \`statistics\`, which includes detailed performance metrics, and \`team\`, which provides information about the player's team. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Player Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/player/{id}/tournament/{tid}/season/{sid}/statistics":{"get":{"tags":["Player Details"],"summary":"Player Tournament Season Statistics","description":"## Get Player Tournament Season Statistics\n\nThis endpoint retrieves the statistical data for a specific player in a given tournament and season. It provides detailed performance metrics that can be used for analysis or reporting purposes.\n\n### Request Method\n\n`GET`\n\n### Endpoint URL\n\n`https://apiv3.sportsapi360.com/football/api/v1/player/:id/tournament/:tid/season/:sid/statistics`\n\n### Request Parameters\n\n- `id` (path parameter): The unique identifier of the player whose statistics are being requested.\n \n- `tid` (path parameter): The unique identifier of the tournament for which the statistics are being fetched.\n \n- `sid` (path parameter): The unique identifier of the season during which the statistics are recorded.\n \n\n### Additional Notes\n\n- The `status` field indicates whether the request was successful.\n \n- The `statusCode` provides further information about the request's outcome.\n \n- The `response` object contains two main sections: `statistics`, which includes detailed performance metrics, and `team`, which provides information about the player's team.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true},{"name":"tid","in":"path","schema":{"type":"integer"},"required":true},{"name":"sid","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` # Team Details ## Team Details > \## API Endpoint: Get Team Details\ > \ > \### Request Method\ > \ > \`GET\`\ > \ > \### Endpoint\ > \ > \` > \ > \### Parameters\ > \ > \- \`id\` (path parameter): The unique identifier of the team for which details are being requested.\ > \ > \ > \### Expected Response Format\ > \ > On a successful request, the API will return a JSON object with 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.\ > \ > \- \`response\` (object): Contains detailed information about the team, including:\ > \ > \- \`id\` (integer): The unique identifier of the team.\ > \ > \- \`name\` (string): The name of the team.\ > \ > \- \`shortName\` (string): The abbreviated name of the team.\ > \ > \- \`gender\` (string): The gender category of the team.\ > \ > \- \`fullName\` (string): The full name of the team.\ > \ > \- \`nameCode\` (string): The code representing the name of the team.\ > \ > \- \`ranking\` (string): The current ranking of the team.\ > \ > \- \`foundationDateTimestamp\` (integer): The timestamp of the team's foundation date.\ > \ > \- \`national\` (boolean): Indicates if the team is a national team.\ > \ > \- \`category\` (object): Information about the team category, including:\ > \ > \- \`name\` (string): The name of the category.\ > \ > \- \`id\` (integer): The unique identifier of the category.\ > \ > \- \`country\` (object): Details about the country associated with the category.\ > \ > \- \`alpha2\` (string): The two-letter country code.\ > \ > \- \`alpha3\` (string): The three-letter country code.\ > \ > \- \`name\` (string): The name of the country.\ > \ > \- \`flag\` (string): The URL of the country's flag.\ > \ > \- \`manager\` (object): Information about the team's manager, including:\ > \ > \- \`name\` (string): The name of the manager.\ > \ > \- \`shortName\` (string): The abbreviated name of the manager.\ > \ > \- \`id\` (integer): The unique identifier of the manager.\ > \ > \- \`country\` (object): Details about the country of the manager.\ > \ > \- \`venue\` (object): Information about the team's venue, including:\ > \ > \- \`city\` (object): Details about the city where the venue is located.\ > \ > \- \`venueCoordinates\` (object): The geographical coordinates of the venue.\ > \ > \- \`latitude\` (number): The latitude of the venue.\ > \ > \- \`longitude\` (number): The longitude of the venue.\ > \ > \- \`hidden\` (boolean): Indicates if the venue is hidden.\ > \ > \- \`name\` (string): The name of the venue.\ > \ > \- \`capacity\` (integer): The seating capacity of the venue.\ > \ > \- \`id\` (integer): The unique identifier of the venue.\ > \ > \- \`country\` (object): Details about the country where the venue is located.\ > \ > \- \`type\` (integer): The type of team.\ > \ > \- \`pregameForm\` (object): Information about the team's pregame form, including:\ > \ > \- \`avgRating\` (string): The average rating of the team.\ > \ > \- \`position\` (integer): The team's position.\ > \ > \- \`value\` (string): The value associated with the team's form.\ > \ > \- \`form\` (array): An array representing the team's recent form.\ > \ > \ > This endpoint provides comprehensive details about a specific football team based on the provided team ID. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Team Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/{id}":{"get":{"tags":["Team Details"],"summary":"Team Details","description":"## API Endpoint: Get Team Details\n\n### Request Method\n\n`GET`\n\n### Endpoint\n\n`https://apiv3.sportsapi360.com/football/api/v1/team/:id`\n\n### Parameters\n\n- `id` (path parameter): The unique identifier of the team for which details are being requested.\n \n\n### Expected Response Format\n\nOn a successful request, the API will return a JSON object with 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.\n \n- `response` (object): Contains detailed information about the team, including:\n \n - `id` (integer): The unique identifier of the team.\n \n - `name` (string): The name of the team.\n \n - `shortName` (string): The abbreviated name of the team.\n \n - `gender` (string): The gender category of the team.\n \n - `fullName` (string): The full name of the team.\n \n - `nameCode` (string): The code representing the name of the team.\n \n - `ranking` (string): The current ranking of the team.\n \n - `foundationDateTimestamp` (integer): The timestamp of the team's foundation date.\n \n - `national` (boolean): Indicates if the team is a national team.\n \n - `category` (object): Information about the team category, including:\n \n - `name` (string): The name of the category.\n \n - `id` (integer): The unique identifier of the category.\n \n - `country` (object): Details about the country associated with the category.\n \n - `alpha2` (string): The two-letter country code.\n \n - `alpha3` (string): The three-letter country code.\n \n - `name` (string): The name of the country.\n \n - `flag` (string): The URL of the country's flag.\n \n - `manager` (object): Information about the team's manager, including:\n \n - `name` (string): The name of the manager.\n \n - `shortName` (string): The abbreviated name of the manager.\n \n - `id` (integer): The unique identifier of the manager.\n \n - `country` (object): Details about the country of the manager.\n \n - `venue` (object): Information about the team's venue, including:\n \n - `city` (object): Details about the city where the venue is located.\n \n - `venueCoordinates` (object): The geographical coordinates of the venue.\n \n - `latitude` (number): The latitude of the venue.\n \n - `longitude` (number): The longitude of the venue.\n \n - `hidden` (boolean): Indicates if the venue is hidden.\n \n - `name` (string): The name of the venue.\n \n - `capacity` (integer): The seating capacity of the venue.\n \n - `id` (integer): The unique identifier of the venue.\n \n - `country` (object): Details about the country where the venue is located.\n \n - `type` (integer): The type of team.\n \n - `pregameForm` (object): Information about the team's pregame form, including:\n \n - `avgRating` (string): The average rating of the team.\n \n - `position` (integer): The team's position.\n \n - `value` (string): The value associated with the team's form.\n \n - `form` (array): An array representing the team's recent form.\n \n\nThis endpoint provides comprehensive details about a specific football team based on the provided team 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"}}}}}}}}} ``` ## Team Extended Details > \## Endpoint Description\ > \ > This endpoint retrieves detailed information about a specific football team based on the provided team ID.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\`: The unique identifier for the football team whose details are being requested.\ > \ > \ > \### Response\ > \ > The response will return a JSON object containing 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.\ > \ > \- \*\*response\*\*: An object containing detailed information about the team, which includes:\ > \ > \- \*\*id\*\*: The unique identifier of the team.\ > \ > \- \*\*name\*\*: The official name of the team.\ > \ > \- \*\*shortName\*\*: A shortened version of the team's name.\ > \ > \- \*\*gender\*\*: The gender category of the team (e.g., male, female).\ > \ > \- \*\*fullName\*\*: The full official name of the team.\ > \ > \- \*\*nameCode\*\*: A code representing the name of the team.\ > \ > \- \*\*ranking\*\*: The current ranking of the team.\ > \ > \- \*\*foundationDateTimestamp\*\*: The timestamp of when the team was founded.\ > \ > \- \*\*national\*\*: A boolean indicating if the team is a national team.\ > \ > \- \*\*category\*\*: An object providing details about the team's category, including:\ > \ > \- \*\*name\*\*: The name of the category.\ > \ > \- \*\*id\*\*: The unique identifier for the category.\ > \ > \- \*\*country\*\*: An object with country details, including:\ > \ > \- \*\*alpha2\*\*: The two-letter country code.\ > \ > \- \*\*alpha3\*\*: The three-letter country code.\ > \ > \- \*\*name\*\*: The name of the country.\ > \ > \- \*\*flag\*\*: The URL or path to the country's flag.\ > \ > \- \*\*alpha2\*\*: The two-letter country code again.\ > \ > \- \*\*manager\*\*: An object containing information about the team's manager, including:\ > \ > \- \*\*name\*\*: The name of the manager.\ > \ > \- \*\*shortName\*\*: A shortened version of the manager's name.\ > \ > \- \*\*id\*\*: The unique identifier for the manager.\ > \ > \- \*\*country\*\*: An object with country details similar to the team's category.\ > \ > \- \*\*venue\*\*: An object containing information about the team's venue, which includes:\ > \ > \- \*\*city\*\*: An object with the name of the city where the venue is located.\ > \ > \- \*\*venueCoordinates\*\*: An object with the latitude and longitude of the venue.\ > \ > \- \*\*hidden\*\*: A boolean indicating if the venue is hidden.\ > \ > \- \*\*name\*\*: The name of the venue.\ > \ > \- \*\*capacity\*\*: The seating capacity of the venue.\ > \ > \- \*\*id\*\*: The unique identifier for the venue.\ > \ > \- \*\*country\*\*: An object with country details similar to the team's category.\ > \ > \- \*\*stadium\*\*: An object containing stadium details, which includes:\ > \ > \- \*\*name\*\*: The name of the stadium.\ > \ > \- \*\*capacity\*\*: The seating capacity of the stadium.\ > \ > \- \*\*type\*\*: An integer representing the type of team.\ > \ > \- \*\*pregameForm\*\*: An object containing information about the team's pregame form, which includes:\ > \ > \- \*\*avgRating\*\*: The average rating of the team.\ > \ > \- \*\*position\*\*: The current position of the team.\ > \ > \- \*\*value\*\*: The value of the team.\ > \ > \- \*\*form\*\*: An array representing the team's recent form. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Team Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/details/{id}":{"get":{"tags":["Team Details"],"summary":"Team Extended Details","description":"## Endpoint Description\n\nThis endpoint retrieves detailed information about a specific football team based on the provided team ID.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/team/details/:id`\n \n- **Path Parameter**:\n \n - `id`: The unique identifier for the football team whose details are being requested.\n \n\n### Response\n\nThe response will return a JSON object containing 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.\n \n- **response**: An object containing detailed information about the team, which includes:\n \n - **id**: The unique identifier of the team.\n \n - **name**: The official name of the team.\n \n - **shortName**: A shortened version of the team's name.\n \n - **gender**: The gender category of the team (e.g., male, female).\n \n - **fullName**: The full official name of the team.\n \n - **nameCode**: A code representing the name of the team.\n \n - **ranking**: The current ranking of the team.\n \n - **foundationDateTimestamp**: The timestamp of when the team was founded.\n \n - **national**: A boolean indicating if the team is a national team.\n \n - **category**: An object providing details about the team's category, including:\n \n - **name**: The name of the category.\n \n - **id**: The unique identifier for the category.\n \n - **country**: An object with country details, including:\n \n - **alpha2**: The two-letter country code.\n \n - **alpha3**: The three-letter country code.\n \n - **name**: The name of the country.\n \n - **flag**: The URL or path to the country's flag.\n \n - **alpha2**: The two-letter country code again.\n \n - **manager**: An object containing information about the team's manager, including:\n \n - **name**: The name of the manager.\n \n - **shortName**: A shortened version of the manager's name.\n \n - **id**: The unique identifier for the manager.\n \n - **country**: An object with country details similar to the team's category.\n \n - **venue**: An object containing information about the team's venue, which includes:\n \n - **city**: An object with the name of the city where the venue is located.\n \n - **venueCoordinates**: An object with the latitude and longitude of the venue.\n \n - **hidden**: A boolean indicating if the venue is hidden.\n \n - **name**: The name of the venue.\n \n - **capacity**: The seating capacity of the venue.\n \n - **id**: The unique identifier for the venue.\n \n - **country**: An object with country details similar to the team's category.\n \n - **stadium**: An object containing stadium details, which includes:\n \n - **name**: The name of the stadium.\n \n - **capacity**: The seating capacity of the stadium.\n \n - **type**: An integer representing the type of team.\n \n - **pregameForm**: An object containing information about the team's pregame form, which includes:\n \n - **avgRating**: The average rating of the team.\n \n - **position**: The current position of the team.\n \n - **value**: The value of the team.\n \n - **form**: An array representing the team's recent form.","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"}}}}}}}}} ``` ## Team Tournaments > \### API Endpoint: Get Team Tournaments\ > \ > This endpoint retrieves the tournaments associated with a specific football team identified by its unique ID.\ > \ > \#### Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*URL:\*\* \` > \ > \- \*\*Path Parameter:\*\*\ > \ > \- \`id\` (required): The unique identifier of the football team for which the tournaments are being requested.\ > \ > \ > \#### Response\ > \ > The response will return a JSON object containing the following structure:\ > \ > \- \*\*status\*\* (boolean): Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the request (0 typically indicates success).\ > \ > \- \*\*message\*\* (string): A message providing additional information about the request status (may be empty).\ > \ > \- \*\*response\*\* (array): An array of tournament objects associated with the team, where each tournament object contains:\ > \ > \- \*\*name\*\* (string): The name of the tournament.\ > \ > \- \*\*category\*\* (object): An object providing details about the category of the tournament, which includes:\ > \ > \- \*\*name\*\* (string): The name of the category.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the category.\ > \ > \- \*\*flag\*\* (string): A URL or identifier for the category's flag.\ > \ > \- \*\*alpha2\*\* (string): The two-letter country code associated with the category.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the tournament.\ > \ > \- \*\*displayInverseHomeAwayTeams\*\* (boolean): A flag indicating whether to display home and away teams in an inverse order.\ > \ > \ > This endpoint is essential for applications that need to display tournament information for specific football teams, enabling users to view relevant competitions and their details. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Team Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/tournaments/{id}":{"get":{"tags":["Team Details"],"summary":"Team Tournaments","description":"### API Endpoint: Get Team Tournaments\n\nThis endpoint retrieves the tournaments associated with a specific football team identified by its unique ID.\n\n#### Request\n\n- **Method:** GET\n \n- **URL:** `https://apiv3.sportsapi360.com/football/api/v1/team/tournaments/:id`\n \n- **Path Parameter:**\n \n - `id` (required): The unique identifier of the football team for which the tournaments are being requested.\n \n\n#### Response\n\nThe response will return 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 request (0 typically indicates success).\n \n- **message** (string): A message providing additional information about the request status (may be empty).\n \n- **response** (array): An array of tournament objects associated with the team, where each tournament object contains:\n \n - **name** (string): The name of the tournament.\n \n - **category** (object): An object providing details about the category of the tournament, which includes:\n \n - **name** (string): The name of the category.\n \n - **id** (integer): The unique identifier for the category.\n \n - **flag** (string): A URL or identifier for the category's flag.\n \n - **alpha2** (string): The two-letter country code associated with the category.\n \n - **id** (integer): The unique identifier for the tournament.\n \n - **displayInverseHomeAwayTeams** (boolean): A flag indicating whether to display home and away teams in an inverse order.\n \n\nThis endpoint is essential for applications that need to display tournament information for specific football teams, enabling users to view relevant competitions and their details.","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"}}}}}}}}} ``` ## Team Recent Matches > \### Endpoint Description\ > \ > This endpoint retrieves the recent matches for a specific football team identified by the \`:id\` parameter. It provides detailed information about each match, including tournament details, team information, and scores.\ > \ > \### Request Format\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (integer): The unique identifier of the football team for which recent matches are being requested.\ > \ > \ > \### Response Structure\ > \ > The response is a JSON object that contains the following fields:\ > \ > \- \*\*status\*\* (boolean): Indicates whether the request was successful.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the response.\ > \ > \- \*\*message\*\* (string): A message providing additional information about the response.\ > \ > \- \*\*response\*\* (array): An array of match objects, each containing:\ > \ > \- \*\*tournamentId\*\* (integer): The unique identifier for the tournament.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the match.\ > \ > \- \*\*startTimestamp\*\* (integer): The timestamp when the match starts.\ > \ > \- \*\*detailId\*\* (integer): The unique identifier for match details.\ > \ > \- \*\*season\*\* (object): Contains details about the season:\ > \ > \- \*\*name\*\* (string): The name of the season.\ > \ > \- \*\*year\*\* (integer): The year of the season.\ > \ > \- \*\*seasonCoverageInfo\*\* (object): Additional coverage information for the season.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the season.\ > \ > \- \*\*roundInfo\*\* (object): Contains information about the match round:\ > \ > \- \*\*round\*\* (integer): The round number of the match.\ > \ > \- \*\*name\*\* (string): The name of the round.\ > \ > \- \*\*status\*\* (object): Contains the status of the match:\ > \ > \- \*\*code\*\* (integer): The status code of the match.\ > \ > \- \*\*description\*\* (string): A description of the match status.\ > \ > \- \*\*type\*\* (string): The type of the status.\ > \ > \- \*\*homeTeam\*\* (object): Information about the home team:\ > \ > \- \*\*name\*\* (string): The name of the home team.\ > \ > \- \*\*shortName\*\* (string): The short name of the home team.\ > \ > \- \*\*gender\*\* (string): The gender category of the home team.\ > \ > \- \*\*nameCode\*\* (string): The name code of the home team.\ > \ > \- \*\*disabled\*\* (boolean): Indicates if the team is disabled.\ > \ > \- \*\*national\*\* (boolean): Indicates if the team is a national team.\ > \ > \- \*\*type\*\* (integer): The type of team.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the home team.\ > \ > \- \*\*country\*\* (object): Contains country details:\ > \ > \- \*\*alpha2\*\* (string): The two-letter country code.\ > \ > \- \*\*alpha3\*\* (string): The three-letter country code.\ > \ > \- \*\*name\*\* (string): The name of the country.\ > \ > \- \*\*subTeams\*\* (array): An array of sub-teams.\ > \ > \- \*\*homeScore\*\* (object): Contains the score details for the home team:\ > \ > \- \*\*current\*\* (integer): The current score.\ > \ > \- \*\*display\*\* (integer): The displayed score.\ > \ > \- \*\*period1\*\* (integer): The score for the first period.\ > \ > \- \*\*period2\*\* (integer): The score for the second period.\ > \ > \- \*\*normaltime\*\* (integer): The score at normal time.\ > \ > \- \*\*awayTeam\*\* (object): Information about the away team (similar structure as homeTeam).\ > \ > \- \*\*awayScore\*\* (object): Contains the score details for the away team (similar structure as homeScore).\ > \ > \- \*\*time\*\* (object): Contains timing details for the match:\ > \ > \- \*\*injuryTime1\*\* (integer): Injury time for the first period.\ > \ > \- \*\*injuryTime2\*\* (integer): Injury time for the second period.\ > \ > \- \*\*currentPeriodStartTimestamp\*\* (integer): The timestamp for the start of the current period.\ > \ > \- \*\*tournament\*\* (object): Contains details about the tournament:\ > \ > \- \*\*id\*\* (integer): The unique identifier for the tournament.\ > \ > \- \*\*name\*\* (string): The name of the tournament.\ > \ > \- \*\*category\*\* (object): Contains category details:\ > \ > \- \*\*name\*\* (string): The name of the category.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the category.\ > \ > \- \*\*country\*\* (object): Country details associated with the category.\ > \ > \- \*\*flag\*\* (string): The flag associated with the category.\ > \ > \- \*\*details\*\* (object): Additional tournament details:\ > \ > \- \*\*name\*\* (string): The name of the tournament details.\ > \ > \- \*\*category\*\* (object): Category details (similar structure as above).\ > \ > \- \*\*hasPerformanceGraphFeature\*\* (boolean): Indicates if performance graph feature is available.\ > \ > \- \*\*id\*\* (integer): The unique identifier for the tournament details.\ > \ > \- \*\*country\*\* (object): Country details associated with the tournament.\ > \ > \- \*\*hasEventPlayerStatistics\*\* (boolean): Indicates if player statistics are available for events.\ > \ > \- \*\*displayInverseHomeAwayTeams\*\* (boolean): Indicates if home and away teams are displayed inversely. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Team Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/recent/matches/{id}":{"get":{"tags":["Team Details"],"summary":"Team Recent Matches","description":"### Endpoint Description\n\nThis endpoint retrieves the recent matches for a specific football team identified by the `:id` parameter. It provides detailed information about each match, including tournament details, team information, and scores.\n\n### Request Format\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/team/recent/matches/:id`\n \n- **Path Parameter**:\n \n - `id` (integer): The unique identifier of the football team for which recent matches are being requested.\n \n\n### Response Structure\n\nThe response is a JSON object that contains the following fields:\n\n- **status** (boolean): Indicates whether the request was successful.\n \n- **statusCode** (integer): A code representing the status of the response.\n \n- **message** (string): A message providing additional information about the response.\n \n- **response** (array): An array of match objects, each containing:\n \n - **tournamentId** (integer): The unique identifier for the tournament.\n \n - **id** (integer): The unique identifier for the match.\n \n - **startTimestamp** (integer): The timestamp when the match starts.\n \n - **detailId** (integer): The unique identifier for match details.\n \n - **season** (object): Contains details about the season:\n \n - **name** (string): The name of the season.\n \n - **year** (integer): The year of the season.\n \n - **seasonCoverageInfo** (object): Additional coverage information for the season.\n \n - **id** (integer): The unique identifier for the season.\n \n - **roundInfo** (object): Contains information about the match round:\n \n - **round** (integer): The round number of the match.\n \n - **name** (string): The name of the round.\n \n - **status** (object): Contains the status of the match:\n \n - **code** (integer): The status code of the match.\n \n - **description** (string): A description of the match status.\n \n - **type** (string): The type of the status.\n \n - **homeTeam** (object): Information about the home team:\n \n - **name** (string): The name of the home team.\n \n - **shortName** (string): The short name of the home team.\n \n - **gender** (string): The gender category of the home team.\n \n - **nameCode** (string): The name code of the home team.\n \n - **disabled** (boolean): Indicates if the team is disabled.\n \n - **national** (boolean): Indicates if the team is a national team.\n \n - **type** (integer): The type of team.\n \n - **id** (integer): The unique identifier for the home team.\n \n - **country** (object): Contains country details:\n \n - **alpha2** (string): The two-letter country code.\n \n - **alpha3** (string): The three-letter country code.\n \n - **name** (string): The name of the country.\n \n - **subTeams** (array): An array of sub-teams.\n \n - **homeScore** (object): Contains the score details for the home team:\n \n - **current** (integer): The current score.\n \n - **display** (integer): The displayed score.\n \n - **period1** (integer): The score for the first period.\n \n - **period2** (integer): The score for the second period.\n \n - **normaltime** (integer): The score at normal time.\n \n - **awayTeam** (object): Information about the away team (similar structure as homeTeam).\n \n - **awayScore** (object): Contains the score details for the away team (similar structure as homeScore).\n \n - **time** (object): Contains timing details for the match:\n \n - **injuryTime1** (integer): Injury time for the first period.\n \n - **injuryTime2** (integer): Injury time for the second period.\n \n - **currentPeriodStartTimestamp** (integer): The timestamp for the start of the current period.\n \n - **tournament** (object): Contains details about the tournament:\n \n - **id** (integer): The unique identifier for the tournament.\n \n - **name** (string): The name of the tournament.\n \n - **category** (object): Contains category details:\n \n - **name** (string): The name of the category.\n \n - **id** (integer): The unique identifier for the category.\n \n - **country** (object): Country details associated with the category.\n \n - **flag** (string): The flag associated with the category.\n \n - **details** (object): Additional tournament details:\n \n - **name** (string): The name of the tournament details.\n \n - **category** (object): Category details (similar structure as above).\n \n - **hasPerformanceGraphFeature** (boolean): Indicates if performance graph feature is available.\n \n - **id** (integer): The unique identifier for the tournament details.\n \n - **country** (object): Country details associated with the tournament.\n \n - **hasEventPlayerStatistics** (boolean): Indicates if player statistics are available for events.\n \n - **displayInverseHomeAwayTeams** (boolean): Indicates if home and away teams are displayed inversely.","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"}}}}}}}}} ``` ## Team Next Matches > \### Endpoint Description\ > \ > This endpoint retrieves the upcoming matches for a specific football team identified by the provided team ID.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier of the football team for which the next matches are being requested.\ > \ > \ > \### Response\ > \ > The response will return a JSON object containing the following fields:\ > \ > \- \`status\` (boolean): Indicates the success of the request.\ > \ > \- \`statusCode\` (integer): A code representing the status of the request.\ > \ > \- \`message\` (string): A message providing additional information about the request status.\ > \ > \- \`response\` (array): An array of upcoming match details, where each match object contains:\ > \ > \- \`tournamentId\` (integer): The ID of the tournament.\ > \ > \- \`id\` (integer): The unique identifier for the match.\ > \ > \- \`startTimestamp\` (integer): The start time of the match in timestamp format.\ > \ > \- \`detailId\` (integer): The detail ID for the match.\ > \ > \- \`season\` (object): Information about the season, including:\ > \ > \- \`name\` (string): The name of the season.\ > \ > \- \`year\` (integer): The year of the season.\ > \ > \- \`id\` (integer): The unique identifier for the season.\ > \ > \- \`status\` (object): The current status of the match, including:\ > \ > \- \`code\` (integer): Status code.\ > \ > \- \`description\` (string): Description of the status.\ > \ > \- \`type\` (string): Type of status.\ > \ > \- \`homeTeam\` (object): Information about the home team, including:\ > \ > \- \`name\` (string): The name of the team.\ > \ > \- \`shortName\` (string): The short name of the team.\ > \ > \- \`gender\` (string): Gender category of the team.\ > \ > \- \`nameCode\` (string): Code representing the team's name.\ > \ > \- \`disabled\` (boolean): Indicates if the team is disabled.\ > \ > \- \`national\` (boolean): Indicates if the team is a national team.\ > \ > \- \`type\` (integer): Type of team.\ > \ > \- \`id\` (integer): Unique identifier for the team.\ > \ > \- \`country\` (object): Country details of the team.\ > \ > \- \`homeScore\` (object): Score details for the home team.\ > \ > \- \`awayTeam\` (object): Information about the away team (similar structure to \`homeTeam\`).\ > \ > \- \`awayScore\` (object): Score details for the away team.\ > \ > \- \`time\` (object): Time details for the match.\ > \ > \- \`tournament\` (object): Information about the tournament, including:\ > \ > \- \`id\` (integer): Unique identifier for the tournament.\ > \ > \- \`name\` (string): Name of the tournament.\ > \ > \- \`category\` (object): Category details of the tournament.\ > \ > \- \`details\` (object): Additional details about the tournament.\ > \ > \ > \### Notes\ > \ > \- Ensure that the provided team ID corresponds to an existing team in the database to receive valid match information.\ > \ > \- The response may vary based on the availability of upcoming matches for the specified team. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Team Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/next/matches/{id}":{"get":{"tags":["Team Details"],"summary":"Team Next Matches","description":"### Endpoint Description\n\nThis endpoint retrieves the upcoming matches for a specific football team identified by the provided team ID.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/team/next/matches/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier of the football team for which the next matches are being requested.\n \n\n### Response\n\nThe response will return 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 request.\n \n- `message` (string): A message providing additional information about the request status.\n \n- `response` (array): An array of upcoming match details, where each match object contains:\n \n - `tournamentId` (integer): The ID of the tournament.\n \n - `id` (integer): The unique identifier for the match.\n \n - `startTimestamp` (integer): The start time of the match in timestamp format.\n \n - `detailId` (integer): The detail ID for the match.\n \n - `season` (object): Information about the season, including:\n \n - `name` (string): The name of the season.\n \n - `year` (integer): The year of the season.\n \n - `id` (integer): The unique identifier for the season.\n \n - `status` (object): The current status of the match, including:\n \n - `code` (integer): Status code.\n \n - `description` (string): Description of the status.\n \n - `type` (string): Type of status.\n \n - `homeTeam` (object): Information about the home team, including:\n \n - `name` (string): The name of the team.\n \n - `shortName` (string): The short name of the team.\n \n - `gender` (string): Gender category of the team.\n \n - `nameCode` (string): Code representing the team's name.\n \n - `disabled` (boolean): Indicates if the team is disabled.\n \n - `national` (boolean): Indicates if the team is a national team.\n \n - `type` (integer): Type of team.\n \n - `id` (integer): Unique identifier for the team.\n \n - `country` (object): Country details of the team.\n \n - `homeScore` (object): Score details for the home team.\n \n - `awayTeam` (object): Information about the away team (similar structure to `homeTeam`).\n \n - `awayScore` (object): Score details for the away team.\n \n - `time` (object): Time details for the match.\n \n - `tournament` (object): Information about the tournament, including:\n \n - `id` (integer): Unique identifier for the tournament.\n \n - `name` (string): Name of the tournament.\n \n - `category` (object): Category details of the tournament.\n \n - `details` (object): Additional details about the tournament.\n \n\n### Notes\n\n- Ensure that the provided team ID corresponds to an existing team in the database to receive valid match information.\n \n- The response may vary based on the availability of upcoming matches for the specified team.","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"}}}}}}}}} ``` ## Team Squads > \### Endpoint Description\ > \ > This endpoint retrieves the squad information for a specific football team identified by the team ID. It provides detailed data about the players within the squad, including their personal details and team affiliations.\ > \ > \### Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*URL:\*\* \` > \ > \- \*\*Path Parameter:\*\*\ > \ > \- \`id\` (required): The unique identifier of the team whose squad information is being requested.\ > \ > \ > \### Response Structure\ > \ > The response will return a JSON object containing the following fields:\ > \ > \- \*\*status\*\* (boolean): Indicates the success status of the request.\ > \ > \- \*\*statusCode\*\* (integer): A code representing the status of the request.\ > \ > \- \*\*message\*\* (string): A message providing additional information regarding the request status.\ > \ > \- \*\*response\*\* (array): An array containing the squad details, where each element represents a player with the following properties:\ > \ > \- \*\*name\*\* (string): The full name of the player.\ > \ > \- \*\*shortName\*\* (string): The abbreviated name of the player.\ > \ > \- \*\*team\*\* (object): Details about the team including:\ > \ > \- \*\*name\*\* (string): The name of the team.\ > \ > \- \*\*shortName\*\* (string): The abbreviated name of the team.\ > \ > \- \*\*gender\*\* (string): The gender category of the team.\ > \ > \- \*\*tournament\*\* (object): Information about the tournament the team is part of, including:\ > \ > \- \*\*name\*\* (string): The name of the tournament.\ > \ > \- \*\*category\*\* (object): Details about the category of the tournament.\ > \ > \- \*\*id\*\* (integer): The unique identifier of the tournament.\ > \ > \- \*\*country\*\* (object): Country details related to the tournament.\ > \ > \- \*\*flag\*\* (string): The flag associated with the tournament.\ > \ > \- \*\*alpha2\*\* (string): The two-letter country code.\ > \ > \- \*\*isLive\*\* (boolean): Indicates if the tournament is currently live.\ > \ > \- \*\*id\*\* (integer): The unique identifier of the team.\ > \ > \- \*\*primaryUniqueTournament\*\* (object): Details about the primary tournament associated with the player.\ > \ > \- \*\*nameCode\*\* (string): A code representing the player's name.\ > \ > \- \*\*disabled\*\* (boolean): Indicates if the player is currently disabled.\ > \ > \- \*\*national\*\* (boolean): Indicates if the player is a national team member.\ > \ > \- \*\*type\*\* (integer): The type of player (e.g., professional, amateur).\ > \ > \- \*\*id\*\* (integer): The unique identifier of the player.\ > \ > \- \*\*country\*\* (object): Country details related to 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.\ > \ > \- \*\*preferredFoot\*\* (string): The preferred foot of the player (e.g., left, right).\ > \ > \- \*\*deceased\*\* (boolean): Indicates if the player is deceased.\ > \ > \- \*\*gender\*\* (string): The gender of the player.\ > \ > \- \*\*sofascoreId\*\* (string): The unique identifier for the player in the SofaScore database.\ > \ > \- \*\*shirtNumber\*\* (integer): The shirt number of the player.\ > \ > \- \*\*dateOfBirthTimestamp\*\* (integer): The timestamp of the player's date of birth.\ > \ > \- \*\*contractUntilTimestamp\*\* (integer): The timestamp indicating until when the player's contract is valid.\ > \ > \- \*\*proposedMarketValue\*\* (integer): The proposed market value of the player.\ > \ > \- \*\*proposedMarketValueRaw\*\* (object): The raw market value details including:\ > \ > \- \*\*value\*\* (integer): The numeric value of the proposed market value.\ > \ > \- \*\*currency\*\* (string): The currency in which the market value is expressed. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Team Details"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/squads/{id}":{"get":{"tags":["Team Details"],"summary":"Team Squads","description":"### Endpoint Description\n\nThis endpoint retrieves the squad information for a specific football team identified by the team ID. It provides detailed data about the players within the squad, including their personal details and team affiliations.\n\n### Request\n\n- **Method:** GET\n \n- **URL:** `https://apiv3.sportsapi360.com/football/api/v1/team/squads/:id`\n \n- **Path Parameter:**\n \n - `id` (required): The unique identifier of the team whose squad information is being requested.\n \n\n### Response Structure\n\nThe response will return a JSON object containing the following fields:\n\n- **status** (boolean): Indicates the success status of the request.\n \n- **statusCode** (integer): A code representing the status of the request.\n \n- **message** (string): A message providing additional information regarding the request status.\n \n- **response** (array): An array containing the squad details, where each element represents a player with the following properties:\n \n - **name** (string): The full name of the player.\n \n - **shortName** (string): The abbreviated name of the player.\n \n - **team** (object): Details about the team including:\n \n - **name** (string): The name of the team.\n \n - **shortName** (string): The abbreviated name of the team.\n \n - **gender** (string): The gender category of the team.\n \n - **tournament** (object): Information about the tournament the team is part of, including:\n \n - **name** (string): The name of the tournament.\n \n - **category** (object): Details about the category of the tournament.\n \n - **id** (integer): The unique identifier of the tournament.\n \n - **country** (object): Country details related to the tournament.\n \n - **flag** (string): The flag associated with the tournament.\n \n - **alpha2** (string): The two-letter country code.\n \n - **isLive** (boolean): Indicates if the tournament is currently live.\n \n - **id** (integer): The unique identifier of the team.\n \n - **primaryUniqueTournament** (object): Details about the primary tournament associated with the player.\n \n - **nameCode** (string): A code representing the player's name.\n \n - **disabled** (boolean): Indicates if the player is currently disabled.\n \n - **national** (boolean): Indicates if the player is a national team member.\n \n - **type** (integer): The type of player (e.g., professional, amateur).\n \n - **id** (integer): The unique identifier of the player.\n \n - **country** (object): Country details related to 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 - **preferredFoot** (string): The preferred foot of the player (e.g., left, right).\n \n - **deceased** (boolean): Indicates if the player is deceased.\n \n - **gender** (string): The gender of the player.\n \n - **sofascoreId** (string): The unique identifier for the player in the SofaScore database.\n \n - **shirtNumber** (integer): The shirt number of the player.\n \n - **dateOfBirthTimestamp** (integer): The timestamp of the player's date of birth.\n \n - **contractUntilTimestamp** (integer): The timestamp indicating until when the player's contract is valid.\n \n - **proposedMarketValue** (integer): The proposed market value of the player.\n \n - **proposedMarketValueRaw** (object): The raw market value details including:\n \n - **value** (integer): The numeric value of the proposed market value.\n \n - **currency** (string): The currency in which the market value is expressed.","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"}}}}}}}}} ``` # Rankings ## Team FIFA Rankings > \## Endpoint Description\ > \ > This endpoint retrieves the FIFA rankings of football teams. It provides a list of teams along with their ranking details, which can be useful for applications that need to display or analyze current football team standings.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \### Response\ > \ > The response is a JSON object containing the following structure:\ > \ > \- \*\*rankings\*\*: An array of objects, each representing a team's ranking information.\ > \ > \- \*\*team\*\*: An object containing details about the team.\ > \ > \- \*\*name\*\*: The full name of the team.\ > \ > \- \*\*shortName\*\*: The abbreviated name of the team.\ > \ > \- \*\*gender\*\*: The gender category of the team.\ > \ > \- \*\*nameCode\*\*: A code representing the team's name.\ > \ > \- \*\*ranking\*\*: The current ranking of the team.\ > \ > \- \*\*disabled\*\*: A boolean indicating if the team is disabled.\ > \ > \- \*\*national\*\*: A boolean indicating if the team is a national team.\ > \ > \- \*\*type\*\*: The type of team (e.g., national, club).\ > \ > \- \*\*id\*\*: A unique identifier for the team.\ > \ > \- \*\*country\*\*: An object containing country information.\ > \ > \- \*\*alpha2\*\*: The two-letter country code.\ > \ > \- \*\*alpha3\*\*: The three-letter country code.\ > \ > \- \*\*name\*\*: The name of the country.\ > \ > \- \*\*type\*\*: The type of ranking.\ > \ > \- \*\*rowName\*\*: The name of the row in the ranking.\ > \ > \- \*\*ranking\*\*: The current ranking position.\ > \ > \- \*\*points\*\*: The points accumulated by the team.\ > \ > \- \*\*previousRanking\*\*: The team's ranking in the previous update.\ > \ > \- \*\*previousPoints\*\*: The points the team had in the previous update.\ > \ > \- \*\*id\*\*: A unique identifier for the ranking entry.\ > \ > \- \*\*country\*\*: An object representing country details (may be empty).\ > \ > \- \*\*rankingClass\*\*: The classification of the ranking.\ > \ > \- \*\*updatedAtTimestamp\*\*: A timestamp indicating when the rankings were last updated.\ > \ > \ > This endpoint does not require any request body, and it provides a comprehensive overview of the current FIFA rankings for football teams. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Rankings"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/rankings/fifa":{"get":{"tags":["Rankings"],"summary":"Team FIFA Rankings","description":"## Endpoint Description\n\nThis endpoint retrieves the FIFA rankings of football teams. It provides a list of teams along with their ranking details, which can be useful for applications that need to display or analyze current football team standings.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/team/rankings/fifa`\n \n\n### Response\n\nThe response is a JSON object containing the following structure:\n\n- **rankings**: An array of objects, each representing a team's ranking information.\n \n - **team**: An object containing details about the team.\n \n - **name**: The full name of the team.\n \n - **shortName**: The abbreviated name of the team.\n \n - **gender**: The gender category of the team.\n \n - **nameCode**: A code representing the team's name.\n \n - **ranking**: The current ranking of the team.\n \n - **disabled**: A boolean indicating if the team is disabled.\n \n - **national**: A boolean indicating if the team is a national team.\n \n - **type**: The type of team (e.g., national, club).\n \n - **id**: A unique identifier for the team.\n \n - **country**: An object containing country information.\n \n - **alpha2**: The two-letter country code.\n \n - **alpha3**: The three-letter country code.\n \n - **name**: The name of the country.\n \n - **type**: The type of ranking.\n \n - **rowName**: The name of the row in the ranking.\n \n - **ranking**: The current ranking position.\n \n - **points**: The points accumulated by the team.\n \n - **previousRanking**: The team's ranking in the previous update.\n \n - **previousPoints**: The points the team had in the previous update.\n \n - **id**: A unique identifier for the ranking entry.\n \n - **country**: An object representing country details (may be empty).\n \n - **rankingClass**: The classification of the ranking.\n \n- **updatedAtTimestamp**: A timestamp indicating when the rankings were last updated.\n \n\nThis endpoint does not require any request body, and it provides a comprehensive overview of the current FIFA rankings for football teams.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Team UEFA National Rankings > \## Endpoint Description\ > \ > This endpoint retrieves the UEFA national team rankings for football. It provides information about the rankings of national teams participating in UEFA tournaments.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \### Response\ > \ > The response will contain a JSON object with the following structure:\ > \ > \- \*\*rankings\*\*: An array of ranking objects, each containing:\ > \ > \- \*\*tournament\*\*: An object representing the tournament details, including:\ > \ > \- \*\*name\*\*: The name of the tournament.\ > \ > \- \*\*category\*\*: An object with details about the category, including:\ > \ > \- \*\*name\*\*: The name of the category.\ > \ > \- \*\*id\*\*: The unique identifier for the category.\ > \ > \- \*\*country\*\*: An object containing country details, including:\ > \ > \- \*\*alpha2\*\*: The two-letter country code.\ > \ > \- \*\*alpha3\*\*: The three-letter country code.\ > \ > \- \*\*name\*\*: The name of the country.\ > \ > \- \*\*flag\*\*: The flag associated with the country.\ > \ > \- \*\*id\*\*: The unique identifier for the tournament.\ > \ > \- \*\*displayInverseHomeAwayTeams\*\*: A boolean indicating if home/away teams should be displayed inversely.\ > \ > \- \*\*totalTeams\*\*: The total number of teams in the tournament.\ > \ > \- \*\*playingTeams\*\*: The number of teams currently playing.\ > \ > \- \*\*year\*\*: The year of the ranking.\ > \ > \- \*\*type\*\*: An integer representing the type of ranking.\ > \ > \- \*\*rowName\*\*: The name of the row in the ranking.\ > \ > \- \*\*ranking\*\*: The ranking position of the team.\ > \ > \- \*\*points\*\*: The points accumulated by the team.\ > \ > \- \*\*id\*\*: The unique identifier for the ranking.\ > \ > \- \*\*country\*\*: An object with country details similar to the tournament's country object.\ > \ > \- \*\*rankingClass\*\*: A classification for the ranking.\ > \ > \- \*\*updatedAtTimestamp\*\*: A timestamp indicating when the rankings were last updated.\ > \ > \ > \### Notes\ > \ > \- Ensure that the base URL is correctly set before making the request.\ > \ > \- The rankings may vary based on the latest updates from UEFA. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Rankings"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/rankings/uefa/national":{"get":{"tags":["Rankings"],"summary":"Team UEFA National Rankings","description":"## Endpoint Description\n\nThis endpoint retrieves the UEFA national team rankings for football. It provides information about the rankings of national teams participating in UEFA tournaments.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/team/rankings/uefa/national`\n \n\n### Response\n\nThe response will contain a JSON object with the following structure:\n\n- **rankings**: An array of ranking objects, each containing:\n \n - **tournament**: An object representing the tournament details, including:\n \n - **name**: The name of the tournament.\n \n - **category**: An object with details about the category, including:\n \n - **name**: The name of the category.\n \n - **id**: The unique identifier for the category.\n \n - **country**: An object containing country details, including:\n \n - **alpha2**: The two-letter country code.\n \n - **alpha3**: The three-letter country code.\n \n - **name**: The name of the country.\n \n - **flag**: The flag associated with the country.\n \n - **id**: The unique identifier for the tournament.\n \n - **displayInverseHomeAwayTeams**: A boolean indicating if home/away teams should be displayed inversely.\n \n - **totalTeams**: The total number of teams in the tournament.\n \n - **playingTeams**: The number of teams currently playing.\n \n - **year**: The year of the ranking.\n \n - **type**: An integer representing the type of ranking.\n \n - **rowName**: The name of the row in the ranking.\n \n - **ranking**: The ranking position of the team.\n \n - **points**: The points accumulated by the team.\n \n - **id**: The unique identifier for the ranking.\n \n - **country**: An object with country details similar to the tournament's country object.\n \n - **rankingClass**: A classification for the ranking.\n \n- **updatedAtTimestamp**: A timestamp indicating when the rankings were last updated.\n \n\n### Notes\n\n- Ensure that the base URL is correctly set before making the request.\n \n- The rankings may vary based on the latest updates from UEFA.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` ## Team UEFA Club Rankings > \### Endpoint Description\ > \ > This endpoint retrieves the UEFA club rankings for football teams. It provides a comprehensive list of teams along with their respective rankings, points, and associated metadata.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \### Response Structure\ > \ > The response will return a JSON object containing the following fields:\ > \ > \- \*\*rankings\*\*: An array of ranking objects, each representing a football team with the following properties:\ > \ > \- \*\*team\*\*: An object containing details about the team:\ > \ > \- \*\*name\*\*: The full name of the team.\ > \ > \- \*\*shortName\*\*: The abbreviated name of the team.\ > \ > \- \*\*gender\*\*: The gender category of the team.\ > \ > \- \*\*nameCode\*\*: A code representing the team's name.\ > \ > \- \*\*disabled\*\*: A boolean indicating if the team is disabled.\ > \ > \- \*\*national\*\*: A boolean indicating if the team is a national team.\ > \ > \- \*\*type\*\*: An integer representing the type of team.\ > \ > \- \*\*id\*\*: The unique identifier for the team.\ > \ > \- \*\*country\*\*: An object containing country details:\ > \ > \- \*\*alpha2\*\*: The 2-letter country code.\ > \ > \- \*\*alpha3\*\*: The 3-letter country code.\ > \ > \- \*\*name\*\*: The name of the country.\ > \ > \- \*\*year\*\*: The year for which the ranking is applicable.\ > \ > \- \*\*type\*\*: An integer representing the type of ranking.\ > \ > \- \*\*rowName\*\*: The name of the row in the ranking.\ > \ > \- \*\*ranking\*\*: The rank of the team.\ > \ > \- \*\*points\*\*: The points accumulated by the team.\ > \ > \- \*\*id\*\*: The unique identifier for the ranking entry.\ > \ > \- \*\*country\*\*: An object representing additional country details.\ > \ > \- \*\*rankingClass\*\*: A string representing the classification of the ranking.\ > \ > \- \*\*updatedAtTimestamp\*\*: A timestamp indicating when the rankings were last updated. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Rankings"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/team/rankings/uefa/club":{"get":{"tags":["Rankings"],"summary":"Team UEFA Club Rankings","description":"### Endpoint Description\n\nThis endpoint retrieves the UEFA club rankings for football teams. It provides a comprehensive list of teams along with their respective rankings, points, and associated metadata.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/team/rankings/uefa/club`\n \n\n### Response Structure\n\nThe response will return a JSON object containing the following fields:\n\n- **rankings**: An array of ranking objects, each representing a football team with the following properties:\n \n - **team**: An object containing details about the team:\n \n - **name**: The full name of the team.\n \n - **shortName**: The abbreviated name of the team.\n \n - **gender**: The gender category of the team.\n \n - **nameCode**: A code representing the team's name.\n \n - **disabled**: A boolean indicating if the team is disabled.\n \n - **national**: A boolean indicating if the team is a national team.\n \n - **type**: An integer representing the type of team.\n \n - **id**: The unique identifier for the team.\n \n - **country**: An object containing country details:\n \n - **alpha2**: The 2-letter country code.\n \n - **alpha3**: The 3-letter country code.\n \n - **name**: The name of the country.\n \n - **year**: The year for which the ranking is applicable.\n \n - **type**: An integer representing the type of ranking.\n \n - **rowName**: The name of the row in the ranking.\n \n - **ranking**: The rank of the team.\n \n - **points**: The points accumulated by the team.\n \n - **id**: The unique identifier for the ranking entry.\n \n - **country**: An object representing additional country details.\n \n - **rankingClass**: A string representing the classification of the ranking.\n \n- **updatedAtTimestamp**: A timestamp indicating when the rankings were last updated.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ``` # Manager ## Manager Details > \## Get Manager Details\ > \ > This endpoint retrieves detailed information about a football manager based on their unique identifier.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier of the manager whose details are to be fetched.\ > \ > \ > \### Response\ > \ > The response will return a JSON object with the following structure:\ > \ > \- \*\*status\*\*: Indicates the success of the request (boolean).\ > \ > \- \*\*statusCode\*\*: A numerical code representing the status of the response (integer).\ > \ > \- \*\*message\*\*: A message providing additional context (string).\ > \ > \- \*\*response\*\*: An object containing the manager's details, including:\ > \ > \- \*\*name\*\*: The full name of the manager (string).\ > \ > \- \*\*shortName\*\*: A shorter version of the manager's name (string).\ > \ > \- \*\*teams\*\*: An array of teams associated with the manager, where each team object includes:\ > \ > \- \*\*name\*\*: The name of the team (string).\ > \ > \- \*\*shortName\*\*: The short name of the team (string).\ > \ > \- \*\*gender\*\*: The gender category of the team (string).\ > \ > \- \*\*category\*\*: An object containing details about the team category (name, id, flag, alpha2).\ > \ > \- \*\*tournament\*\*: An object detailing the tournament information associated with the team.\ > \ > \- \*\*isLive\*\*: Indicates if the team is currently active (boolean).\ > \ > \- \*\*id\*\*: The unique identifier of the team (integer).\ > \ > \- \*\*preferredFormation\*\*: The formation preferred by the manager (string).\ > \ > \- \*\*deceased\*\*: Indicates if the manager is deceased (boolean).\ > \ > \- \*\*id\*\*: The unique identifier of the manager (integer).\ > \ > \- \*\*country\*\*: An object containing the country information (alpha2, name).\ > \ > \- \*\*performance\*\*: An object summarizing the manager's performance metrics (total wins, draws, losses, goals scored, goals conceded, total points).\ > \ > \- \*\*dateOfBirthTimestamp\*\*: The timestamp of the manager's date of birth (integer). ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Manager"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/manager/{id}":{"get":{"tags":["Manager"],"summary":"Manager Details","description":"## Get Manager Details\n\nThis endpoint retrieves detailed information about a football manager based on their unique identifier.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/football/api/v1/manager/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier of the manager whose details are to be fetched.\n \n\n### Response\n\nThe response will return a JSON object with the following structure:\n\n- **status**: Indicates the success of the request (boolean).\n \n- **statusCode**: A numerical code representing the status of the response (integer).\n \n- **message**: A message providing additional context (string).\n \n- **response**: An object containing the manager's details, including:\n \n - **name**: The full name of the manager (string).\n \n - **shortName**: A shorter version of the manager's name (string).\n \n - **teams**: An array of teams associated with the manager, where each team object includes:\n \n - **name**: The name of the team (string).\n \n - **shortName**: The short name of the team (string).\n \n - **gender**: The gender category of the team (string).\n \n - **category**: An object containing details about the team category (name, id, flag, alpha2).\n \n - **tournament**: An object detailing the tournament information associated with the team.\n \n - **isLive**: Indicates if the team is currently active (boolean).\n \n - **id**: The unique identifier of the team (integer).\n \n - **preferredFormation**: The formation preferred by the manager (string).\n \n - **deceased**: Indicates if the manager is deceased (boolean).\n \n - **id**: The unique identifier of the manager (integer).\n \n - **country**: An object containing the country information (alpha2, name).\n \n - **performance**: An object summarizing the manager's performance metrics (total wins, draws, losses, goals scored, goals conceded, total points).\n \n - **dateOfBirthTimestamp**: The timestamp of the manager's date of birth (integer).","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"}}}}}}}}} ``` ## Manager Career > \## Get Manager Career Details\ > \ > This endpoint retrieves the career details of a football manager identified by their unique ID.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: \`GET\`\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (required): The unique identifier of the manager whose career details are being requested.\ > \ > \ > \### Response\ > \ > On success, 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 request (if any).\ > \ > \- \*\*response\*\*: An array containing the career details of the manager, where each item includes:\ > \ > \- \*\*team\*\*: An object with details about the team, including:\ > \ > \- \`name\`: The name of the team.\ > \ > \- \`shortName\`: The abbreviated name of the team.\ > \ > \- \`gender\`: The gender category of the team.\ > \ > \- \`nameCode\`: A code representing the name of the team.\ > \ > \- \`disabled\`: A boolean indicating if the team is disabled.\ > \ > \- \`national\`: A boolean indicating if the team is a national team.\ > \ > \- \`type\`: An integer representing the type of team.\ > \ > \- \`id\`: The unique identifier of the team.\ > \ > \- \*\*performance\*\*: An object summarizing the manager's performance, including:\ > \ > \- \`total\`: Total number of matches managed.\ > \ > \- \`wins\`: Total number of matches won.\ > \ > \- \`draws\`: Total number of matches drawn.\ > \ > \- \`losses\`: Total number of matches lost.\ > \ > \- \`totalPoints\`: Total points accumulated.\ > \ > \ > This response structure allows consumers of the API to easily understand the career trajectory and performance metrics of the specified football manager. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Manager"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/manager/career/{id}":{"get":{"tags":["Manager"],"summary":"Manager Career","description":"## Get Manager Career Details\n\nThis endpoint retrieves the career details of a football manager identified by their unique ID.\n\n### Request\n\n- **Method**: `GET`\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/football/api/v1/manager/career/:id`\n \n- **Path Parameter**:\n \n - `id` (required): The unique identifier of the manager whose career details are being requested.\n \n\n### Response\n\nOn success, the 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 request (if any).\n \n- **response**: An array containing the career details of the manager, where each item includes:\n \n - **team**: An object with details about the team, including:\n \n - `name`: The name of the team.\n \n - `shortName`: The abbreviated name of the team.\n \n - `gender`: The gender category of the team.\n \n - `nameCode`: A code representing the name of the team.\n \n - `disabled`: A boolean indicating if the team is disabled.\n \n - `national`: A boolean indicating if the team is a national team.\n \n - `type`: An integer representing the type of team.\n \n - `id`: The unique identifier of the team.\n \n - **performance**: An object summarizing the manager's performance, including:\n \n - `total`: Total number of matches managed.\n \n - `wins`: Total number of matches won.\n \n - `draws`: Total number of matches drawn.\n \n - `losses`: Total number of matches lost.\n \n - `totalPoints`: Total points accumulated.\n \n\nThis response structure allows consumers of the API to easily understand the career trajectory and performance metrics of the specified football manager.","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"}}}}}}}}} ``` # Images ## Team Image > \### Get Team Image\ > \ > This endpoint retrieves the image associated with a specific football team identified by its unique ID.\ > \ > \#### Request Parameters\ > \ > \- \`id\` (path parameter): The unique identifier of the team whose image is to be fetched. This parameter is required.\ > \ > \ > This endpoint is useful for applications that need to display team images dynamically based on user selection or other criteria. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Images"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/image/team/{id}":{"get":{"tags":["Images"],"summary":"Team Image","description":"### Get Team Image\n\nThis endpoint retrieves the image associated with a specific football team identified by its unique ID.\n\n#### Request Parameters\n\n- `id` (path parameter): The unique identifier of the team whose image is to be fetched. This parameter is required.\n \n\nThis endpoint is useful for applications that need to display team images dynamically based on user selection or other criteria.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"Successful response","content":{"application/json":{}}}}}}}} ``` ## Player Image > \## Get Player Image\ > \ > This endpoint retrieves the image associated with a specific player identified by their unique ID.\ > \ > \### Request Parameters\ > \ > \- \`id\` (path parameter): The unique identifier of the player whose image is being requested. This parameter is required.\ > \ > \ > On a successful request, the response will include the player's image in a format suitable for display.\ > \ > \### Notes\ > \ > \- Ensure that the player ID provided is valid and corresponds to an existing player in the system.\ > \ > \- The response will return a 200 status code on success, and appropriate error codes for invalid requests or if the player is not found. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Images"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/image/player/{id}":{"get":{"tags":["Images"],"summary":"Player Image","description":"## Get Player Image\n\nThis endpoint retrieves the image associated with a specific player identified by their unique ID.\n\n### Request Parameters\n\n- `id` (path parameter): The unique identifier of the player whose image is being requested. This parameter is required.\n \n\nOn a successful request, the response will include the player's image in a format suitable for display.\n\n### Notes\n\n- Ensure that the player ID provided is valid and corresponds to an existing player in the system.\n \n- The response will return a 200 status code on success, and appropriate error codes for invalid requests or if the player is not found.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"Successful response","content":{"application/json":{}}}}}}}} ``` ## Manager Image > \## Get Manager Image\ > \ > This endpoint retrieves the image associated with a specific football manager identified by their unique ID.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*Endpoint\*\*: \` > \ > \- \*\*Path Parameter\*\*:\ > \ > \- \`id\` (string): The unique identifier of the football manager whose image is to be fetched.\ > \ > \ > \### Response\ > \ > The response will contain the image data of the specified manager. The expected format is an image file, which may vary based on the manager's image type (e.g., JPEG, PNG).\ > \ > The response will return the image file directly in the body of the response. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Images"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/image/manager/{id}":{"get":{"tags":["Images"],"summary":"Manager Image","description":"## Get Manager Image\n\nThis endpoint retrieves the image associated with a specific football manager identified by their unique ID.\n\n### Request\n\n- **Method**: GET\n \n- **Endpoint**: `https://apiv3.sportsapi360.com/football/api/v1/image/manager/:id`\n \n- **Path Parameter**:\n \n - `id` (string): The unique identifier of the football manager whose image is to be fetched.\n \n\n### Response\n\nThe response will contain the image data of the specified manager. The expected format is an image file, which may vary based on the manager's image type (e.g., JPEG, PNG).\n\nThe response will return the image file directly in the body of the response.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true}],"responses":{"200":{"description":"Successful response","content":{"application/json":{}}}}}}}} ``` ## Flag Image > \## Get Country Flag Image\ > \ > This endpoint retrieves the flag image of a specified country.\ > \ > \### Request\ > \ > \- \*\*Method:\*\* GET\ > \ > \- \*\*Endpoint:\*\* \` > \ > \ > \### Parameters\ > \ > \- \*\*Path Parameter:\*\*\ > \ > \- \`name\` (string): The name of the country whose flag image is to be retrieved. This should be the official name of the country.\ > \ > \ > \### Response\ > \ > The response will be in image format (typically PNG or JPEG) representing the flag of the specified country. The content type of the response will be \`image/png\` or \`image/jpeg\` depending on the format of the flag image.\ > \ > \### Example\ > \ > \- \*\*Request:\*\* \`GET > \ > \- \*\*Response:\*\* An image of the French flag. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Images"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/image/flags/{name}":{"get":{"tags":["Images"],"summary":"Flag Image","description":"## Get Country Flag Image\n\nThis endpoint retrieves the flag image of a specified country.\n\n### Request\n\n- **Method:** GET\n \n- **Endpoint:** `https://apiv3.sportsapi360.com/football/api/v1/image/flags/:name`\n \n\n### Parameters\n\n- **Path Parameter:**\n \n - `name` (string): The name of the country whose flag image is to be retrieved. This should be the official name of the country.\n \n\n### Response\n\nThe response will be in image format (typically PNG or JPEG) representing the flag of the specified country. The content type of the response will be `image/png` or `image/jpeg` depending on the format of the flag image.\n\n### Example\n\n- **Request:** `GET https://apiv3.sportsapi360.com/football/api/v1/image/flags/France`\n \n- **Response:** An image of the French flag.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"name","in":"path","schema":{"type":"string"},"required":true}],"responses":{"200":{"description":"Successful response","content":{"application/json":{}}}}}}}} ``` ## Tournament Image > \## Endpoint Description\ > \ > This endpoint retrieves an image associated with a specific tournament based on the provided unique identifier and an optional theme.\ > \ > \### Request\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \ > \#### Path Parameters\ > \ > \- \`:id\` (string, required): The unique identifier for the tournament. This parameter is essential to specify which tournament's image is being requested.\ > \ > \- \`:theme\` (string, optional): An optional parameter that allows the user to specify a theme for the image. If provided, the response will return an image that aligns with the specified theme.\ > \ > \ > This endpoint is useful for applications that need to display tournament images dynamically based on user selections or preferences. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[{"name":"Images"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/image/tournament/unique/{id}/{theme}":{"get":{"tags":["Images"],"summary":"Tournament Image","description":"## Endpoint Description\n\nThis endpoint retrieves an image associated with a specific tournament based on the provided unique identifier and an optional theme.\n\n### Request\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/image/tournament/unique/:id/:theme?`\n \n\n#### Path Parameters\n\n- `:id` (string, required): The unique identifier for the tournament. This parameter is essential to specify which tournament's image is being requested.\n \n- `:theme` (string, optional): An optional parameter that allows the user to specify a theme for the image. If provided, the response will return an image that aligns with the specified theme.\n \n\nThis endpoint is useful for applications that need to display tournament images dynamically based on user selections or preferences.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"id","in":"path","schema":{"type":"integer"},"required":true},{"name":"theme","in":"path","schema":{"type":"string"},"required":true,"description":"dark or light"}],"responses":{"200":{"description":"Successful response","content":{"application/json":{}}}}}}}} ``` # FOOTBALL API V1 ## Global Search > \### Endpoint Description\ > \ > This endpoint allows users to search for football-related information globally based on a specified query. In this case, the query is set to "Barcelona", which will return relevant data associated with the search term.\ > \ > \### Request Format\ > \ > \- \*\*Method\*\*: GET\ > \ > \- \*\*URL\*\*: \` > \ > \- \*\*Query Parameters\*\*:\ > \ > \- \`query\` (string): The search term used to find relevant football data. In this example, the query is set to "Barcelona".\ > \ > \ > \### Response Structure\ > \ > The response from this endpoint will be in JSON format and consists of 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 context about the request's status (may be empty).\ > \ > \- \*\*response\*\* (array): An array containing the search results, where each result has the following properties:\ > \ > \- \*\*id\*\* (integer): A unique identifier for the football entity.\ > \ > \- \*\*name\*\* (string): The name of the football entity.\ > \ > \- \*\*nameCode\*\* (string): A code representing the name of the football entity.\ > \ > \- \*\*national\*\* (boolean): Indicates if the entity is national.\ > \ > \- \*\*type\*\* (string): The type of entity (e.g., player, team).\ > \ > \- \*\*gender\*\* (string): The gender associated with the entity.\ > \ > \- \*\*country\*\* (object): An object containing country information:\ > \ > \- \*\*alpha2\*\* (string): The two-letter country code.\ > \ > \- \*\*name\*\* (string): The name of the country.\ > \ > \- \*\*score\*\* (integer): A score associated with the search result.\ > \ > \ > This structure provides a comprehensive overview of the search results related to the specified query. ```json {"openapi":"3.0.0","info":{"title":"FOOTBALL API V1","version":"1.0.0"},"tags":[],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/football/api/v1/global/search":{"get":{"tags":["default"],"summary":"Global Search","description":"### Endpoint Description\n\nThis endpoint allows users to search for football-related information globally based on a specified query. In this case, the query is set to \"Barcelona\", which will return relevant data associated with the search term.\n\n### Request Format\n\n- **Method**: GET\n \n- **URL**: `https://apiv3.sportsapi360.com/football/api/v1/global/search`\n \n- **Query Parameters**:\n \n - `query` (string): The search term used to find relevant football data. In this example, the query is set to \"Barcelona\".\n \n\n### Response Structure\n\nThe response from this endpoint will be in JSON format and consists of 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 context about the request's status (may be empty).\n \n- **response** (array): An array containing the search results, where each result has the following properties:\n \n - **id** (integer): A unique identifier for the football entity.\n \n - **name** (string): The name of the football entity.\n \n - **nameCode** (string): A code representing the name of the football entity.\n \n - **national** (boolean): Indicates if the entity is national.\n \n - **type** (string): The type of entity (e.g., player, team).\n \n - **gender** (string): The gender associated with the entity.\n \n - **country** (object): An object containing country information:\n \n - **alpha2** (string): The two-letter country code.\n \n - **name** (string): The name of the country.\n \n - **score** (integer): A score associated with the search result.\n \n\nThis structure provides a comprehensive overview of the search results related to the specified query.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"query","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}} ```