1 Overview
Note:
API usage and capabilities are subject to change. For more information on API versioning, see the Versioning topic in the Oracle Hospitality Integration Platform User Guide.
For the most comprehensive and up-to-date information, including additional query parameters and detailed descriptions, always refer to the latest API specifications in GitHub. This will ensure that you are accessing the most current and complete set of features available.
The Oracle OPERA Cloud Hotel Property Interface application (IFC8) is used to connect various on-premise vendor management systems with the Oracle Property Management system. It sends out room and guest data to the vendor system, for example, check-in of guest and check-out of guest. The interface can also receive data (for example, charges or status changes) from the external system to be stored in OPERA Cloud using synchronous TCP/IP or serial connection exchanging messages, which are based on either Oracle's universal FIAS API, XML-POS API, or many vendor-based specifications.
-
Telephone Management Systems (TMS) or middleware to TMS systems
-
Door Locking Systems
-
HSIA Internet Access Systems
-
Point of Sale Systems (Restaurant, SPA, Golf)
-
Video Services Systems
-
Guest Service Systems
-
Minibar Systems
-
Building Management Systems
-
Miscellaneous / Other systems installed at property
The typical data exchanged through the Property Interface are check-in / check-out notifications (for example, room and guest details, guest rights), charge postings received from vendor systems, make door key requests, wake up requests, credit card payment requests, guest message notifications, room maid status notifications, and many more. This data is exchanged at the time the action occurs in OPERA Cloud or on the external system and is usually exchanged without a delay in transmission.
For IFC8 actions exchanged between OPERA Cloud and an external application, the REST APIs utilize multiple ways of connection.
There are inbound actions from the external system that are exposed through the OHIP REST APIs. Some examples of these inbound actions are sending charges to the guest's room or hotel account, inquiry requests for guest information by a Point-Of-Sale system, sending room status changes, wake up requests, and guest bill balance requests.
Some outbound IFC8 actions are exposed using streaming APIs. Some examples include check-in, check-out, room-move notifications, wake-up requests, and guest text messages.
Specific outbound synchronous messages are exposed using additional outbound service connections from the PMS to the external system. Some examples are door lock key actions (for example, make key and delete key), which require related response messages.