Integration Schema

Owned by Martin Mand
Last updated: Oct 11, 2019 by Tonis Danilson


The V3 Integration Service has been designed to deliver various types of data including fixture information, markets and prices, results, match state and feeds coverage. Service content can be varied according to your requirements so that you can receive only the data types that meet your platform's needs. It includes several features to ensure that you receive the updates you are expecting and have the information necessary to operate an elegant fault-recovery solution. These features make the system robust as well as reliable and secure and are discussed below.

Background

The diagram below shows the logical components of the system.



 The products (shown in the left-hand box of the diagram above, labelled "Sports Data Services") generate messages that are delivered to a customer through a component known as the Integration Service. This component is responsible for converting updates into the format expected by your trading platform. Four types of Integration Service are offered to suit a variety of trading platforms:

  1. OpenBet Feed Handler – deployed only for customers operating OpenBet trading platforms
  2. IGT Evenue – deployed only for customers operating IGT's trading platform
  3. Optima Evenue – deployed only for customers operating Optima's MM2 trading platform
  4. V3 XML IS – deployed for customers developing their own trading platform or providing their own integration into a downstream platform such as OpenBet.




Message snippets and examples in this document are shown in XML but can be delivered through the V3 integration service as either JSON or XML, per your requirements.

If you are not operating an OpenBet or IGT/Optima system, you shall most likely use option 4.
Update messages for OpenBet or Evenue systems are formatted according to the requirements of those systems. The format of update messages sent by the V3 IS is described on this Confluence space.