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 /FanSync/Clubs HTTP/1.1
Host: stubbur-app.azurewebsites.net
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<FanSyncClubsRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<Teams>
<FanSyncTeam>
<ClubName>String</ClubName>
<ClubTeamNumber>String</ClubTeamNumber>
<Name>String</Name>
<TeamNumber>String</TeamNumber>
</FanSyncTeam>
</Teams>
</FanSyncClubsRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<FanSyncClubsResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<Mapped>0</Mapped>
<Message>String</Message>
<StatusCode>0</StatusCode>
<Unmapped>0</Unmapped>
</FanSyncClubsResult>