Assign a specific unit to a reservation.
Changed onAssigns a specific unit to a reservation which is in state 'Confirmed' or 'InHouse'. If the unit is not available, the call will return an error, and no unit will be assigned.<br>You must have at least one of these scopes: 'reservations.assign-unit, reservations.manage'.<br>For fine-grained clients, you must have this permission: 'core.reservations.modify'.
Request
- Base URLhttps://api.apaleo.com (the document declares no server; this is the origin it was published from)
- URLhttps://api.apaleo.com/booking/v1/reservation-actions/{id}/assign-unit/{unitId}
- AuthOAuth 2Implicit: https://identity.apaleo.com/connect/authorizeScopes: reservations.assign-unit, reservations.manage, admin
Path parameters
Id of the reservation the unit should be assigned to.
The id of the unit to be assigned.
Query parameters
The start date and optional time for the unit assignment. If not specified, the reservation's arrival will be used.<br />Specify either a pure date or a date and time (without fractional second part) in UTC or with UTC offset as defined in <a href="https://en.wikipedia.org/wiki/ISO_8601">ISO8601:2004</a>
The end date and optional time for the unit assignment. If not specified, the reservation's departure will be used.<br />Specify either a pure date or a date and time (without fractional second part) in UTC or with UTC offset as defined in <a href="https://en.wikipedia.org/wiki/ISO_8601">ISO8601:2004</a>
Whether to lock the unit for the duration of the reservation. If not specified, the unit will not be locked.
Response
Unit assignment was successful.
Example response
{
"unit": {
"id": "MUC-JQI",
"name": "A.102",
"description": "Double room",
"unitGroupId": "MUC-DBL"
}
}Changes
- info
added the new optional
queryrequest parameterlockUnit - info
added the non-success response with the status
- info