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

# Match Over By Overs

### Match Over By Overs

Retrieves a breakdown of runs scored in each over for a specific cricket match, with optional filtering by innings and over number.

#### Path Variables

| Variable | Description                                                                |
| -------- | -------------------------------------------------------------------------- |
| `id`     | The unique match ID. Populated via the `{{match_id}}` collection variable. |

#### Query Parameters

| Parameter | Required | Description                                                         |
| --------- | -------- | ------------------------------------------------------------------- |
| `api_key` | Yes      | Your API access token. Use the `{{api_token}}` collection variable. |
| `innings` | No       | Filter by innings number (e.g. `1`, `2`).                           |
| `over`    | No       | Filter by a specific over number (e.g. `4`).                        |
| `page`    | No       | Page number for paginated results. Starts at `1`.                   |
| `limit`   | No       | Number of over entries to return per page.                          |

#### Response

Returns a paginated list of over summaries, each containing the over number, runs scored, wickets taken, and ball-by-ball breakdown.

#### Authentication

Pass your API token via the `api_key` query parameter.

```json
{"openapi":"3.0.3","info":{"title":"All Endpoints V5","version":"1.0.0"},"servers":[{"url":"https://apiv5.sportsapi360.com"}],"paths":{"/cricket/v1/matches/{id}/overs_by_overs":{"get":{"summary":"Match Over By Overs","description":"## Match Over By Overs\n\nRetrieves a breakdown of runs scored in each over for a specific cricket match, with optional filtering by innings and over number.\n\n### Path Variables\n\n| Variable | Description |\n|----------|-------------|\n| `id` | The unique match ID. Populated via the `{{match_id}}` collection variable. |\n\n### Query Parameters\n\n| Parameter | Required | Description |\n|-----------|----------|-------------|\n| `api_key` | Yes | Your API access token. Use the `{{api_token}}` collection variable. |\n| `innings` | No | Filter by innings number (e.g. `1`, `2`). |\n| `over` | No | Filter by a specific over number (e.g. `4`). |\n| `page` | No | Page number for paginated results. Starts at `1`. |\n| `limit` | No | Number of over entries to return per page. |\n\n### Response\n\nReturns a paginated list of over summaries, each containing the over number, runs scored, wickets taken, and ball-by-ball breakdown.\n\n### Authentication\n\nPass your API token via the `api_key` query parameter.","operationId":"matchOverByOvers","parameters":[{"name":"innings","in":"query","schema":{"type":"string"},"description":"Filter over by overs runs by innings number."},{"name":"over","in":"query","schema":{"type":"string"},"description":"Filter over by overs runs by over number."},{"name":"page","in":"query","schema":{"type":"string"},"description":"Page number for request"},{"name":"limit","in":"query","schema":{"type":"string"},"description":"Number of commentaries to list in each api request"},{"name":"api_key","in":"query","required":true,"schema":{"type":"string"},"description":"API Access token"}],"responses":{"200":{"description":"Match Over By Overs","headers":{"CF-RAY":{"schema":{"type":"string"}},"Cache-Control":{"schema":{"type":"string"}},"Connection":{"schema":{"type":"string"}},"Content-Encoding":{"schema":{"type":"string"}},"Date":{"schema":{"type":"string"}},"Nel":{"schema":{"type":"string"}},"Report-To":{"schema":{"type":"string"}},"Server":{"schema":{"type":"string"}},"Transfer-Encoding":{"schema":{"type":"string"}},"Vary":{"schema":{"type":"string"}},"X-Request-Id":{"schema":{"type":"string"}},"alt-svc":{"schema":{"type":"string"}},"cf-cache-status":{"schema":{"type":"string"}}},"content":{"application/json":{"schema":{"type":"object","properties":{"data":{"type":"array","items":{"type":"object","properties":{"balls":{"type":"array","items":{"type":"object","properties":{"ball":{"type":"string"},"event":{"type":"string"},"runs":{"type":"number"},"score":{"type":"string"}}}},"inning_number":{"type":"number"},"over":{"type":"string"},"runs":{"type":"number"},"wickets":{"type":"number"}}}},"meta":{"type":"object","properties":{"api_version":{"type":"string"},"page":{"type":"object","properties":{"has_more":{"type":"boolean"},"limit":{"type":"number"},"page":{"type":"number"},"total":{"type":"number"},"total_pages":{"type":"number"}}},"provider":{"type":"string"},"request_id":{"type":"string"}}},"success":{"type":"boolean"}}}}}}}}}}}
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportsapi360.com/cricket-docs/cricket-api/all-endpoints-v5/match-over-by-overs.md?ask=<question>&goal=<user_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.

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.
