> 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/sport_event_condition.md).

# Sport\_event\_condition

### **Sport event conditions** <a href="#sport_event_condition-sporteventconditions" id="sport_event_condition-sporteventconditions"></a>

This element identifies several features related to the event (see example below).

![](https://1868790214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1KlIQPveu0EGYCTI8DL1%2Fuploads%2FwOknwmZLJt9WaT23eNXV%2F42696984.png?alt=media)

Table below shows all attributes with possible values and meaning.

| Attributes of sport\_event\_condition | possible values | meaning                                                 |
| ------------------------------------- | --------------- | ------------------------------------------------------- |
| Attendance                            | Integer         | number of people who attended the match                 |
| match\_mode                           | bo3, bo5, bo7   | used for sports like tennis which has best of 3,5,7 etc |

Table below shows possible values and meaning of the sub-elements of the sport\_event\_conditions

| Possible sub-elements in sport\_event\_conditions |
| ------------------------------------------------- |
| referee                                           |
| venue                                             |
| pitcher                                           |
| pitcher history                                   |

Attributes of **referee** with possible values and meaning

| Attribute   | meaning                    | possible values       |
| ----------- | -------------------------- | --------------------- |
| id          | id of the referee          | id = sr:referee:81627 |
| name        | name of the referee        | string                |
| nationality | nationality of the referee | string                |

<br>

For more detailed info related to the **Venue** element, please, check the following page: Venue&#x20;

For more detailed info related to the **Pitcher and Pitcher history**, please, check the following page: Pitcher and Pitcher history


---

# 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/sport_event_condition.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.