> 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/introduction/glossary.md). # Glossary This glossary defines the terms, abbreviations, and product names used across the Unified Odds Feed (UOF) documentation. Because UOF spans a wide range of topics, from feed protocols to market behavior to SDK internals, the glossary is split into one page per top-level section, matching the structure of this documentation: * **Introduction** — foundational terms: environments, producers, integration credentials * **Data & Features** — markets, outcomes, message types, and feed behavior * **SDK** — SDK-specific components and concepts * **API and Structure** — API endpoints, parameters, and recovery mechanisms Each page lists its terms alphabetically. If you're not sure which section a term belongs to, use your browser's search (`Ctrl/Cmd + F`) on this page, or check the section whose topic feels closest to what you're looking for. --- # 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/uof/introduction/glossary.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.