> 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/imga-dl-trading-odds-distribution/odds-distribution-service/supported-market-types.md).

# Supported Market Types

Having assessed the different market types, analysed the spread of popularity and handle across each market, IMGA and DL have come up with a list of High, Medium and Low Priority markets to get live. High will be ready for PGA tour events in time for 15th May 2025 (USPGA Champ), Medium will be for 29th May and Low are yet to be determined the importance of each one. For DPWT, the High and Medium markets will be available from KLM Open on 5th June and for LPGA from 19th June.

**`Note`**: the high and medium level markets will be re-created as per the Mustard service and are non negotiable. All the low priority markets are still being assessed on their merits, so please don't assume these will all be live. However, if any of these low priority markets are crucial or you need more information, please let us know via [support@sportradar.com](mailto:support@imgarena.com).

**Data Coverage**

* L1 - only used for PGA events. This is the PGA full live shotlink system (Camera systems on tees and greens, walking scorers and 6 producers in the truck all focused on data quality). Addressing ball/hit ball, approx/detailed lies etc
* L1.5 only relevant for a very small subset of IMGA live collected tournaments (typically something like The Open or Scottish Open or European Ryder Cup where IMGA collect green cam data). Other than green cam data, IMGA collect the full live walking scorer data- addressing ball/hit ball, approx/detailed lies etc
* L1.75 - this will be for 90% of DPWT tournaments (IMGA live collected tournaments). No green camera collected data but instead measured with lasers by walking scorers as well as addressing ball/hit ball, approx/detailed lies data etc
* L2 - Live scorecard data on course with no stroke by stoke data
* L3 - as above but 'live' leaderboard data at high latency and either collected off broadcast or in venue but with a reduced scorer presence

**Market Coverage**

* Markets 1 (DL1): Full In-Play Market offering
* Markets 2 (DL2): Tournaments markets full inlay, player markets only featured groups.
* Markets 3 (DL3): Hole Winner and Hole Scores
* Markets 3.5 (DL 3.5): Tournament Winner, First Round Leader, Groups and Nationalities (InPlay) 2/3 Ball winner (Pre-Match)
* Markets 4 (DL 4): Tournament Winner, First Round Leader, Groups and Nationalities (InPlay)
* Markets 5 (DL 5): Tournament Winner, First Round Leader, Groups and Nationalities (DL decision to trading some inlay but mainly deadball)

{% file src="/files/vy6yZNHf7izqCRBla6fG" %}


---

# 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/imga-dl-trading-odds-distribution/odds-distribution-service/supported-market-types.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.
