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 /SuggestedBets HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<SuggestedBetsRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions" />
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<SuggestedBetsResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<Items xmlns:d2p1="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">
<d2p1:SuggestedBet>
<d2p1:AdvertisedStartTime>0001-01-01T00:00:00</d2p1:AdvertisedStartTime>
<d2p1:Barrier>String</d2p1:Barrier>
<d2p1:ClientID>0</d2p1:ClientID>
<d2p1:EventID>0</d2p1:EventID>
<d2p1:IsJockeySilkExist>false</d2p1:IsJockeySilkExist>
<d2p1:JockeyName>String</d2p1:JockeyName>
<d2p1:LongTipReason>String</d2p1:LongTipReason>
<d2p1:OutcomeID>0</d2p1:OutcomeID>
<d2p1:RaceNumber>0</d2p1:RaceNumber>
<d2p1:RaceVenue>String</d2p1:RaceVenue>
<d2p1:RunnerName>String</d2p1:RunnerName>
<d2p1:RunnerRaceCardNumber>String</d2p1:RunnerRaceCardNumber>
<d2p1:SecondsToJump>0</d2p1:SecondsToJump>
<d2p1:ShortForm>String</d2p1:ShortForm>
<d2p1:ShortTipReason>String</d2p1:ShortTipReason>
<d2p1:Trainer>String</d2p1:Trainer>
<d2p1:WeightCarried>String</d2p1:WeightCarried>
</d2p1:SuggestedBet>
</Items>
</SuggestedBetsResponse>