> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match.md).

# 02. During a Match

- [Scoring](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match/scoring.md): Basic packets about point scoring during a game.
- [Serves](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match/the-basics.md): Basic packets about swapping sides and serves during a game.
- [Correction](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match/undo-events.md): In an event of making a mistake when entering information into the match scoresheet, the problem should be fixed and correct scores should be published.
- [Timeouts](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match/timeouts.md): Each player has one timeout per match lasting up to 60 seconds along with a brief towel-off breaks at every 6 points during a match.
- [Sanctions](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match/sanctions.md): Both players and coaches may be sanctioned during a match. A Sanction packet will be emitted in such scenarios, describing the player that was sanctioned, and which sanction(s) have been applied.
- [Penalties](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match/sanctions/game-penalties.md)
- [Disqualification](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match/sanctions/disqualification.md): The referee has the power to disqualify a player from a match, an event or a whole competition by holding up a red card. The umpire can also issue a red card to coaches.
- [Expediting](https://docs.sportradar.com/table-tennis/live-data-scenarios/during-a-match/expedite-rule.md): This regulation in table tennis, also known as the Expedite System, begins after 10 minutes of gameplay and fewer than 18 total points have been recorded.


---

# 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.sportradar.com/table-tennis/live-data-scenarios/during-a-match.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.