> 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/tennis/schedule-endpoints-restful-1/tournaments-id-draws.md).

# Tournament Draws

This endpoint lists the draws for a tournament. This includes the placeholders for matches in each round of the competition.

A typical Tennis draw is an expected set of matchups within a tennis tournament which is a knockout competition. Every match a player wins, they are entered into the next round of the draw

![](https://files.readme.io/22b1fd9-Screen_Shot_2017-03-14_at_18.27.44.png)

A Tennis draw on the DDE is first of all defined by the draw type, with each competition in a tennis tournament having its own draw.

For example, the majority of tennis tournaments require one or more qualifying rounds, which typically take place over the weekend before the tournament week starting. On the DDE, a qualifying round can be identified by each match's specific event ID. Event IDs are explained in detail on [this](https://img-arena.gitbook.io/tennis/-M-nnUijRFbIhBBjSfUz/documentation/how-are-event-ids-structured) page.

We recommend that you request the REST endpoint every minute so that you have the most up-to-date information on the draws from live/upcoming tournaments.

Legacy URL:  `https://dde-api.data.imgarena.com/tournaments/{id}/draws` (decommissioning on 30th Sept 2026)

**NEW URL:** `https://dde-api.data.srarena.io/tournaments/{id}/draws`

## Request Parameters

This endpoint currently takes no request parameters, we aim to add them, and once we have they will be detailed here.


---

# 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/tennis/schedule-endpoints-restful-1/tournaments-id-draws.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.