POST | /scheduling/{UserId}/cancel-wait-list | Cancel a wait list record. |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ApiKey | query | string | Yes | Api Key - Grants access to resources |
StoreId | query | integer | No | Store ID or Chain ID is required |
ChainId | query | integer | No | Store ID or Chain ID is required |
UserId | path | integer | Yes | ClubReady User ID |
ClassScheduleId | query | integer | Yes | Class Schedule ID |
RestrictedId | body | int? | No | |
RestrictedResourceType | body | RestrictedResourceType | No |
Store | |
Chain | |
User | |
Undefined |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Success | form | bool | No | |
Message | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
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/json
Content-Type: application/json
Content-Length: length
{"ApiKey":"String","StoreId":0,"ChainId":0,"UserId":0,"ClassScheduleId":0,"RestrictedId":0,"RestrictedResourceType":"Chain"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"Success":false,"Message":"String"}