> 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-ski-jumping/ski-jumping-live-odds-configuration.md).

# Ski Jumping Live Odds Configuration

The Live Odds markets for Ski Jumping can be activated within CTRL by accessing the market configuration templates:

<https://ctrl.betradar.com/configuration/templates/list?activeId=true&sportId=48&typeId=CODDS>

There you will find the following template:

* competition template

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

Templates can be assigned on different levels and will be inherited accordingly as described in the example below:

&#x20; \> **Sport** (Ski Jumping)

&#x20;     \> **Season** (e.g. Ski Alpine 2022/23)

&#x20;         \> **Discipline** (e.g. Overall, World Cup)

&#x20;                \> **Event** (e.g. Oberstdorf, HS 137)

&#x20;                      \> Run (Jump)

{% hint style="danger" %}
Event Stage

The trading takes place on the event stage.&#x20;
{% endhint %}

If a template like this one is assigned on sport level, it will be inherited for every event except those events which have a dedicated template assigned.

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

The key for the winner market can be configured dynamically\
by setting a Base key, a Key increment per outcome and a Max key as shown below:

![](/files/4xFQDAEpJdDAFQlytmp8)

If a competitor retires or has already finished and does not lead the competition, the key will be adjusted by the configured increment in order to stay competitive.
{% 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 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/live-competition-odds/live-odds-ski-jumping/ski-jumping-live-odds-configuration.md?ask=<question>&goal=<endgoal>
```

`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.