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 /DiscountCodeTypeValidTicketType/Search HTTP/1.1
Host: stubbur-app.azurewebsites.net
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<DiscountCodeTypeValidTicketTypesSearchRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<DiscountCodeTypeId>0</DiscountCodeTypeId>
<EventSeriesOwnerTicketType>0</EventSeriesOwnerTicketType>
</DiscountCodeTypeValidTicketTypesSearchRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<DiscountCodeTypeValidTicketTypesResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<Items>
<DiscountCodeTypeValidTicketType>
<DiscountCodeTypeId>0</DiscountCodeTypeId>
<EventSeriesOwnerTicketType>0</EventSeriesOwnerTicketType>
<ID>0</ID>
<IsValid>false</IsValid>
</DiscountCodeTypeValidTicketType>
</Items>
<Message>String</Message>
<StatusCode>0</StatusCode>
</DiscountCodeTypeValidTicketTypesResult>