> 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.md).

# Live Odds - Ski Jumping

Live Odds for Ski Jumping are offered for the World Cup and World Championship competitions.\
Explore the [Live Odds market overview](/uof/introduction/market-overview-uof-and-cb.md).\
\
All Ski Jumping competitions will be automatically booked once the required Winter Sports package is purchased and active in ISA. Please contact your sales representative for more package details.&#x20;

Live Odds Ski Jumping 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"/>
```


---

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