Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • prereservationExpirationDate,

  • nextReservationTimes.

Note

Please note, that you must always supply all the nextReservationTimes (that you supplied in POST request) for every single parcel’s update, otherwise you will loose your next reservation times!

Updating PrereservationExpirationDate

...

You can update the nextReservationTimes now as well. It is not allowed to supply any new next reservation time times 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.
Please note, that you must always supply all the nextReservationTimes (that you supplied in POST request)!

If you try to add new next reservation time (that is supply an element in the nextreservationtimes nextReservationTimesarray, which doesn’t match any element used in POST request for the reservation), you will receive bad reqest reposnse with an error message informing you about this case.

...

Code Block
languagejson
{
  "data": {
    "reservation": {
      "id": "id_prereservation_efae3b16-5d13-4978-bb2b-a790f9a541e1",
      "attributes": {
        "nextreservationtimesnextReservationTimes":[
            {
                "expirationDate": "2024-08-25T16:00:00.000Z",
                "startReservationDate": "2024-08-25T14:00:00.000Z",
                "prereservationExpirationDate":"2024-08-25T13:35:00.000Z"
            }
        ]
      }
    }
  }
}

...