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/Travel/{UserTravelProfileID} HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<UpdateUserTravelProfile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<DateArrived>0001-01-01T00:00:00</DateArrived>
<DateDeparture>0001-01-01T00:00:00</DateDeparture>
<Description>String</Description>
<IsHidden>false</IsHidden>
<LocationGID>String</LocationGID>
<ShowSimpleDates>false</ShowSimpleDates>
<UserTravelProfileID>0</UserTravelProfileID>
</UpdateUserTravelProfile>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<UserTravelProfile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<DateArrived>0001-01-01T00:00:00</DateArrived>
<DateDeparture>0001-01-01T00:00:00</DateDeparture>
<Description>String</Description>
<IsHidden>false</IsHidden>
<LocationGID>String</LocationGID>
<ShowSimpleDates>false</ShowSimpleDates>
<UserTravelProfileID>0</UserTravelProfileID>
<LocationLabel>String</LocationLabel>
<LocationText>String</LocationText>
<TextApprovalStatus>Approved</TextApprovalStatus>
</UserTravelProfile>