> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/user-guide/booking-events-and-odds-settings.md).

# Booking Events & Odds

Order fixtures and configure odds settings

Learn how to subscribe to fixtures and configure your odds display settings.

***

## Fixture Ordering

[**Fixture Ordering**](https://docs.lsports.eu/u/trade/user-guide/booking-events-and-odds-settings/fixture-ordering.md) — Subscribe to sporting events

* Order fixtures by sport, league, or individual event
* Apply templates for quick configuration
* Set up automatic ordering rules

***

## Odds Settings

[**Odds Settings**](https://docs.lsports.eu/u/trade/user-guide/booking-events-and-odds-settings/odds-settings.md) — Configure how odds are displayed and calculated

* Set margins at sport, league, or market level
* Configure mainline/baseline preferences
* Apply odds ladders for rounding

***

## Line Limits

[**Max Number of Lines**](https://docs.lsports.eu/u/trade/user-guide/booking-events-and-odds-settings/max-number-of-lines.md) — Control line depth per market

* Set maximum lines for handicap markets
* Configure over/under line limits
* Optimize data volume

***

## Workflow

1. **Check coverage** — Review provider availability for your target events
2. **Order fixtures** — Subscribe to the events you need
3. **Configure odds** — Set margins and display preferences
4. **Monitor** — Track on the [Trading Floor](https://docs.lsports.eu/u/trade/user-guide/operational/trading-floor.md)


---

# 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.lsports.eu/u/trade/user-guide/booking-events-and-odds-settings.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.
