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.
GET /User/Club/{ClubID}/Event/ HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<ArrayOfUserEventListItem xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<UserEventListItem>
<ApprovalStatus>Approved</ApprovalStatus>
<DateHeld>0001-01-01T00:00:00</DateHeld>
<DateHeldDisplay>String</DateHeldDisplay>
<DateHeldUtcIso>String</DateHeldUtcIso>
<EventBannerUrl>String</EventBannerUrl>
<EventID>0</EventID>
<EventTitle>String</EventTitle>
<EventType>MemberEvent</EventType>
<InterestCount>0</InterestCount>
<Location>
<City>String</City>
<Country>String</Country>
<State>String</State>
<StateAbbr>String</StateAbbr>
</Location>
<TimeZone xmlns:d3p1="http://schemas.datacontract.org/2004/07/RHP.Model">
<d3p1:AbbrDaylight>String</d3p1:AbbrDaylight>
<d3p1:AbbrGeneric>String</d3p1:AbbrGeneric>
<d3p1:AbbrStandard>String</d3p1:AbbrStandard>
<d3p1:BaseUtcOffset>String</d3p1:BaseUtcOffset>
<d3p1:DaylightName>String</d3p1:DaylightName>
<d3p1:DaylightOffset>String</d3p1:DaylightOffset>
<d3p1:ID>String</d3p1:ID>
<d3p1:IanaName>String</d3p1:IanaName>
<d3p1:IsDaylightSavingTime>false</d3p1:IsDaylightSavingTime>
<d3p1:StandardName>String</d3p1:StandardName>
<d3p1:SupportsDaylightSavingTime>false</d3p1:SupportsDaylightSavingTime>
<d3p1:WindowsName>String</d3p1:WindowsName>
</TimeZone>
<TimeZoneInfoID>String</TimeZoneInfoID>
</UserEventListItem>
</ArrayOfUserEventListItem>