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 /LBetStopExclusionReasons HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<LBetStopExclusionReasonsRequest 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
<LBetStopExclusionReasonsResponse 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:LBetStopExclusionReason>
<d2p1:BetStopExclusionReason>String</d2p1:BetStopExclusionReason>
<d2p1:BetStopExclusionReasonID>0</d2p1:BetStopExclusionReasonID>
</d2p1:LBetStopExclusionReason>
</Items>
</LBetStopExclusionReasonsResponse>