> 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/betlink-integration/markets-and-selections.md).

# Markets and Selections

Betting via the BetLink platform is done via markets and selections.

**Market** - A market is defined as a specific betting scenario that has two or more potential outcomes. An example would be a 90 minute outright market for a football match that would have three possible outcomes; team A win, team B win and draw. In BetLink, these outcomes are known as 'selections'.

**Selection** - selections represent the possible outcomes of a market. There can be many selections in a market (e.g. the outright win market for a golf tournament will have every single player as a selection) or there can be few but there will always be at least two selections. Selections are linked one to one with a fluid price for that particular outcome at any given time. As events unfold, the price being offered for a selection can change as it becomes more or less likely to occur.

**Updates** - BetLink updates the prices of selections in real time as events unfold and this is represented on screen to the user via animations and shading on the prices themselves. Markets may also be suspended and removed on the fly for a range of reasons.


---

# 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/betlink-integration/markets-and-selections.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.