API - postReservation, putReservation, postCancelReservation Added

A new Distribution Reservation API is released in addition to Book and Reservation Notification.

Designed for booking engine direct channels powered by the property supplier that require both the simplicity of distribution mapping and the depth of PMS functionality.

It merges the strengths of the distribution layer, such as channel mapping, degraded mode, with the advanced reservation capabilities of the PMS, including internal operational features typically available to property users.

This flexibility makes it ideal for property developers building fully flexible guest-facing applications that demand comprehensive booking features, beyond what standard distribution APIs allow.

• Fully unified CRS and PMS-level booking capabilities paired with flexible distribution for advanced property applications.
• Easy migration for hoteliers and partners using OPERA Cloud Property Reservation API (RSV) today.

This new Distribution Reservation API also supports:

• the inclusion of Rate summary in the reservation response that provides the daily details as well as the total amount before and after tax, total fixed charges, deposit payment, total cost of stay, and and outstanding cost of stay.

• the inclusion of deposit payments (deposit notifications) during the reservation creation process, in the same API call. The deposit Folio required in certain countries is not supported as part of the reservation creation. However, deposit folios can be sent via a separate call using property APIs.

  When a deposit policy is associated with the reservation, the deposit payment is automatically linked to the corresponding policy. If multiple deposit policies are present, the first matching policy with the earliest due date is used. When no deposit policy is associated, the payment is posted as an unallocated deposit payment.

• the inclusion of add-on package elements during the reservation creation process, in the same API call.
• the inclusion of fixed charges during the reservation creation process, in the same API call.

IMPACT OR OTHER CONSIDERATIONS

This Distribution Reservation API is created in addition to the Distribution Book and Distribution Reservation Notification existing APIs.

• Book is designed for external channels, such as GDS or traditional “pull”demand channels, that book directly in OPERA Cloud (OC) using global industry-standard codes and distribution business logic.

In this model, OC is the source of truth where rates and policies are generated and cannot be altered by the channel. Inventory and restriction checks are strictly enforced, ensuring full compliance with property-defined availability rules.

This API is best suited for channels that requirecontrolled access to predefined rates and inventory, with functionality limited to traditional indirect distribution use cases such as room and rate selection, but without the flexibility to override CRS-driven business rules.

• Reservation Notification is Intended for OTA “push” channels or channel managers that deliver bookings already confirmed to the guest in upstream system.

These reservations are transmitted directly into OC using global industry-standard codes. Unlike Distribution Book, the rates provided by the channel are accepted as-is, and CRS validation for inventory and restrictions is bypassed, since the booking is already committed.

Default values for codes like room or rate codes can also be defined. This API ensures a seamless handoff of externally-owned reservations into the CRS while minimizing conflicts over availability and mapping validation.

---