> 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/multiple-lines-configuration.md).

# Multiple Lines Configuration

When clicking on the odds key, the user can also find line configuration tools as shown below (in red).

<figure><img src="https://2462374060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePWvwv8SZVMy3wnD1Faz%2Fuploads%2FqAGIdyIYItoLFuoKsQj6%2Fannotely_image.png?alt=media&amp;token=7311f6c1-9782-4945-b924-f2cc9eb88567" alt=""><figcaption></figcaption></figure>

***Multiple Lines Configuration > Lines***

The multiple line configuration tools allow the user to select which types of lines they would like to enable. To do this, it is necessary to check the box(es) to specify the granularity of the lines - x.25, x5, x.75, and x.0 (red box above). The x.5 line is standard, meaning it is greyed out as it cannot be disabled on any market with multiple lines.

***Multiple Lines Configuration > Max Number of Lines***

Additionally, the maximum number of lines allowed for that market at any one time can be limited using the ‘Max Number’ drop down menu . This means that the most balanced line will always be taken and the necessary lines above and below will be added until the defined number is reached.

***Multiple Lines Configuration > Range Limitation***

Finally, on markets with multiple lines, the template row can be expanded using the ‘open market config’ tab (blue below) to show the range limitation field.

{% tabs %}
{% tab title="English" %}

{% @storylane/embed subdomain="app" linkValue="47bwkfqffs0l" url="<https://app.storylane.io/share/47bwkfqffs0l>" %}
{% endtab %}

{% tab title="Spanish" %}
{% @storylane/embed subdomain="app" linkValue="aihat8hoym5f" url="<https://app.storylane.io/share/aihat8hoym5f>" %}
{% endtab %}
{% endtabs %}


---

# 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/ctrl/guide/configuration/mytemplates-pre-match/multiple-lines-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.
