> 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/support-and-history/archived/deprecated-uof-endpoints/elements/tournament.md).
# Tournament
The tournament element provides information about the email tournament and contains 2 sub-elements which are:
* sport
* category
Here follows an example of the tournament element shown in the fixture end point.
```
```
List of attributes in the tournament element:
| Attribute | Meaning | Possible values |
| --------- | ----------------------------------------------------------------- | --------------------------------------------------------------------- |
| id | Unique id of the competition the fixture belongs in | String value, example:
|
| name | Name of the tournament (main competition) the fixture belongs in | String value, example:
|
List of attributes in the sport sub-element:
| Attribute | Meaning | Possible values |
| --------- | ------------------------------------- | --------------------------------------------------------------- |
| id | Unique id of the sport of the fixture | String value, example:
|
| name | Name of the sport | String value, example:
|
List of attributes in the category sub-element:
| Attribute | Meaning | Possible values |
| ------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| id | Unique id of the category. The category addresses the country where the tournament is taking place | String value, example:
|
| name | Name of the category | String value, example:
|
| country\_code | Code of the country for the category | String value, example:
|
---
# 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/uof/support-and-history/archived/deprecated-uof-endpoints/elements/tournament.md?ask=&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.