The ResDiary - Opera integration enables seamless communication between your hotel’s property management system and ResDiary. Its primary purpose is to:

  • Improve guest recognition by importing customer profiles from Opera to ResDiary.

  • Ensure a unified guest history by syncing restaurant reservations to the guest’s Opera profile as activities.

  • Support ongoing visibility of guest dining activity


1. Customer Lookup

  • Begin by entering the surname and/or first name of the customer into the ResDiary booking form.
  • The system will first search for a matching customer profile in ResDiary.
  • If no matching profile is found, the Opera integration is triggered automatically, and ResDiary will search the Opera database for matching customer profiles.
  • Matching profiles from Opera will be displayed within the search results.An Opera can be identified by the presence of an Opera ID on the customer profile


  • If a customer profile already exists in ResDiary but does not include an Opera ID, you can manually enter the Opera ID into the ResDiary profile to link it with the corresponding Opera profile. Once the profile is correctly linked, using the Opera-imported version of the customer profile ensures that all future restaurant activities are synchronised back to Opera.


2. Selecting and Importing an Opera Customer

  • Click on the appropriate customer from the Opera search results.

  • ResDiary will the import the customer profile into the ResDiary database.

  • Once imported, the customer can be selected for the booking and used in future reservations without re-querying Opera.


3. Syncing Booking Details to Opera

  • Once a booking using the Opera Profile is saved in ResDiary, the reservation is recorded as an Activity on the customer’s profile in Opera.



4. Handling Future Reservations 

If the Guest makes subsequent Restaurant Reservations (even when they may not be resident in the hotel) details of those reservations will still be passed up to their Profile in Opera, so the hotel staff have a complete view of Customer activity in the hotel.


Functional Limitation

a) If the Guest calls (the Opera User) to cancel any Activity, the restaurant reservation must be cancelled in ResDiary – it cannot be cancelled from within Opera directly.


b) If a Guest cancels their hotel booking the restaurant reservation will not be simultaneously cancelled. The restaurant reservation must be cancelled in ResDiary



Integration Setup Requirements  

To enable the ResDiary integration, your property must be running OPERA Cloud and have an active subscription to OPERA Cloud Foundation. This is a prerequisite for enabling any external integrations, including ResDiary, as it provides the core functionality and interface access required to support the connection.   

Before we can proceed with the integration, ResDiary requires: 

  • Confirmation that OPERA Cloud Foundation is currently running for your property 
  • Your OPERA Cloud URL (the web address used to access your OPERA Cloud environment) 
  • Your Hotel ID 
  • Activity Location Code 
  • Your Enterprise ID 

Once the above details are received, your OPERA administrator will need to authorise the connection. 

  • For Opera environments using the Resource Owner Group authentication scheme (SSD), partner connections are approved by the chain administrator. The administrator will receive an approval request via email from SSD and must approve the partner request within the SSD portal. 
  • For Opera environments supporting a Client Credentials authentication scheme (OCIM), an email notification is sent to all the chain administrators informing them about the new connection and approvals take place within the OHIP (Customer) developer portal.