> 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/documentation-1/tournaments-vs-competitions.md).

# Tournaments vs Competitions

Within our data is is important to distinguish between a Tournament and a Competition.

Competitions are sub sets of tournaments. The tournament is the over-arching event, and the competitions happen within these tournaments.

Within each tournament there are multiple competitions, e.g. Men's Singles, Men's Doubles, Women's Doubles, e.t.c.. These competitions are knockout competitions that have a single winner.

Each of these Competitions has their own ID - although in every case the Men's Singles and Doubles (and Women's Singles and Doubles) will have the same competition ID (see examples below).

Example - Wimbledon:

![](https://files.readme.io/6752108-Screen_Shot_2017-06-22_at_16.19.49.png)

**Grand Slam Tournament IMG Covers:**

* The Championships 2024, Wimbledon (Tournament ID: 11956)

**Competitions IMG Cover within this:**

* Wimbledon Men's Championships 2024 (Competition ID: 2024-0540, the same for both Singles and Doubles)
* Wimbledon Women's Championships 2024 (Competition ID: 2024-0904, the same for both Singles and Doubles)
* Wimbledon Mixed Doubles Championships 2024 (Competition ID: 2024-0005)


---

# 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/documentation-1/tournaments-vs-competitions.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.