> 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/data-and-features/markets-and-outcomes/identify-a-market.md).

# Identify a Market

Betradar Unified Odds uses markets and market lines. Each market is a bet type identified with a unique ID and within a market, multiple different lines are often provided

Each of these lines is uniquely identified by additional specifiers (e.g. Total Goals 2.5 is the same market as Total Goals 1.5, but it is two different market lines. The market ID for both are the same, but the first one has a specifier ((goals=2.5)) and the other one has a specifier ((goals=1.5)) that uniquely identifies them). 

*XML example of the same market with 2 different market lines.*

{% code title="XML example" %}

```xml
<market name="Total" id="18" specifiers="total=3.5" status="1">
    <outcome name="over 3.5" active="1" id="12" odds="2.3"/>
    <outcome name="under 3.5" active="1" id="13" odds="1.55"/>
</market>
 
 
<market name="Total" id="18" specifiers="total=2.75" status="1">
    <outcome name="under 2.5" active="1" id="13" odds="2.1"/>
    <outcome name="over 2.5" active="1" id="12" odds="1.65"/>
</market>
```

{% endcode %}

The market lifetime for a sport event typically begins when Betradar provides pre-match odds – often well before the match starts (and the same market continues to live). If Betradar does not cover a sport event live or the market for some reason, is not suitable live, and the market is closed once the match starts.

In general, markets in the Unified Odds model span pre-match and live. They also use the same IDs and specifiers if the sport event; hasn't started yet, is live, or has ended.


---

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

```
GET https://docs.sportradar.com/uof/data-and-features/markets-and-outcomes/identify-a-market.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.