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 /RaceReplayFromForm HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<RaceReplayFromFormRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<Items>
<RaceReplayFormItem>
<Date>String</Date>
<RaceNumber>0</RaceNumber>
<RaceTypeCode>String</RaceTypeCode>
<TrackName>String</TrackName>
</RaceReplayFormItem>
</Items>
</RaceReplayFromFormRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<RaceReplayFromFormResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<Items>
<RaceReplayFromFormResponseItem>
<Date>String</Date>
<RaceNumber>0</RaceNumber>
<Streaming xmlns:d4p1="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">
<d4p1:LiveStream>
<d4p1:Channel>String</d4p1:Channel>
<d4p1:Provider>String</d4p1:Provider>
</d4p1:LiveStream>
<d4p1:Replay>
<d4p1:Channel>String</d4p1:Channel>
<d4p1:Provider>String</d4p1:Provider>
</d4p1:Replay>
<d4p1:StreamingUrl>String</d4p1:StreamingUrl>
<d4p1:ThumbnailUrl>String</d4p1:ThumbnailUrl>
</Streaming>
<TrackName>String</TrackName>
</RaceReplayFromFormResponseItem>
</Items>
</RaceReplayFromFormResponse>