Create/update reservation

Creating new reservations, updating reservations, canceling reservations.

Behavior of this endpoint heavily depends on the agreed scheme of communication:

1 - Reservation Statuses:

The default scheme is "dual requests" - the first request contains status: option and does not contain customer data. The second request contains status: confirmed and includes customer data. This scheme allows more gradual control of the state of the reservation. Both statuses are expected to block the room for the reservation.

The second option is "single request" - in this scheme, even the first request with status: option contains all customer data and the voucher code. The confirmation request is sent also with the same data but does not have to be relayed to the hotel. Single-request mode is more suited for systems which do not support modifying existing reservations without canceling them and creating a new one (OTA-like behavior). You should specify which behavior better suits your system capabilities when consulting the integration with Termino.

2 - Reservation ID:

For referencing reservations between Termino and your system, either your ID or our ID can be used. In case your ID is used, the first (option) request does not contain the property id. You have to generate and send it in response.

In case our ID is used, the first (option) request contains the property id with our ID. You have to store it and use it in all subsequent requests.

Using your ID can be problematic in case communication during the first request fails due to any unexpected error (timeout, outage, etc.). This may cause a reservation being created in your system, but not in Termino. That's why we prefer using our ID, which we can use to check and remove such un-synced reservation.

Termino expects the room to be blocked for reservation when the option request is successfully processed.

Usage:

• Called with status option and then confirmed when creating a new reservation (see above)
• Called with canceled status to cancel the reservation
• Called when changing booking date on customer's request

Grouped reservations are currently not implemented; one request always contains only one reservation. Reservation group ID is the same as reservation ID. Reservation response should contain the same data as the request.