# 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"}}}}}}}}} ```` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docsv3.sportsapi360.com/football-docs/api-collection-football/matches.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.