> 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/documentation-1/connecting-programmatically.md).

# Testing

Learn about the different methods to test your integration before going live.

This page includes test event IDs and other information to make sure your integration works as planned. Use it to trigger different flows in your integration and ensure they are handled accordingly.

### Table Tennis API

When using the Table Tennis API in your application, ensure that:

* All required header paramters are set correctly
* You have a valid OAuth Bearer 2.0 token for authentication
* Use the correct URL to get connected to the API

### Basic Match IDs <a href="#cards" id="cards"></a>

Genuine match ID information cannot be used in test mode. Instead, use any of the following test match ID numbers to make a successful request.

| Match ID | Details       |
| -------- | ------------- |
| 999991   | Test Match ID |

### Example of how to connect to a Websocket <a href="#cards" id="cards"></a>

Use the following command to get more details about a match associated with the id of 999991.

`WebSocket: wss://dde-streams.srarena.io/tabletennis/999991/matchdetails`

Then right after getting connected, a valid authentication token should be sent immediately.

```
{
  "authToken": "<token>"
}
```

### Example of how to connect to the REST API <a href="#cards" id="cards"></a>

**Method:** GET

**URL:** [https://dde-test-api.srarena.io/tabletennis/tournaments/](https://dde-test-api.imggaming.com/tabletennis/tournaments/)

**Headers:** \[Accept] application/vnd.imgarena.dde.api+json;version=1


---

# 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/documentation-1/connecting-programmatically.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.