> 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="https://1868790214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1KlIQPveu0EGYCTI8DL1%2Fuploads%2FhMKTobwTqMI3Q4Lt1Jcd%2FSki%20Jumping%20image2022-11-4_16-15-23.png?alt=media&amp;token=e3f1d457-3ef4-471d-858f-95df910bc818" 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:

![](https://1868790214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1KlIQPveu0EGYCTI8DL1%2Fuploads%2FW9s2TQK1lXD7WVrckbQ7%2Fimage2022-3-7_13-19-28.png?alt=media\&token=2ed7edf3-0a57-4418-ac73-0e28d473a1fd)

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