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 /scheduling/{UserId}/cancel-wait-list HTTP/1.1
Host: clubready.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<CancelWaitListRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/ClubReady.Web.Api.Scheduling.Model">
<ApiKey>String</ApiKey>
<ChainId>0</ChainId>
<ClassScheduleId>0</ClassScheduleId>
<StoreId>0</StoreId>
<UserId>0</UserId>
</CancelWaitListRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<CancelWaitListResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/ClubReady.Web.Api.Scheduling.Model">
<Message>String</Message>
<Success>false</Success>
</CancelWaitListResponse>