ClubReady Api

BookingStatusUpdateRequest

The following routes are available for this service:
POST	/scheduling/booking-status-update	Update a Booking Status

**BookingStatusUpdateRequest** Parameters:
Name	Parameter	Data Type	Required	Description
XForwardedFor	header	string	No	IP address of the end user
ApiKey	query	string	Yes	Api Key - grants access to resources
StoreId	query	string	Yes	StoreId
UserId	query	string	Yes	UserID
StatusId	query	integer	Yes	Status ID
BookingId	query	integer	Yes	Booking ID
RestrictedId	body	int?	No
RestrictedResourceType	body	RestrictedResourceType	No

**BookingStatusUpdateRequestDto** Parameters:
Name	Parameter	Data Type	Required
UserId	form	int?	No
StatusId	form	int	No
BookingId	form	int	No

**ApiDtoBase** Parameters:
Name	Parameter	Data Type	Required
ApiKey	form	string	No
StoreId	form	int?	No
ChainId	form	int?	No

**RestrictedResourceType** Enum:
Store
Chain
User
Undefined

**BookingStatusUpdateResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Success	form	bool	No
Message	form	string	No

**BookingStatusUpdateResponseDto** Parameters:
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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /scheduling/booking-status-update HTTP/1.1 
Host: clubready.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"XForwardedFor":"String","ApiKey":"String","StoreId":0,"UserId":0,"StatusId":0,"BookingId":0,"RestrictedId":0,"RestrictedResourceType":"Store","ChainId":0}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Success":false,"Message":"String"}