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 /TimeZones/Convert HTTP/1.1
Host: stubbur-autoupdates-live.smartnewapis.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<TimeZonesConvertRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<FromDate>0001-01-01T00:00:00</FromDate>
<TimeZoneFromName>String</TimeZoneFromName>
<TimeZoneToName>String</TimeZoneToName>
</TimeZonesConvertRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<TimeZoneConvertResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<FromDate>0001-01-01T00:00:00</FromDate>
<FromTimeZoneInfo xmlns:d2p1="http://schemas.datacontract.org/2004/07/System" i:nil="true" />
<Message>String</Message>
<StatusCode>0</StatusCode>
<ToDate>0001-01-01T00:00:00</ToDate>
<ToTimeZoneInfo xmlns:d2p1="http://schemas.datacontract.org/2004/07/System" i:nil="true" />
<UTCDate>0001-01-01T00:00:00</UTCDate>
</TimeZoneConvertResponse>