Our business depends on being able to help you connect our sports odds data feed to your systems.

This page provides information and documentation downloads to help make that process as smooth as possible. If you cannot find what you are looking for, contact us and we will help you find what you need. 

FUSION - Key facts


  • Fusion is a new product designed for streaming extremely low-latency odds.
  • Reference data required to support the odds (fixtures, fixturegroups, competitions, bookmakers, sports, countries and odds types available now, participants and to follow) is supplied by the same mechanism and in the same format.
  • Data for odds, fixtures, fixturegroups and competitions is supplied in a similar manner, context is shipped first followed by streaming of updates.
  • Odds are classified using SuperOddsTypes a method of concisely classifying odds to avoid issues encountered when mapping traditional odds types. Content
  • Low-latency data streams shipped via subscriber-specific channels.
  • Integration, de-duplication and normalisation of raw source data into a unified representation known as SuperOddsTypes.
  • A unique subscription query mechanism based on client-selected data cubes according to such dimensions as sports, bookmakers or odds types.
  • Concurrent client subscriptions can be started or stopped independently. Each new subscription can start by optionally shipping a fully consistent context, i.e., all the offers corresponding to the specified subscription query or alternative options for “gap-filling”, i.e., to request messages between your last subscription and now. All other offers (and associated timestamps) for the bookmakers specified in the query included with each update, simplifying the logic on the clients.
  • Always adding new improvements to data consistency, sports coverage and latency optimisation. Technology
  • Fusion utilizes HTTP / Server-Sent Events (SSE) as a transport mechanism to stream the odds. • This uses regular HTTP requests for the persistent connection, not a special protocol greatly simplifying the integration process.
  • Connections are initiated by the client, and once connected the server will send events in text/event-stream format without closing the connection.
  • Similar to WebSockets in that they happen in real time, SSE are a one-way read-only communication method from the server.
  • SSE allows clients to automatically re-connect if the connection is interrupted and the data stream can be continued from the point of interruption, so no messages are lost.
  • Unique IDs are sent with each message from the server allowing the client to send the most recent when reconnecting.
  • It is possible to have many streams open at the same time with the SSE streams being multiplexed over the same physical connection.
  • Compression can also be requested by the client to further reduce bandwidth consumption and decrease latency.
  • Highly available, resilient and load tested Odds Distributor endpoints from which to consume data.
  • Heartbeats are published by the Odds Distributor so Clients can monitor the status of the service.

Legacy Systems

TXODDS has several different feeds AHC, xml2 & Push that can deliver information about competitions, fixtures, and odds. Although these systems are designed to inter-operate there are inevitably some issues e.g., AHC and xml2 both maintain their own identifier for the fixture. Most of the information across the feeds is consistent, so competitions, leagues, participants, countries, bookmakers and sports will have the same identifiers and names across all feeds.
As the new fixtures system Merlin is introduced there will be a new identifier for fixtures, fixturegroups and competitions. These are referred to in this documentation as the Merlin IDs. In time Merlin will become the new source for all other information such as participants, countries, bookmakers and sports and as such these will have a Merlin ID. For a period of time many Merlin IDs will be the same as the AHC and xml2 Ids, however in time they will diverge the aim being Merlin will become the single authoritative source for all IDs across TXODDS.

Fusion makes use of Merlin IDs, but to protect existing customers investment in AHC and xml2 integration, the IDs generated by these systems will be available in the Fusion feed but marked as Legacy. Although this increases the payload of the messages, future enhancements to the system for “Items of Interest” will allow customers to select which fields they would like to be supplied in the feed, and if not required Legacy fields can be dropped from the subscription.

Users of Fusion will therefore be able to obtain all required information to support the odds subscriptions from Fusion itself without having to rely on other feeds. The customer experience and integration effort will be greatly simplified as all feeds will be delivered in a single, consistent manner.

General Architecture

The service allows a client to have one or more subscriptions concurrently, with each subscription’s scope (or interest) expressed in a very simple subscription DSL. The client application communicates with the server-side Odds Distributor component that authorises and manages all the current customer subscriptions.

Basic Fusion Streaming Features


Odds Distributor endpoints are available only via HTTPS to provide encryption to ensure your requests are being sent to our servers and to protect the privacy and integrity of the exchanged data from malicious attacks or being read by a third party. Customers will need to supply external facing IP addresses from which they will connect as these will have to be added to the allow list on the firewall. Customer subscriptions will be required to supply credentials for authentication and access to the feeds.

Time Sensitivity

Each data request is time stamped to the millisecond, so you immediately know: • when the data was last verified as accurate on our server whether the price has moved or is simply still the same as before. • if a bookmaker site is down for maintenance or is currently overloaded and we can’t get the price we won’t update the timestamp until we can verify it again. • allows you to decide what information you act upon. If you want to filter out anything over 10 minutes old, you can do so.

Data on Demand

TXODDS data is broken down into different market segments to allow you full control over what information you get and when you get it. For example, you can request information by:

