> 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/live-competition-odds/live-odds-golf.md).

# Golf

{% hint style="info" %}
**IMPORTANT MIGRATION NOTICE: GOLF PRODUCT UPGRADE & LEGACY SUNSET**

The new Sportradar Golf product is available in production from 16 Nov 2026.

It includes two sets of events: events priced by Dime Line Trading (DLT), and events priced in-house.

All live Golf comes through producer 14.

Pre-match is split. DLT-covered events come from producer 14. All other events come from producer 3.

Until 13 Dec 2026, some DLT-covered events are still also priced in-house. The in-house pre-match message for those events is still sent on producer 3, so the same pre-match event can arrive twice. If it does, use the pre-match message on producer 14 and ignore the pre-match message for that event on producer 3. Live is not affected.

After 13 Dec 2026, our in-house service stops pricing any event DLT offers. The same event is no longer sent on both producers. DLT pre-match comes from producer 14 only. In-house pre-match comes from producer 3 only. Live remains on producer 14.

On 5 Jan 2027, legacy live Golf ends only for clients who do not take the new Sportradar Golf product. To upgrade, contact your Sportradar representative or <sales@sportradar.com>.\
\
**REFER TO THE FOLLOWING INTEGRATION DOCUMENTS:**

* **Technical Client Guide:** Download Golf - **UOF C-Odds Technical Client Guide (PDF)** below
* **Market Overview:** See the [Golf Market Overview](https://docs.sportradar.com/uof/introduction/market-overview-uof-and-cb.md) for the full market list, including which events are covered by DLT.&#x20;

\
**Core Platform Prerequisites & Guides:**\
• AMQP Topic Filtering & Routing Keys: [Configure queue bindings for both .pre. and .live. Golf routing keys:](https://docs.sportradar.com/uof/data-and-features/messages/amqp-topic-filtering.md)\
• Golf API Stage Structure: [Understand how Golf tournaments, stages, and rounds are modeled (sr:stage)](https://docs.sportradar.com/uof/api-and-structure/api-stage-structure/golf.md):
{% endhint %}

{% file src="/files/ou3HVPZQTLxlkqCWpkFt" %}
Golf Technical Client Guide
{% endfile %}

Live Odds for Golf stroke play tournaments are offered for various groups as well as on event/tournament level.\
Please find the Live Odds market overview [here](https://docs.sportradar.com/uof/introduction/market-overview-uof-and-cb.md).\
\
All covered Golf events will be automatically booked and as a consequence be delivered in the Unified Odds Feed once the required Golf Live Odds package is purchased. Please contact your sales representative for more package details.&#x20;

Live Odds for Golf are delivered via the Unified Odds Feed Competition Odds Producer. Please find producer details below:

* Name: C-Odds
* Description: Competition Odds
* ID: 14 &#x20;

```xml
<producer id="14" name="C-Odds" description="Competition Odds" api_url=" https://api.betradar.com/v1/codds/"
active="true" scope="live" stateful_recovery_window_in_minutes="4320"/>
```

{% hint style="info" %}
**NEW AND IMPORTANT INFORMATION** :arrow\_down:

***

**Pricing Options: Pre-Marginated Odds vs. True Odds**

For Golf on Producer 14 (Competition Odds), Sportradar offers two pricing delivery options depending on how your trading operation manages golf margins.

**1. Pre-Marginated Odds (Default / Market-Ready)**

* *Status:* Default setting for all accounts.
* *What it is:* Markets delivered with provider-calculated margins already applied
* *Recommended for:* Operators who want ready-to-publish golf markets with no need to perform margin shaping or odds ladder calculations in-house.

**2. True Odds (Raw Probabilities / Opt-In)**

* *Status:* Available upon request (opt-in).
* *What it is:* 100% true odds / raw probabilities passed through directly from the provider.
* *Recommended for:* Operators with proprietary pricing/trading systems who wish to apply their own custom margins, bias, and risk models downstream.
* *Implementation requirement:* Because true odds are unmarginated, operators choosing this option *must* apply their own margin logic in their downstream betting engine before offering odds to customers.

***

**Critical Notice: Sportradar Template Configurations (CTRL)**

* Bookmakers activate the market templates they wish to offer.
* *No Effect from Template Changes:* Configuring or modifying Odds Keys, percentage payout targets, or ladders in your Sportradar CTRL templates will *not* alter published Golf odds on either feed:
  * *Pre-Marginated Odds (Default):* Provider margins are passed through intact.
  * *True Odds (Opt-In):* Raw true odds are passed through with no Sportradar margin markup.

***

**How to Configure / Opt In to True Odds**

By default, all accounts receive *Pre-Marginated Odds*.

**To request&#x20;*****True Odds*****:**

Contact your Sportradar Account Manager or Customer Support (<support@sportradar.com>).

Provide your *Bookmaker ID (BMID)*.

Specify: *"**Golf Producer 14: Opt-in to True Odds**"*
{% endhint %}


---

# 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/live-competition-odds/live-odds-golf.md?ask=<question>&goal=<user_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.
