Introduction and Integration Specifics
What is OneFeed?
OneFeed is a new service that allows sportsbook providers to have their risk management carried out by one centralized cutting-edge service, retaining also the access to all MTS features (AI models, Alpha Odds, etc.).
This new service enables the conversion of sports data and odds feeds from non-Sportradar suppliers to a UOF-compatible (Unified Odds Feed) format. When using OneFeed, MTS and Insight Tech can recognize the content and carry out full risk management services regardless of the source of the feed.
In addition, a significant benefit of OneFeed is to allow bookmakers to support and maintain a single integration: avoiding development effort, reducing integration times and maintenance costs, while achieving a shorter time-to-market thanks to the UOF-compatible format.
OneFeed is not a data provider on its own, it serves as Feed Aggregator and Converter, which means that each client is responsible for their own commercial relationship with the external data provider(s) they want to use.
What does OneFeed offer?
Sportradar Products – access to be agreed with your Sportradar sales representative
UOF Prematch (PRE)
✅ already supported
-
As a pass-through
UOF Live Odds (LO)
-
✅ already supported
As a pass-through
UOF BetPal (BP)
-
✅ already supported
As a pass-through
UOF Alpha Odds (AO)
⚠️ in progress
⚠️ in progress
UOF Premium Cricket (PC)
⚠️ in progress
⚠️ in progress
As a pass-through
UOF Competition Odds (CO)
-
⚠️ in progress
As a pass-through
3rd Party Independent Products – access to be agreed directly with each provider
InnBets
✅ already supported
-
See explanation below
InnPlay
-
✅ already supported
See explanation below
BetGenius
⛔ not supported
✅ already supported
Some Live markets to be still mapped
Oddin
✅ already supported
✅ already supported
Zoom
✅ already supported
✅ already supported
LSports
⛔ not supported
✅ already supported
Beter
✅ already supported
✅ already supported
Infront
✅ already supported
-
Tennis ITF (using InnBets)
DST
✅ already supported
✅ already supported
Player Props
⚠️ in progress for Custom Bets
OneFeed is a functionality that is currently quickly developing (in close cooperation with a partner company called InnProjekt), so if you would like it to start supporting additional data providers, do not hesitate to reach out to your Sportradar sales representative or Operational Account Manager (OAM), and they will connect you with relevant people, so each case can be evaluated individually.
Related products
To complement your operations you can also consider the following related products that complete the management suite:
InnBets:
Monitoring of competitors and the data sent in real-time allows the bookmaker to always be competitive and in line with the sportsbook market.
Possibility to create new matches on the schedule, using thousands of markets available, as well as to create new fantasy matches (team vs. team, team vs. player) to extend the offer.
An infinite quantity of produced markets and the possibility of creating new ones, linked to a tailor-made calculation algorithm created ad-hoc for each customer, makes it the most competitive and most current tool to manage and improve the performance of each single bookmaker. Using this sports betting solution, the result is a rapid and significant enhancement of the company’s performance.
Technology: the platform is highly innovative both from the IT and mathematical points of view: it allows, as a matter of fact, to work on the entire pregame in a simple, efficient and fast way, minimizing the risk of mistakes due to lack of attention.
InnPlay:
Using InnPlay bookmakers can easily manage tons of side bets with extra focus on Player Props. The bookmaker can independently manage the variation of odds, control the market and player trends. This sports betting tool can be adapted to any type of live event, all in a single screen.
Increase the offer of the player markets: side bets of all types for each player, such as Assists, Cards, Crosses, Fouls, Passes, Shots, Shots On Target, Scorers with hundreds of markets.
InnPlay is closely related to InnBets: once the prematch is closed, InnPlay generates the odds. Based on the placed bets that the bookmaker received, InnPlay will balance the odds with the margins the bookmaker has set.
Competitive advantage: this tool is based on sophisticated and always up-to-date mathematical calculations, which can be highly customized for the needs of the bookmaker, creating a tailor-made service that gives an unprecedented competitive advantage to those who use it.
LiveSelector:
Live Selector is a booking planning management tool, and it’s a must-have: bookmakers can manage the live sports betting bookings, preventing the risk of a double purchase of the same match, and not forgetting to book the matches. All this on one page.
Automatically organize the entire schedule: Live Selector, having been developed within the InnBets platform, has a section where the bookmaker can choose for each competition (or country) which provider to rely on. It only needs to be configured once.
With a simple click on the screen, the bookmaker has the possibility to make the Booking for the live matches. All of this is possible by always following the all-in-one philosophy: buying from all the providers on a single page.
Current constraints
While using OneFeed, please consider the following limitations and constraints that are currently present:
UOF Content: as described in the table above, the support for the following features is still in development: Premium Cricket, Competition Odds, UOF CustomBet API and Probabilities API. To use those features in combination with OneFeed, the client has to set up a secondary instance that will be connecting directly to the UOF to consume that data, while the primary instance will be connected to OneFeed for the external provider feed data.
3rd Party markets: new markets published by non-Sportradar providers need a few weeks to be prepared and mapped in a UOF-compatible format. During this time, OneFeed cannot push those markets to the clients, and MTS cannot manage risk for them.
The mapping process is always ongoing with scheduled releases, depending on the new markets published by the providers.
Alpha Odds: Alpha odds are not compatible with enhanced prematch (InnBets) and
live (InnPlay) products. The two are mutually exclusive, so the client has to choose either Alpha Odds or the enhanced services.
Double-booking: In case the client did not decide to use LiveSelector for match booking from multiple providers, it is their sole responsibility to prevent double-booking of the events. In case this still accidentally happens, MTS will reject all tickets placed on such matches with code -450 Event has multiple booking sources.
OneFeed specifics
Please, keep in mind that some minor aspects behave differently between OneFeed and UOF.
<reference_ids>
<reference_id name="bg:link:Booked" value="bg:match:11632597" />
</reference_ids><extra_info>
<info key="best_of" value="3" />
<info key="sport_icon" value="https://cdn.oddin.gg/assets/sports/icons/cs2.png" />
<info key="home_underage" value="0" />
<info key="home_icon" value="https://cdn.oddin.gg/assets/teams/icons/preasy_esport.png" />
<info key="away_underage" value="0" />
<info key="away_icon" value="https://cdn.oddin.gg/assets/teams/icons/adepts.png" />
</extra_info>OneFeed producers
In OneFeed, we've introduced dedicated producer IDs for external content, where the first two numbers indicate the provider, while the last two correspond to the UOF producers. This is configurable, so you can go in this direction or have it the same way as UOF, which would be just id=1, but our recommendation would be to have dedicated ones.
I.e. for BetGenius Live that would be producer 1201 - 12 reserved for BG, 01 meaning LiveOdds. Benefits of having separate producer IDs are:
UOF protocol compliance
When a given producer encounters an error, it stops producing periodic "alive" messages. As a result, the consumers stop all betting offer associated with the producer. When multiple 3rd party feeds are merged into a single producer, this is no longer possible, since stopping the producer would stop the betting on all 3rd party feeds. For example: BG live and Oddin live are merged into a single OneFeed producer. If BG fails, OneFeed's live producer as a whole cannot be marked as down, since this would also stop Oddin's betting offer. Instead, the OneFeed Live producer must remain active, and the BG betting offer needs to be stopped by an artificial bet_stop message for each individual BG event.
Simplified recovery
When multiple 3rd party feeds are merged into a single OneFeed producer, handling recovery requests becomes complicated. When the consumer starts the recovery, OneFeed has to produce recovery messages for all 3rd party providers merged into the producer, which unnecessarily increases the processing load on both sides. If a given OneFeed producer represents only one 3rd party feed, the recovery requests on the producer can be performed simply by precisely triggering the recovery operation on the target 3rd party feed.
Detection of source feed
If only one 3rd party feed is represented by a given OneFeed producer, detecting which feed produced a betting offer for a given event becomes trivial, since the feed can be identified by inspecting which producer produced the markets associated with the event.
Separate Producer IDs
11
1101-1199
Live = 1101
Prematch = 1103
BetPal = 1104
PremiumCricket = 1105
C-Odds = 1114
BetRadar
sr
Prematch + Live
12
1201-1299
Live = 1201
BetGenius
bg
Only Live
13
1301-1399
Live = 1301
LSports
ls
Only Live
14
1401-1499
Live = 1401
RunningBall
rb
Only Live
15
1501-1599
Live = 1501
Prematch = 1503
Pinnacle
pn
Prematch + Live
16
1601-1699
Live = 1601
Opta
op
Only Live
17
1701-1799
Live = 1701
Prematch = 1703
Oddin
od
Prematch + Live
18
1801-1899
Prematch = 1803
StatsPerform
sp
Only Prematch
19
1901-1999
Live = 1901
Prematch = 1903
ALT Sports Data
at
Prematch + Live
20
Reserved
Reserved
21
Reserved
Reserved
22
2201-2299
Live = 2201
Prematch = 2203
Zoom
zm
Prematch + Live
23
2301-2399
Live = 2301
Prematch = 2303
Beter
be
Prematch + Live
24
2401-2499
Live = 2401
Prematch = 2403
Infront
if
Prematch + Live
25
2501-2599
Live = 2501
Prematch = 2503
DST
ds
Prematch + Live
(Player Props)
99
9901-9999
Live = 9901
Prematch = 9903
InnProjekt
-
Internal
Introductory call
After you have decided that you want to start using OneFeed services, we will first have to organize an introductory call to collect the needed input from your side and provide potential clarifications and answers to your questions. The participants on the call should be business and technical decision-makers from your side, and sales, product, account, service and programme management representatives from Sportradar side.
As a minimum, we would like to discuss the following:
Total intended scope of your offer in production - providers, producers, sports, functionalities…
Offer that you expect to run through OneFeed and what will continue being consumed directly from the source
Usage of other related products (i.e. B.E.T. widgets, VAIX marketing services, Alpha Odds, InnBets, InnPlay, Live Selector)
Number of UOF-supported languages and location of your servers
Timelines for your and our testing and your launch to production
OneFeed instance preparation
After this call we will initiate the preparation of your dedicated instance. At this point the next steps greatly differ based on the type of external provider.
1
Communications: depending on the external provider we can handle most of them, or it will be up to you.
2
Credentials: extra settings and credentials for the external content will be needed, depending on the provider.
3
IP whitelisting: depending on the provider, we can make the request, or you will have to handle it by yourself.
4
After we receive all required details, we can start loading the full feed content from all providers, which can take several business days.
The duration of this initial load increases with the number of used languages.
5
When all the data is loaded and we will do the first sanity check from our side, we will finalize the OneFeed credentials for you.
6
Securely encrypted credentials will be shared with you via email or in the active chat, so you can connect to OneFeed and the testing phase can begin. They will look like this:
7
Before your launch to production, we will need to conduct QA and E2E testing from our side as well, for which we must have enough content available for betting, and url and test accounts to access your non-productive front end. Match booking can either be done by you or by us directly, if you give us permissions.
8
When both parties are happy with the results of the testing process, we can start discussing the launch plans. Instances on our side will have to be promoted to production and integration data replaced with production, which once again takes a few business days, so this final step needs to be carefully aligned between all parties.
At the same time, OneFeed team will create the Production environment for the launch.
Future development on OneFeed
Match Enabler will permit to enable and/or disable to receive data for a specific match from a specific supplier. If the bookmaker decides to stop it when the markets are already open for the match, the tool will notify the bookmaker and, upon a confirmation, it will send the bet_stop message to close the match before stopping the data flow.
Multi-feed user interface (MTS Console) will ensure trading efficiency without sacrificing custom configurations. It will be possible to apply trading-related configurations on various levels, reducing trading effort & costs.
Custom Bet supported through OneFeed will offer a seamless integration of same-event betting from a single endpoint across multiple feed providers.
Last updated
Was this helpful?