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/Follows HTTP/1.1
Host: stubbur-app.azurewebsites.net
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<FanSyncFollowsRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<Chunk>0</Chunk>
<Final>false</Final>
<Rows>
<FanSyncFollowRow>
<FollowedAt>String</FollowedAt>
<Phone>String</Phone>
<TeamNumber>String</TeamNumber>
</FanSyncFollowRow>
</Rows>
<RunId>String</RunId>
</FanSyncFollowsRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<FanSyncFollowsResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<Deduped>0</Deduped>
<DroppedNoOwner>0</DroppedNoOwner>
<DroppedNotFanPhone>0</DroppedNotFanPhone>
<Kept>0</Kept>
<LiveRows>0</LiveRows>
<Message>String</Message>
<Received>0</Received>
<RunId>String</RunId>
<StatusCode>0</StatusCode>
<Swapped>false</Swapped>
</FanSyncFollowsResult>