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.
PUT /profile/update-home HTTP/1.1
Host: consumer-api.brovs.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<ProfileUpdateHomeLocationRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/ConsumerApi.Dto">
<Home xmlns:d2p1="http://schemas.datacontract.org/2004/07/Entities.Common">
<d2p1:Address>
<d2p1:CountryCode>String</d2p1:CountryCode>
<d2p1:PostalCode>String</d2p1:PostalCode>
<d2p1:Region>String</d2p1:Region>
<d2p1:StreetName>String</d2p1:StreetName>
<d2p1:StreetNumber>String</d2p1:StreetNumber>
</d2p1:Address>
<d2p1:Latitude>0</d2p1:Latitude>
<d2p1:Longitude>0</d2p1:Longitude>
</Home>
</ProfileUpdateHomeLocationRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<ProfileUpdateHomeLocationResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/ConsumerApi.Dto">
<HomeLocation xmlns:d2p1="http://schemas.datacontract.org/2004/07/Entities.Common">
<d2p1:Address>
<d2p1:CountryCode>String</d2p1:CountryCode>
<d2p1:PostalCode>String</d2p1:PostalCode>
<d2p1:Region>String</d2p1:Region>
<d2p1:StreetName>String</d2p1:StreetName>
<d2p1:StreetNumber>String</d2p1:StreetNumber>
</d2p1:Address>
<d2p1:Latitude>0</d2p1:Latitude>
<d2p1:Longitude>0</d2p1:Longitude>
</HomeLocation>
</ProfileUpdateHomeLocationResponse>