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.
PATCH /User/Account/Settings/EmailNotification HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<PatchEmailNotificationSettings xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<DateFinder>false</DateFinder>
<Events>false</Events>
<MatchReport>false</MatchReport>
<Offers>false</Offers>
<RHPTeamMessages>false</RHPTeamMessages>
</PatchEmailNotificationSettings>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<EmailNotificationSettings xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP.ServiceHelper.Model">
<DateFinder>false</DateFinder>
<Events>false</Events>
<MatchReport>false</MatchReport>
<Offers>false</Offers>
<RHPTeamMessages>false</RHPTeamMessages>
</EmailNotificationSettings>