Reservation Station API

JoinVenue

The following routes are available for this service:
POST	/venue/join

**JoinVenue** Parameters:
Name	Parameter	Data Type	Required	Description
VenueCode	body	string	No
UserCustomFields	body	List<UserCustomFieldData>	No

**ApiServiceRequest** Parameters:
Name	Parameter	Data Type	Required	Description
ApiKey	form	string	Yes	The API Key required for authentication
Latitude	form	double	No	Latitude of the user making this request
Longitude	form	double	No	Longitude of the user making this request

**UserCustomFieldData** Parameters:
Name	Parameter	Data Type	Required
Id	form	Guid	No
Value	form	string	No
Name	form	string	No
Optional	form	bool	No

**JoinVenueResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Venues	form	List<VenueData>	No
VenueCustomFields	form	List<VenueCustomField>	No

**ApiServiceResponse** Parameters:
Name	Parameter	Data Type	Required
Description	form	string	No
Heading	form	string	No
WasSuccessful	form	bool	No
ModelState	form	Object	No

**VenueData** Parameters:
Name	Parameter	Data Type	Required
VenueId	form	int	No
Name	form	string	No
RegisteredDate	form	string	No
VenueCode	form	string	No
IsCoordinator	form	bool	No
Facilities	form	List<FacilityData>	No
Latitude	form	double	No
Longitude	form	double	No
HasLocation	form	bool	No
LogoUrl	form	string	No
LeadTime	form	int	No
VenueInfo	form	string	No
AllowGuests	form	bool	No
ContactNumber	form	string	No

**FacilityData** Parameters:
Name	Parameter	Data Type	Required
FacilityId	form	int	No
FacilityGuid	form	string	No
Name	form	string	No
Description	form	string	No
NextAvailable	form	string	No
HasNextAvailable	form	bool	No
Rates	form	List<RatesItem>	No
ThemeColor	form	string	No
BookingNotes	form	string	No
LeadTime	form	int	No
VenueId	form	int	No
AllowExtraRequirements	form	bool	No

**RatesItem** Parameters:
Name	Parameter	Data Type	Required	Description
Rate	form	decimal	No
Minutes	form	int	No

**VenueCustomField** Parameters:
Name	Parameter	Data Type	Required
VenueName	form	string	No
VenueId	form	int	No
Fields	form	List<UserCustomFieldData>	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .other suffix or ?format=other

HTTP + OTHER

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

POST /venue/join HTTP/1.1 
Host: reservation.api.dev.86degrees.com 
Accept: text/jsonl
Content-Type: text/jsonl
Content-Length: length

{"venueCode":"String","userCustomFields":[{"id":"00000000-0000-0000-0000-000000000000","value":"String","name":"String","optional":false}],"apiKey":"String","latitude":0,"longitude":0}

HTTP/1.1 200 OK
Content-Type: text/jsonl
Content-Length: length

{"venues":[{}],"venueCustomFields":[{"venueName":"String","venueId":0,"fields":[{"id":"00000000-0000-0000-0000-000000000000","value":"String","name":"String","optional":false}]}],"description":"String","heading":"String","wasSuccessful":false,"modelState":{}}