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 /Product/Validate/Google HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<ValidateGooglePaymentReceipt xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<Receipts>
<GoogleReceipt>
<autoRenewingAndroid>false</autoRenewingAndroid>
<dataAndroid>String</dataAndroid>
<isAcknowledgedAndroid>false</isAcknowledgedAndroid>
<productId>String</productId>
<purchaseStateAndroid>String</purchaseStateAndroid>
<purchaseToken>String</purchaseToken>
<signatureAndroid>String</signatureAndroid>
<transactionDate>String</transactionDate>
<transactionId>String</transactionId>
<transactionReceipt>String</transactionReceipt>
</GoogleReceipt>
</Receipts>
</ValidateGooglePaymentReceipt>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<ArrayOfGoogleValidateReceiptResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<GoogleValidateReceiptResponse>
<ReceiptValidationResult>Success</ReceiptValidationResult>
<TransactionID>String</TransactionID>
</GoogleValidateReceiptResponse>
</ArrayOfGoogleValidateReceiptResponse>