TBS Apps API

LiveScoreRequest

The following routes are available for this service:
GET,POST	/LiveScore	Gets Live Scores. Sports master categories can be thought of as 'Leagues'	Gets Live Score Data. Sports master categories can be thought of as 'Leagues'. Ex: Soccer - EPL

**LiveScoreRequest** Parameters:
Name	Parameter	Data Type	Required	Description
MasterEventID	body	int	Yes	Master Event ID ex: 12345

**LiveScoreResponse** Parameters:
Name	Parameter	Data Type	Required
MasterEventID	form	int	No
HomeScore	form	string	No
AwayScore	form	string	No
Status	form	string	No
MatchSummaryMessage	form	string	No
MatchSummaryTimestamp	form	DateTime	No
MatchDetailTimestamp	form	DateTime	No
MatchDetailMessage	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /LiveScore HTTP/1.1 
Host: tstextweb20.np.bluebet.com.au 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<LiveScoreRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
  <MasterEventID>0</MasterEventID>
</LiveScoreRequest>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<LiveScoreResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
  <AwayScore>String</AwayScore>
  <HomeScore>String</HomeScore>
  <MasterEventID>0</MasterEventID>
  <MatchDetailMessage>String</MatchDetailMessage>
  <MatchDetailTimestamp>0001-01-01T00:00:00Z</MatchDetailTimestamp>
  <MatchSummaryMessage>String</MatchSummaryMessage>
  <MatchSummaryTimestamp>0001-01-01T00:00:00Z</MatchSummaryTimestamp>
  <Status>String</Status>
</LiveScoreResponse>