> 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/ctrl/guide/configuration/mytemplates-pre-match/margin-oddskey-definition.md).

# Margin (oddskey) definition

When setting up the keys for each market in the template, the user will find a chronological timeline for each market. This allows the user to define exactly when a market will be published and at what key value, and thereafter set predetermined automatic modifications of that key as time progresses.&#x20;

Additionally, the user can choose to set a key value to ‘Inst’ (instantaneous), which ensures it is offered as soon as Betradar’s odds suggestions are available.

For example, in the screenshot below, there are 4 markets visible: each of these 4 markets has had the key set up slightly differently as an example of the possibilities Ctrl affords:

| 3-Way             | The user has selected a number of different keys, the biggest value furthest out from the event (112 as soon as odds are available) with the key gradually shortening as the event draws nearer (103 at 1hr) |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Total             | The user has set a low initial key value (105 as soon as odds are available), which gradually increases as the event draws closer (107 at 3hrs)                                                              |
| Handicap          | The user only wants to publish this market from 7 days prior to the event, with a key of 108                                                                                                                 |
| Halftime/Fulltime | <p>The user wants to offer this market as soon as odds are available, with a key value of 115</p><p> </p>                                                                                                    |

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

{% hint style="info" %}
After adjusting any keys, market status, or market ladders on a template, the user must press save in order to apply the changes.
{% endhint %}

For markets with only 2 outcomes, such as Totals or Handicaps, there is a different way of defining how the odds will be calculated other than the oddskeys: The Permissible Pairs (PP).&#x20;

This means the odds will not be fixed using the margin, but instead will have a table with odds pairings. In order to use this functionality for a specific 2 outcome market, it is possible to switch from ‘keys’ mode to ‘p-pairs’ mode as shown in the screenshot below:

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

Then, it is also necessary to define which Permissible Pairs ladder will be applied throughout the timeline (time dependent sports will allow to apply different ladders and different times of the match). There is a predefined list of possible PP-ladders to choose from:

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


---

# 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/ctrl/guide/configuration/mytemplates-pre-match/margin-oddskey-definition.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.
