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 /CreditCardDeposit HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<CreditCardDepositRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<Amount>0</Amount>
<CVN>String</CVN>
<CreditCardId>0</CreditCardId>
</CreditCardDepositRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<PaymentResponse 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>
<AddInfo xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</AddInfo>
<GatewayReference>String</GatewayReference>
<IsFirstDeposit>false</IsFirstDeposit>
<TBSReference>String</TBSReference>
</PaymentResponse>