> 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/volleyball/readme.md). # Overview This comprehensive guide provides information on our consumer-facing APIs and WebSockets, enabling seamless connections between our clients and us. To start, you can head to the following few sections. It offers a step-by-step walkthrough on utilising our REST APIs and WebSocket endpoints. You'll find detailed query parameter explanations, payload examples, responses, and various action types. If you encounter any issues or require assistance, our dedicated support team is here to help. Feel free to reach out to them at [support@sportradar.com](mailto:support@imgarena.com). We're committed to ensuring a smooth and successful experience for you. Once again, welcome to the technical documentation, and we look forward to assisting you on your journey! {% hint style="info" %} Please note that the API currently supports only indoor volleyball tournaments by FIVB and CEV. From May 2024, it will include beach volleyball. Data points for tournaments are consistent across organisers. Player-specific data like lineup, injuries, and substitutions will be available for CEV games starting May 2024. {% endhint %} --- # 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/volleyball/readme.md?ask=&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.