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 /recurringPayments/card HTTP/1.1
Host: stubbur-app.azurewebsites.net
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<UpdateRecurringPaymentCardRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<ExpMonth>String</ExpMonth>
<ExpYear>String</ExpYear>
<Id>0</Id>
<PanLastFour>String</PanLastFour>
<PaymentTokenId>String</PaymentTokenId>
<Phone>String</Phone>
<Token>String</Token>
<Via>String</Via>
</UpdateRecurringPaymentCardRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<UpdateRecurringPaymentCardResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<Effect>String</Effect>
<Id>0</Id>
<Message>String</Message>
<NextPayment>0001-01-01T00:00:00</NextPayment>
<Ok>false</Ok>
<PriorStatus>String</PriorStatus>
<Resumed>false</Resumed>
<Status>String</Status>
<StatusCode>0</StatusCode>
</UpdateRecurringPaymentCardResult>