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.
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.
The following diagrams exemplify some of the most used SDK entities and their hierarchies.
Last updated
Was this helpful?