March 2019

Updates to Housekeeping related API calls

We added new housekeeping endpoints that allow you to manage Housekeepers. As a part of this project, some of our other housekeeping calls were improved.  Now, new scope housekeeping is a requirement for Housekeeping-related calls.

Endpoint(s)	Description
getHousekeepers (new)	Provides the list of housekeepers available in myfrontdesk with name and ID.
putHousekeeper (new)	Allows the housekeeper's name to be edited.
postHousekeeper (new)	A housekeeper can be added to myfrontdesk.
postHousekeepingAssignment (new)	Assign rooms (single or multiple) to an existing housekeeper
postHousekeepingStatus	Added parameter “status”which allows you to set a specific status instead of switching the status dirty/clean.
getHousekeepingStatus	Added possibility to filter by housekeeperID
getHousekeepingStatus & getRooms	Information about blocked rooms (by out of service block or courtesy holds) was added to the response to these calls.

Changes and new endpoints

Endpoint(s)	Description
userinfo(new)	To OAuth flow, we added this new endpoint which allows you to identify and see email information from the user that has authorized/approved the application connection.
putResesrvationDetails & getPaymentRecent	These calls were soft deprecated and we won't develop and fix them going forward.
getRoomsUnassigned & getRooms	We clarified the description for parameters startDate/endDate. These are not check-in check-out dates and can be used as “stay dates”.
getReservationRoomDetails	Added all guests to the response.
getReservationInvoiceInformation, getPayments & getTransactions	Added UTC time