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 /ticketTransfer/incoming HTTP/1.1
Host: stubbur-app.azurewebsites.net
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<TicketTransferIncomingRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<PhoneVerificationNumber>String</PhoneVerificationNumber>
</TicketTransferIncomingRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<TicketTransferIncomingResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<ErrorCode>String</ErrorCode>
<Message>String</Message>
<StatusCode>0</StatusCode>
<Transfers>
<TicketTransferIncomingItem>
<CreatedAt>0001-01-01T00:00:00</CreatedAt>
<EventId>0</EventId>
<EventName>String</EventName>
<ExpiresAt>0001-01-01T00:00:00</ExpiresAt>
<FromPhoneDisplay>String</FromPhoneDisplay>
<Tickets>
<TicketTransferTicketSummary>
<Count>0</Count>
<TicketDisplayString>String</TicketDisplayString>
<TicketName>String</TicketName>
</TicketTransferTicketSummary>
</Tickets>
<TimeOfEvent>0001-01-01T00:00:00</TimeOfEvent>
<TransferToken>String</TransferToken>
</TicketTransferIncomingItem>
</Transfers>
</TicketTransferIncomingResult>