GET | /User/Club/InviteList |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
UserID | query | long | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /User/Club/InviteList HTTP/1.1 Host: tstsrvs.redhotpie.com.au Accept: application/xml
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <ArrayOfClubSummary xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel"> <ClubSummary> <ClubBannerPhoto xmlns:d3p1="http://schemas.datacontract.org/2004/07/RHP.ServiceHelper.Model"> <d3p1:ApprovalState>Pending</d3p1:ApprovalState> <d3p1:FullUrl>String</d3p1:FullUrl> <d3p1:Height>0</d3p1:Height> <d3p1:Width>0</d3p1:Width> </ClubBannerPhoto> <ClubID>0</ClubID> <IsOwner>false</IsOwner> <MemberCount>0</MemberCount> <Name>String</Name> <PrivacyType>Public</PrivacyType> </ClubSummary> </ArrayOfClubSummary>