> 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/data-and-features.md). # Data & Features ## **B** *** ## **bet\_settlement** A message that settles (clears) bets for the listed markets and outcomes of a particular event, including result, void\_factor, and dead-heat/each-way settlement details. ## **C** *** ### **Certainty** A field on `bet_settlement` indicating whether the settlement came from scouts reporting results live (1) or from confirmed official results post-match (2). ## **D** *** ### **Dead Heat Factor** Reduces a payout proportionally when multiple competitors tie for a placing. A related field, `dead_heat_factor_place`, applies the same logic specifically to the place portion of an each-way bet. ## **E** *** ### **Each-Way Bet** A bet settled in two parts, win and place, using each-way terms specific to the market (e.g. 1/4 odds for the first 5 places). Governed by the `each_way_factor` (fraction of win odds used for the place payout) and `each_way_result` (whether the win portion, place portion, or both settled as a winner). ## **H** *** ### **Handover** The transition period when a live producer takes over odds delivery for a match from the pre-match producer. Markets are marked either `deactivated` (no longer sent) or `handed_over` (should be suspended until the live producer sends its own update). ## **M** *** ### **Market Status** The current lifecycle state of a market: active, suspended, deactivated, or handed\_over, reflecting whether it's currently open for betting. ## **O** *** ### **odds\_change** A message listing odds changes for some or all markets on a match, which can also signal a bet stop for the whole match, specific markets, or specific outcomes. ### **Outrights** Winner markets spanning a tournament or short-term competition. Six types exist: Championship, Top 3, Top X, Short Term, 3Balls (Golf only), and Head2Heads (H2H). ## **R** *** ### **Replay Server** A testing environment that lets customers replay pre-made or previously finished matches exactly as they occurred live. Available for both the API and the SDK. ## **V** *** ### **Void Reason** Explains why one or more outcomes in a market were voided. Present only when at least one outcome carries a `void_factor` (the fraction of the stake to be refunded). --- # 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/introduction/glossary/data-and-features.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.