> 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/uof/api-and-structure/api-stage-structure/golf.md). # Golf All Golf markets, both pre-match and live, are delivered through the **Competition Odds producer (Producer ID: 14)**. Golf is organized into stages as well. Thanks to the "All Sport" end point, it is possible to retrieve the id of the sport which is 9 and retrieve all the stages thanks to the "All avaialble tournament for sport". The end point provides all the available tournaments for such sport identified via stages. ```xml ``` \ Once all the stages are retrieved, it is possible to filter the stages one by one in the end point "Schedule for a tournament" and get more information. The scheduled start date and end date are not to be taken into consideration for outrights. Dates related to outrights are sent via the UOF AMQP messages. ```xml ``` --- # 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/uof/api-and-structure/api-stage-structure/golf.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.