> 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/sdk/languages/java/class-hierarchies/sporteventstatus.md).

# SportEventStatus

On Competition SportEvent type we can get sport event status. Depending on the type of sport event it needs to be cast to the appropriate status type to get all possible values.

The class diagram below shows all interfaces derived from the SportEventStatus along with methods defined on each one.

#### Class Structure <a href="#uofjavasdksporteventstatus-classstructure" id="uofjavasdksporteventstatus-classstructure"></a>

The following links will lead you to the respective class articles. Each article has three sections consisting of a class/interface description, method summary, and methods details.

**i. For sport event  (competition) status**

> You can access the complete **Unified Odds SDK Java documentation** here:\
> [UnifiedOddsSdkJava Docs](https://sportradar.github.io/UnifiedOddsSdkJava/)

Defines methods used to access general competition status attributes

* CompetitionStatus
* MatchStatus
  * SoccerStatus
* StageStatus

**ii. For sports event (competition) statistics**

Defines methods used to access general competition status attributes

* CompetitionStatistics
  * MatchStatistics
    * SoccerStatistics

Defines methods used to access team statistics

* TeamStatistics

Defines methods used to access specific period statistics

* PeriodStatistics

#### 'CompetitionStatus' Class Diagram <a href="#uofjavasdksporteventstatus-competitionstatusclassdiagram" id="uofjavasdksporteventstatus-competitionstatusclassdiagram"></a>

<figure><img src="/files/hlbr3MV4iAOBtx29wh5A" alt=""><figcaption></figcaption></figure>


---

# 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/uof/sdk/languages/java/class-hierarchies/sporteventstatus.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.