Update reservation
This workflow allows third parties to update an existing reservation for a specific room with specified times.
The following parameters are used in the request. These are all required.
Parameter
Description
UltimoId
The internal Ultimo Id of a reservation for the room (ReservationLine Id).
StartTime
The start time (datetime) of reservation.
Allowed formats:
yyyy-MM-dd hh:mm:ss (i.e. 2018-08-21 15:21:59)
UTC: yyyy-MM-ddThh:mm:ssZ (i.e. 2018-08- 20T15:17:59Z)
EndTime
The end time (datetime) of reservation.
Allowed formats:
yyyy-MM-dd hh:mm:ss (i.e. 2018-08-21 15:21:59)
UTC: yyyy-MM-ddThh:mm:ssZ (i.e. 2018-08- 20T15:17:59Z)
Technical details
Basic URL (POST):
https://customer.ultimo.com/api/V1/Action/REST_UpdateReservation
Header data:
Parameter
Description
ApiKey
Request an API key at (application manager or consultant
ApplicationElementId
Fixed value “3736d834-fa5e-4edc-9abd-f38962ff8afd”
Body (example):
{
"UltimoId": "00000006712",
"StartTime": "2021-06-14 12:00:00",
"EndTime": "2021-06-14 13:00:00"
}
Normal response:
Status: 200 OK
{
"properties": {}
}
Responses when the action is not allowed:
Status: 400 Bad Request
{
"message": "Room reservation cannot be requested or processed.\r\nCause: Meeting room 2 is not available.",
"type": "3",
"code": "1015"
}
In this case it is not allowed to make a reservation for a room that already has a reservation at the specified time. Ultimo will not process this action.
Status: 400 Bad Request
{
"message": "Room reservation cannot be modified.\r\nCause: Room reservation is in the past.",
"type": "3",
"code": "1166"
}
In this case it is not allowed to modify a room reservation that lies in the past. Ultimo will not process this action.
Response when the API-key is invalid:
Status: 401 Unauthorized
{
"message": "Missing API key",
"code": "MissingApiKey"
}
Last updated