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

# Class Hierarchies

Bookmakers rely on time-critical data to provide betting information to punters in a timely fashion. Messages received through the feed contain critical information (market\_ids, outcome\_ids, odds) which should be processed in a timely fashion

Additional information like market names/ outcome names and sport event metadata are obtained via method calls on java/.NET classes which results in issuing HTTP requests to sports API, when relevant data is not previously cached within the SDK. 

In cases the relevant information is accessible in multiple endpoints - the summary endpoint is going to be called to fetch this data for each configured language. Be mindful that HTTP requests might take a considerable amount of time or even fail, so the full message processing could take a longer period of time.

{% hint style="info" %}
Please note that one of the main uses of SDK is to translate feed/API XML payloads into classes. In most cases, the data is exposed in a similar way to how it is obtained from the feed or API. However, there are some structural differences. 
{% endhint %}


---

# 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:

```
GET https://docs.sportradar.com/uof/sdk/languages/java/class-hierarchies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.