Access Methods
The Betradar’s Unified Odds information can be accessed in two ways:
Unified Feed Software Development Kit (SDK) in Java, .NET, and .NET Standard
Directly at the protocol level via API & AMQP
We maintain consistent naming conventions and data types across all aspects of Unified Odds, whether you're using the SDK or our protocols. For example, terms like odds, fixtures, competitors, and sports are standardized across all endpoints.
Benefits of SDK over Protocol (API)
We recommend using our SDK, as it offers clear advantages like faster integration, immediate access to new features, a single object model, automatic recovery and connection handling, automatic API lookups, and in-memory caching, etc.
Automatic API Lookups: The SDK hides the separation between messages and API lookups.
The client system just receives the message objects where all information is prefilled by the SDK caches. In some cases, it is looked up in the background when the client system requests some more rarely requested information.
The SDK automatically takes care of dynamic text markets and outright markets, which requires some extra logic and lookups for someone not using the SDK.
Language support: The SDK takes care of translations transparently. The client system just needs to define what languages it needs.
Connection and recovery handling: The SDK handles initial connect and state, as well as recovery in case of a temporary disconnect. This needs to be handled manually by someone not using the SDK.
In-memory caching: The SDK provides an up-to-date cache of each sport-events current status that is updated automatically.
Working with SDK
Betradar provides a dedicated SDK for accessing the Unified Odds in Java, .NET and .NET Standard.
The Unified Odds SDK provides a simple and efficient way for bookmakers to access Betradar's odds and sports information. It combines subscription of messages and API calls into a unified Java or .NET or NET Standard interface that hides most of the complexity, including connection and recovery handling.
For more information, see Unified Odds Feed SDK.
The SDK has dedicated documentation in all the Java, .NET, and .NET standard versions.
The preferred and recommended mechanism is the Unified Feed SDK, as it helps simplify protocol handling especially things like caching of descriptive localized meanings of markets, outcomes, players, teams, etc. Unless fine-grained control is a requirement, you can focus on the SDK and can safely disregard the protocol specification. Also, the SDK supports all feed features and handles most situations out of the box, and helps to speed up the integration with that.
If you cannot work with the SDK, the protocols can be used instead. But this will add more complexity.
Working with Protocols
When programming directly at the protocol level, you must handle additional elements and attributes where specified in the corresponding schemas. This enables Betradar to add new functionality when it becomes available, and for you to take advantage of such information when convenient. No existing required data is removed or renamed.
If such changes are made, the existing feed works for at least 24 months after such a change has been made.
Protocol Mechanisms
Unified Odds are provided through 2 different protocol mechanisms:
Messaging over Advanced Messaging Queue Protocol (AMQP)
HTTP/XML-based Application Programming Interface (API)
Unified Odds Feed uses AMQP as a protocol for delivering messages and a RESTful API for delivering additional information.
It is always required to use both AMQP and API to fully use all the functionalities of the Unified Odds Feed.
All the dynamic frequently changing information is delivered through lightweight messages using the AMQP protocol. AMQP is used as one-way communication, where messages are pushed to the client’s system, and no requests can be made towards it.
The Unified Odds Messages provide fast real-time updates to key information, such as odds over AMQP (0.9.1)/XML. All AMQP messages are sent on various topics that are intended to provide easy and flexible routing/filtering. More information about how the topic filtering works can be found here.
Last updated
Was this helpful?