With our Opera integration you can seamlessly communicate between your hotel’s property management system share data across both platforms. It improves guest recognition by importing customer profiles from Opera into ResDiary, records restaurant reservations as activities on the guest’s Opera profile, and ensures hotel teams retain clear visibility of guest dining activity over time.
⚠️ Warning: You must have an active Opera Cloud Foundations License in order to integrate with OHIP, without this license connectivity cannot be established.
Below you can find a list of actions you'll be required to complete in order to complete your integration with OHIP.
Request your integration
Complete this form with the details of your venue and select Opera from the PMS options. Once the form has been completed reach out to our support team to flag your request.
Confirm your have licensing
Before proceeding ensure you have the Oracle Cloud Foundations License in place. This enables access to OHIP and is necessary for the integration to proceed.
Share relevant details with us
Once you have completed the form and flagged us about this integration, please do share the following details with our support team:
Field | Description |
Tenant / Chain Code | The hotel tenant code. |
Hotel ID | The Opera ID of the hotel. |
SSD URL | This is the URL for your Opera login page, only needed if not using OCIM. |
Enterprise ID | Only needed if using OCIM. |
Region | The region in which your Opera Cloud Environment is running. |
Activity Location | Refers to the specific location within your property where ResDiary restaurant reservations will be assigned in OPERA. |
Example Opera Profile | Name and number of a profile in Opera that can be used for testing. |
Add ResDiary as an external system in Opera
In Opera, you are required to add ResDiary as an external system using the following code:
Code required: RESDIARYOHIP
Create your restaurant activity type in Opera
In order to support restaurant reservations in Opera Cloud, please follow the steps below to create a new activity type:
From the administrator menu in Opera, click Configuration.
Click Activities, then click Activity type.
Click Select New, then enter the following:
Activity type code: Insert RESTAURANT
Description : For example you can use Restaurant Reservation
Add Activity Status Codes in Opera
Follow the steps below to create your activity status code within Opera:
From the administrator menu in Opera, click Interfaces.
Click Scheduled Activities, then click Status Codes.
Click New, then add the following two statuses:
Code: BOOK
Description: Booked
Application: EAS, External Activities Schedule
Code: CANC
Description: Cancelled
Application: EAS, External Activities Schedule
Approve the connection request
Once the connection is initiated, your administrator will receive a request to approve it. The process differs slightly based on the authentication method your Opera environment uses:
Resource Owner Group SSD Authentication:
Your chain admin receives an email from SSD with the connection request.
Complete the approval in the SSD Portal.
Ensure WSACCESS role is assigned to the user.
Client Credentials OCIM Authentication:
All your chain administrators receive a notification email.
The approval takes place within the OHIP Customer Developer Portal.
We connect and test your integration
Once the setup is complete on your side, we will enable the integration and run a few basic tests to ensure everything is working properly:
Get profile: We’ll test retrieving guest profile data from Opera.
Create booking: We’ll create a booking in Opera using a retrieved profile.
Cancel booking: We’ll confirm a booking can be successfully cancelled.
After these steps, your Opera OHIP integration is live and ready to use.