# UOF API fixture information

### **UOF API - Sport & Category** <a href="#golfuofapifixtureinformation-uofapi-sport-and-category" id="golfuofapifixtureinformation-uofapi-sport-and-category"></a>

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

```xml
<sport id="sr:sport:9" name="Golf"/>
<category id="sr:category:28" name="Men"/>
```

### **UOF API - Golf fixtures & their stage hierarchy** <a href="#golfuofapifixtureinformation-uofapi-golffixtures-and-theirstagehierarchy" id="golfuofapifixtureinformation-uofapi-golffixtures-and-theirstagehierarchy"></a>

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

{% code title="Season stage" %}

```xml
<tournament_info xmlns="http://schemas.sportradar.com/sportsapi/v1/unified" …>
  <tournament id="sr:stage:607727" name="PGA Tour 2021" scheduled="2020-09-10T07:00:00+00:00" scheduled_end="2021-09-
06T04:00:00+00:00">
    <sport id="sr:sport:9" name="Golf"/>
    <category id="sr:category:28" name="Men"/>
  </tournament>
  <coverage_info live_coverage="true"/>
</tournament_info>
```

{% endcode %}

{% hint style="info" %}
**Note**

* Various event stages belong to a season stage and the event schedule of a specific season can be fetched from the UOF API schedule endpoints.
* The sport and the category where a specific stage is connected to are specified within the \<sport> and \<category> elements.
  {% endhint %}

<figure><img src="/files/1LrYOW8INCUex1owlXF9" alt=""><figcaption></figcaption></figure>

{% code title="Event stage" lineNumbers="true" %}

```xml
<fixtures_fixture xmlns="http://schemas.sportradar.com/sportsapi/v1/unified" …>
  <fixture id="sr:stage:634477" name="U.S. Open" type="parent" scheduled="2020-09-17T00:00:00+00:00" scheduled_end="2020-09-
19T00:00:00+00:00" stage_type="event">
    <parent id="sr:stage:538072" name="European Tour 2020" type="parent" stage_type="season"/>
    <additional_parents>
      <parent id="sr:stage:607727" name="PGA Tour 2021" type="parent" stage_type="season"/>
    </additional_parents>
    <tournament id="sr:stage:607727" name="PGA Tour 2021" scheduled="2020-09-10T07:00:00+00:00" scheduled_end="2021-09-
06T04:00:00+00:00">
      <sport id="sr:sport:9" name="Golf"/>
      <category id="sr:category:28" name="Men"/>
    </tournament>
    <competitors>
      <competitor id="sr:competitor:20892" name="Stenson, Henrik" abbreviation="STE"/>
       …
    </competitors>
    <races>
      <sport_event id="sr:stage:634481" type="parent" scheduled="2020-09-17T10:50:00+00:00" stage_type="round"/>
      <sport_event id="sr:stage:634483" type="parent" scheduled="2020-09-18T10:50:00+00:00" stage_type="round"/>
    </races>
    <venue id="sr:venue:44498" name="Winged Foot Golf Club">
      <course>
        <hole number="1" par="4"/>
        <hole number="2" par="4"/>
        <hole number="3" par="3"/>
         …
        <hole number="17" par="4"/>
        <hole number="18" par="4"/>
      </course>
    </venue>
    <extra_info>
      <info key="event_type" value="STROKE"/>
    </extra_info>
  </fixture>
</fixtures_fixture>
```

{% endcode %}

Parents of the event stage are reflected in \<parent> & \<additional\_parents> and have the stage\_type "season".

Children of the event stage are reflected in \<races> and have the stage\_type "round".

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

* Some Golf events are belonging to more than one Tour as shown in the example above.
* \<course> element:\
  The par value is defined for each hole of the affected Golf course e.g. \<hole number="1" par="4"/>
* \<extra\_info> element:\
  The value of the key "event\_type" defines how the Golf event is played e.g. \<info key="event\_type" value="STROKE"/> for stroke play events.
  {% endhint %}

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

