> 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/websockets.md). # Websockets A single websocket endpoint exists for each match. It is a match details feed and contains an action based play by play representation of a volleyball match. ### Endpoint URL `wss://dde-streams.srarena.io/tabletennis/{id}/matchdetails` ### Process for connecting to the web socket endpoints * Connect to SSL websocket address * Send JSON packet containing API token * Receive response indicating that connection is authorised (or a response indicating why the connection cannot be made) * Receive data packets Once you have the API token, any further data that you send over the connection will be ignored. Security protocol for WebSockets:\ Please note that we currently we do not support SSL. We only support the use of TLS Version 1.2+. --- # 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://docs.sportradar.com/table-tennis/documentation-1/websockets.md?ask=&goal= ``` `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.