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 /UserMigratedInfo HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<UserMigratedInfoRequest 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
<UserMigratedInfoResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<ErrorNo xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">0</ErrorNo>
<Identity xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">0</Identity>
<Message xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">String</Message>
<Balance>0</Balance>
<ClientType>DUAL</ClientType>
<FreeBetBalance>0</FreeBetBalance>
<FreeBetCount>0</FreeBetCount>
<MigratedBalance>0</MigratedBalance>
<MigratedBonusBalance>0</MigratedBonusBalance>
<WelcomeBonus>0</WelcomeBonus>
</UserMigratedInfoResponse>