{% code title="Round stage" lineNumbers="true" %}

```xml
<fixtures_fixture xmlns="http://schemas.sportradar.com/sportsapi/v1/unified" …>
  <fixture id="sr:stage:634481" name="Round 1" type="parent" scheduled="2020-09-17T00:00:00+00:00" scheduled_end="2020-09-
18T00:00:00+00:00" stage_type="round">
    <parent id="sr:stage:634477" name="U.S. Open" type="parent" stage_type="event"/>
    <tournament id="sr:stage:607727" name="PGA Tour 2021" scheduled="2020-09-10T07:00:00+00:00" scheduled_end="2021-09-
06T04:00:00+00:00">
      <sport id="sr:sport:9" name="Golf"/>
      <category id="sr:category:28" name="Men"/>
    </tournament>
    <competitors>
      <competitor id="sr:competitor:20892" name="Stenson, Henrik" abbreviation="STE"/>
       …
      <competitor id="sr:competitor:741889" name="Rousard, Eduard" abbreviation="ROU"/>
    </competitors>
    <races>
      <sport_event id="codds:competition_group:183" type="child" scheduled="2020-09-17T10:50:00+00:00"
stage_type="competition_group"/>
       …
      <sport_event id="codds:competition_group:186" type="child" scheduled="2020-09-17T11:12:00+00:00"
stage_type="competition_group"/>
    </races>
  </fixture>
</fixtures_fixture>
```

{% endcode %}

The parent of the round stage is reflected in \<parent> and has the stage\_type "event".

Children of the event stage are reflected in \<races> and have the stage\_type "competition\_group".

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

* \<races> element:\
  Only groups are listed which will be covered with Live Odds e.g.\
  \<sport\_event id="codds:competition\_group:183" type="child" scheduled="2020-09-17T10:50:00+00:00" stage\_type="competition\_group"/>
  {% endhint %}

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

{% code title="Competition group" lineNumbers="true" %}

```xml
<fixtures_fixture xmlns="http://schemas.sportradar.com/sportsapi/v1/unified" …>
  <fixture id="codds:competition_group:186" type="child" scheduled="2020-09-17T11:12:00+00:00" stage_type="competition_group">
    <parent id="sr:stage:634481" name="Round 1" type="parent" stage_type="round"/>
    <tournament id="sr:stage:607727" name="PGA Tour 2021" scheduled="2020-09-10T07:00:00+00:00" scheduled_end="2021-09-
06T04:00:00+00:00">
      <sport id="sr:sport:9" name="Golf"/>
      <category id="sr:category:28" name="Men"/>
    </tournament>
    <competitors>
      <competitor id="sr:competitor:22464" name="Reavie, Chez" abbreviation="REA"/>
      <competitor id="sr:competitor:23293" name="Streelman, Kevin" abbreviation="STR"/>
      <competitor id="sr:competitor:48665" name="Kang, Sung Hoon" abbreviation="KAN"/>
    </competitors>
  </fixture>
</fixtures_fixture>
```

{% endcode %}

The parent of the competition\_group is reflected in \<parent> and has the stage\_type "round".

The competition\_group is the lowest level of the Golf event hierarchy and therefore no \<races> attribute is available.

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

* Competition groups are reflecting the group of players ("flights") which are going together through the Golf course on a specific day/round.
* A competition group includes usually two or three \<competitors> depending on the round and Golf tournament.
* \<fixture> element:\
  \> The "scheduled" attribute indicates their tee time/starting time .<br>
* We provide several Live Odds markets for competition groups (codds:competition\_group:\<id>) and within the AMQP feed dedicated events will be sent as a "container" for those group markets groups. Please find additional information for [Live Golf AMQP feed messages here](/uof/live-competition-odds/live-odds-golf/c-odds-amqp-messages.md).
  {% 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/uof-api-fixture-information.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.