Prereservations can be updated as any other reservations.
Additionally to all the classic reservation’s attributes you can update the two new attributes as well:
prereservationExpirationDate,
nextReservationTimes.
Please note that this parameter is accepted only for parcels created as prereservations (that is with the parameter supplied in the POST request).
Update example:
{ "data": { "reservation": { "id": "id_prereservation_efae3b16-5d13-4978-bb2b-a790f9a541e1", "attributes":{ "prereservationExpirationDate":"2024-08-25T13:35:00.000Z" } } } } |
You can update the nextReservationTimes now as well. It is not allowed to supply any new next reservation time to your exiting prereservation via the PATCH request. However you can update any active existing next reservation time by matching it via the StartReservationDate attribute. Both ExpirationDate and PrereservationExpirationDate are updateable.
Update example:
{ "data": { "reservation": { "id": "id_prereservation_efae3b16-5d13-4978-bb2b-a790f9a541e1", "attributes": { "nextreservationtimes":[ { "expirationDate": "2024-08-25T16:00:00.000Z", "startReservationDate": "2024-08-25T14:00:00.000Z", "prereservationExpirationDate":"2024-08-25T13:35:00.000Z" } ] } } } } |