Integrating Opera Cloud (OHIP) with Triparound enables the automatic synchronization of guest, stay and charging data between the two systems, ensuring consistent information, minimizing manual processes and enhancing operational efficiency.
How to start
Before enabling the integration, make sure that:
Opera Cloud with an active OHIP (Oracle Hospitality Integration Platform) subscription is used
The process is initiated by a user with admin access to Opera Cloud
The requested Opera identifiers are available and can be provided to the Triparound team
How to set it up
As soon as the above are verified, complete the following steps:
Step 1: Share the required details with the Triparound tech support team at [email protected]
Enterprise ID
Chain code
Identity Domain region
These values identify the Opera Cloud enterprise and tenancy so that an OHIP integration user and environment can be securely created and configured.
Step 2: Approve Triparound’s OHIP integration user
Once Triparound receives the above Opera details, an integration user will be created and a connection request will be sent through OHIP to the Opera Cloud environment.
As soon as the Opera admin receives the email notification about the integration user request, they need to:
Log into the Opera / OHIP admin interface (Developer Portal / SSD, depending on the setup)
Locate the pending Triparound integration user request and approve it
Once the integration user request is approved, Triparound can access the Opera Cloud environment via OHIP using the defined permissions.
Step 3: Configure the External System for asynchronous operations
To support asynchronous operations (bulk data fetches or long‑running processes), Opera Cloud requires an External System to be configured in OHIP.
To create the External System for Triparound:
Follow the instructions outlined here
Provide Triparound with the External System Code that will be generated by Opera at the end of this process. Send this code to [email protected]
Note: This code is included in the path of every asynchronous OHIP API call and identifies Triparound as the consuming system.
Once the External System Code is received, Triparound will complete the setup on their side so asynchronous OHIP APIs can be used reliably.
Step 4: Define the room types to be synced
At this stage, the room type mapping between Opera Cloud and Triparound is required.
To do so, inform Triparound of the Opera room types that need to be visible and used in Triparound (e.g., only sellable guest room types or all types including internal/technical).
Triparound will configure the room type mapping accordingly so reservations imported from Opera appear with the correct room information in Triparound.
Step 5: Enable 2‑way connection for posting charges, if required
In case Triparound charges need to be posted back to Opera Cloud (e.g., activity or spa charges that need to be directly posted to a guest’s folio), 2-way communication needs to be enabled.
The information needed for this includes:
The Opera Cashier ID that should be used for Triparound charges
The Opera Account ID that should be used for each Triparound product which posts charges (one account per product or a shared account, depending on the accounting setup)
To enable 2-way connection for posting charges, complete the following actions:
Inform Triparound that posting should be enabled
Share the Opera Cashier ID to be used
Enter the Opera Account ID for each Triparound product that should post charges to Opera.
Note: This can be configured within each product in Triparound. Navigate to Settings & Policies > Bookings > Add Account ID and enter the relevant ID.
Once 2-way communication has been enabled, eligible bookings in Triparound will be posted as charges to guests' folio in Opera, according to the defined configuration.
Step 6: Testing and go‑live
Once the configuration has been completed, proceed with testing as per below:
Make a test reservation in Opera Cloud and verify that it appears correctly in Triparound (guest, stay and room type).
If posting charges is enabled, create a test booking in Triparound and confirm the corresponding charge appears on the Opera folio under the expected account and cashier.
As soon as tests have been completed and no issues are encountered, the integration can be considered live - Triparound will display real Opera guests and stays.