> For the complete documentation index, see [llms.txt](https://docsv3.sportsapi360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docsv3.sportsapi360.com/cricket-docs/api-collection-cricket/matches-list-api.md).

# 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: \`<https://apiv3.sportsapi360.com/cricket/api/v3/match/schedule\\`\\>
> &#x20;   \
> \- Query Parameters:\
> &#x20;   \
> &#x20;   \- type (string, required): Type of matches to retrieve (e.g. All)\
> &#x20;       \
> &#x20;   \- page (integer, required): Page number for pagination (e.g. 0)\
> &#x20;       \
> \
> \#### Response\
> \
> \- Status: 200\
> &#x20;   \
> \- Content-Type: application/json\
> &#x20;   \
> \- Body:\
> &#x20;   \
> &#x20;   \- 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: \`<https://apiv3.sportsapi360.com/cricket/api/v2/match/featured\\`\\>
> &#x20;   \
> \
> \#### Response\
> \
> \- Status: 200\
> &#x20;   \
> \- Content-Type: application/json\
> &#x20;   \
> \- Body:\
> &#x20;   \
> &#x20;   \- 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: \`<https://apiv3.sportsapi360.com/cricket/api/v2/match/schedule\\`\\>
> &#x20;   \
> \- Query Parameters:\
> &#x20;   \
> &#x20;   \- type (string, required): Type of matches to retrieve (e.g. All)\
> &#x20;       \
> &#x20;   \- page (integer, required): Page number for pagination (e.g. 0)\
> &#x20;       \
> \
> \#### Response\
> \
> \- Status: 200\
> &#x20;   \
> \- Content-Type: application/json\
> &#x20;   \
> \- Body:\
> &#x20;   \
> &#x20;   \- 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"}}}}}}}}}
```


---

# 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
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, and the optional `goal` query parameter:

```
GET https://docsv3.sportsapi360.com/cricket-docs/api-collection-cricket/matches-list-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
