To allow us to deliver data, we ask that you provide

an HTTP

 endpoint that exposes the following interface:

interface ITradingPlatform
{   
	void   ProcessMessage(string messageXml);   
	void   Heartbeat();
} 

We will then develop a Connector to plug-in to a per-client deployment of our Integration Service to communicate with this endpoint. This enables us to provide bespoke messaging and security provision that precisely meets your requirements. We

then POST

 XML over HTTP secured with SSL/TLS (HTTPS).
The two methods we require are:

• ProcessMessage: responsible for receiving and acknowledging the XML messages sent by the Integration Service.
• Heartbeat: this method is called regularly to confirm that the Integration Service is able to communicate with the endpoint so that appropriate steps can be taken by both parties in the event of a failure in communication between our data centres.

Anchor
_Toc378061307 _Toc378061307

Anchor
_Toc471889142 _Toc471889142

Other Security Options

XML is used, delivered via HTTP POST and secured with SSL/TLS (HTTPS); other serialisation, authentication or security systems can be implemented if you have particular requirements.

Anchor
_Toc378061308 _Toc378061308

Anchor
_Toc471889143 _Toc471889143

IP Address Range

All traffic originates from within the following IP address range: 185.107.196.0/22 (185.107.196.1 - 185.107.199.254)

Anchor
_Toc471889144 _Toc471889144

Anchor
_Toc378061309 _Toc378061309

Integration Service Schema

XSD files are provided to support the integration of the V3 schema. You can download these files from here: DropBox
The "Integration Schema V3" folder contains various files, including:

• schemas.sportsdataservices.com.integrationService.v3.xsd – the current schema
• schemas.microsoft.com.2003.10.Serialization.xsd – Microsoft types used in the schema (specifically a restriction on xs:duration)
• Match State contracts for each sport

Your endpoint should support the following methods, which will be called by our service. The updategram object is described in the IntegrationService xsd.

• Heartbeat()
• ProcessMessage(Updategram updategram)

 All messages are assumed to have been successfully received if an HTTP 200 (Ok) status message is returned. It is assumed that this acknowledgement indicates that the Trading Platform has received and acted upon the updated information.
If an HTTP 200 status message is not received for any reason (timeout, connection problem, service unavailable etc.) it will be assumed that the message has not been delivered and that the contents have therefore not been acted upon.