• sport e.g. Football/soccer by country or American football NCAA
• league or event e.g. English Premiership, Champions League etc.
• odds type e.g. Asian Handicap or 3Way Odds
• bookmaker e.g. only Ladbrokes and William Hill
• by time e.g. only updated odds since your last request this allows the request size to be kept to a minimum and speed to a maximum.

Of course, if you want all international football league matches for all odds types and all bookmakers currently being quoted then you can have that too. Depending on how much server resource and bandwidth you have you may want to split the requests into multiple sessions/requests for each sport.

Context & Updates Only

You can request only updates to the odds you are interested in, so no need to refresh the entire catalogue of event(s) constantly thereby reducing your server bandwidth and processing resources. As mentioned earlier each odds price on our server has a timestamp declaring when it was last updated. Each time you make a request from our server we also send our server timestamp along with that request too. So, for example, you can request data from us that has changed in the last 30 seconds, 30 minutes as required, using the server timestamp.

Additionally, the Fusion feed transport uses Server Side Events/Eventsource which can provide an automatic request of missed messages. This may depend on the client language used, so please discuss with your support channel for further information.

Note: For consumers that are used to the Push context shipping, Fusion has extended functionality that will also ship suspended/OTB messages from the past 2 hours.

We send our server timestamp which is set to GMT to you to ensure that there are no time zone or clock synchronization problems. Wherever you are in the world or whatever time your local PC or server is set to will not affect the data we send you.

For documentation…


  • Always on, low-latency push service
  • Multiple types of data streams, such as odds enriched with many additional features as well as server-side computed aggregations, TopN updates, and various alerts.
  • Low-latency streams shipped via subscriber-specific push channels.
  • Integration, de-duplication and normalisation of raw source data into a unified representation including normalised odds types.
  • Unique subscription query mechanism based on client-selected data cubes according to such dimensions as sports, bookies or odds types, or for single matches.
  • Concurrent client subscriptions can be started or stopped independently.
  • Each new subscription starts by shipping a fully consistent context, i.e., all the offers corresponding to the specified subscription query.
  • Alerting mechanism based on largest moves or comparison between groups of bookies. The alerts are bespoke for each subscription query, so, for example, the TopN moves are computed only for the cube specified in the query.
  • Pre-kickoff optional consensus price TX LINE and goal line included with each update.
  • All other offers (and associated timestamps) for the bookies specified in the query included with each update, simplifying the logic on the clients.
  • Mutual 1×2 < – > handicaps conversion on the fly.
  • A count of score changes included with the updates.
  • TXLIVE — predicted odds representing normally expected odds, based on a model built using the machine learning techniques.
  • Historical playback of matches.
  • Always adding new improvements to data consistency, sports coverage and latency optimisation.


  • The push paradigm simplifies the client integration effort—simply listen to updates and process each new message one at a time without the need of storing any data on the client.
  • Event processing infrastructure utilising a production cluster of Tibco StreamBase nodes. StreamBase offers a very fast update cycle for new and updated server-side algorithms.
  • Included samples for Java, C# and JavaScript WebSockets integration.
  • Resilient architecture with transparent reconnection mechanisms for planned and unexpected restarts.
  • The system is used in production with major customers.

For documentation…


The TXODDS MARKET ODDS FEED allows you to create custom “normalised” XML output for monitoring any combination of our 200+ bookmakers and odds types across all sports & betting markets covered:

  • 1×2, moneylines, Asian handicaps, totals, handicaps, odds/even, goal/no goal, ht/ft, crs, 1st half etc. across all sports covered.
  • Set any odds/bookmaker combination and monitor current odds in the marketplace.
  • Set any custom average odds combination and monitor global markets.
  • Use XML “last time stamp” feature to monitor all/any custom odds changes according to your settings.
  • Monitor rapid odds movements and potential arbitrage/liability situations.
  • The possibilities are endless, and the TXODDS MARKET ODDS FEED is updated in line with the live master odds database, enabling versatile processing of multiple data streams in a standardised format. Essentially, this enables your own database to connect directly to and respond to events happening 24/7 in the global sports betting market.

For documentation…


The most comprehensive and accessible data relating to sports betting available in the world.

  • Access the world’s biggest archive of timestamped sports betting odds data.
  • Leverage the latest Big Data technologies for statistical and historical analysis.
  • Execute complex queries and enjoy fast response times.
  • Perform quantitative analysis, competitor analysis, historical pricing analysis.
  • Ideal for back-testing, enhancing your existing models and custom reporting
  • Instant access to comparative analysis and reporting on operator/competitor coverage.
  • Providing insight into a wide range of dimensions i.e. which leagues are covered by which bookmakers, identifying gaps in operator coverage related to leagues, odds types or lines
  • Provide multiple aggregations such as match count, average over-rounds etc
  • Create and bookmaker your queries for re-use
  • Download results in CSV for further analysis and reporting either manually or by default


  • Latest “Big Data” technologies developed in other fields to order and easily manage trillions of pieces of odds data.
  • Hadoop infrastructure, no more requirements for handling large SQL files or data dumps.

For documentation…