# Sport Hierarchy

Live Odds markets will be offered for the event and for selected groups (“flights”) which play together within a specific round. Live Golf events are structured in the Unified Odds Feed as follows in order to ensure that groups as well as event markets can be properly consumed and displayed within a platform:<br>

<figure><img src="/files/rSJFnTF0IGv1raiXeXj7" alt=""><figcaption></figcaption></figure>

The hierarchy between those layers is reflected in the UOF API as explained below. \
\
**Season**                                      parent of **Event**

**Event**                                  parent of **Round**

**Round**                          parent of **Competition group**   <br>

Please visit [Golf UOF API fixture information](/uof/live-competition-odds/live-odds-golf/uof-api-fixture-information.md) for more technical details.

{% hint style="info" %}
**Please note**

Live Odds markets are offered only within the following hierarchical layers:

* Event (e.g. the "Tournament winner" market)    &#x20;
* Competition group (e.g. the "3 ball" market)      <br>

The mentioned hierarchical order defines to which round a competition group belongs and as a consequence it defines as well to which round a specific group market (e.g. "3 ball") is referencing to.&#x20;

Example: The market "3 ball" references to round 1, if round 1 is the \<parent> of the affected competition group.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.sportradar.com/uof/live-competition-odds/live-odds-golf/sport-hierarchy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.