ClubReady Api

CreateClassBookingRequest

The following routes are available for this service:
POST	/scheduling/class-booking	Create a Class Booking
POST	/v2/{ApiKey}/club/{StoreId}/booking	(obsolete) Create a Class Booking
POST	/v2/{ApiKey}/club/{StoreId}/class-booking	(obsolete) Create a Class Booking

**CreateClassBookingRequest** Parameters:
Name	Parameter	Data Type	Required	Description
ApiKey	query	string	Yes	Api Key - grants access to resources
UserId	query	string	Yes	UserID
StoreId	query	integer	Yes	Store ID
ScheduleId	query	integer	Yes	Class Schedule ID
AllowWaitList	query	bool	No	Put user in wait list when possible
RestrictedId	body	int?	No
RestrictedResourceType	body	RestrictedResourceType	No

**CreateClassBookingRequestDto** Parameters:
Name	Parameter	Data Type	Required
UserId	form	int	No
ScheduleId	form	int	No
AllowWaitList	form	bool	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

**CreateClassBookingResponse** Parameters:
Name	Parameter	Data Type	Required	Description
BookingId	form	int?	No
Message	form	string	No

**CreateClassBookingResponseDto** Parameters:
Name	Parameter	Data Type	Required	Description
BookingId	form	int?	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/class-booking HTTP/1.1 
Host: www.clubready.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"ApiKey":"String","UserId":0,"StoreId":0,"ScheduleId":0,"AllowWaitList":false,"RestrictedId":0,"RestrictedResourceType":"Store","ChainId":0}

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

{"BookingId":0,"Message":"String"}