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.
GET /User/Purchase/Credits HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<UserCreditRecord xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<CurrentConversationCredits>0</CurrentConversationCredits>
<CurrentStoreCredits>0</CurrentStoreCredits>
<Diamonds>0</Diamonds>
<DiamondsBalance>0</DiamondsBalance>
<Purchases>
<UserCreditPurchase>
<Amount>0</Amount>
<CreditAmount>0</CreditAmount>
<Currency xmlns:d4p1="http://schemas.datacontract.org/2004/07/RHP.Model">
<d4p1:Code>String</d4p1:Code>
<d4p1:CurrencyID>0</d4p1:CurrencyID>
<d4p1:DateCreated>0001-01-01T00:00:00</d4p1:DateCreated>
<d4p1:Name>String</d4p1:Name>
<d4p1:Symbol>String</d4p1:Symbol>
</Currency>
<ExpiryDate>0001-01-01T00:00:00</ExpiryDate>
<PaymentProvider>Verotel</PaymentProvider>
<PaymentProviderTitle>String</PaymentProviderTitle>
<ProductGroup>ConversationCredits</ProductGroup>
<ProductName>String</ProductName>
<PurchaseDate>0001-01-01T00:00:00</PurchaseDate>
</UserCreditPurchase>
</Purchases>
</UserCreditRecord>