Reservation Station API

BookingHistory

The following routes are available for this service:
GET	/booking/history

**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

**BookingHistoryResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Bookings	form	List<UserHistoryDayData>	No

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

**UserHistoryDayData** Parameters:
Name	Parameter	Data Type	Required	Description
Date	form	string	No
Bookings	form	List<BookingHistoryData>	No

**BookingHistoryData** Parameters:
Name	Parameter	Data Type	Required
VenueName	form	string	No
FacilityName	form	string	No
Start	form	string	No
End	form	string	No
BilledAmount	form	decimal	No
Finished	form	bool	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.

GET /booking/history HTTP/1.1 
Host: reservation.api.dev.86degrees.com 
Accept: application/json

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

{"bookings":[{}],"description":"String","heading":"String","wasSuccessful":false,"modelState":{}}