If your property runs Oracle OPERA Cloud, every vendor conversation eventually arrives at the same three letters: OHIP. Booking engines, guest messaging, payment providers, upsell tools, they all connect to your PMS through it. This guide explains what OHIP is in the language of hotel operations, not developer documentation: what it does, which events matter, what connecting a vendor actually involves, and what it changes for guest communication.
One clarification before we start, because the acronym is shared: in hospitality, OHIP is the Oracle Hospitality Integration Platform. It has nothing to do with the Ontario Health Insurance Plan that dominates a Google search for the bare term.
What is OHIP?
OHIP is the integration platform Oracle provides for OPERA Cloud. It is the official way third-party systems read data from the PMS and react to what happens inside it. Vendors register with Oracle, build against a documented set of APIs, and subscribe to events, so that when something happens in OPERA Cloud (a reservation is created, a guest checks in), the connected system knows about it within moments rather than hours.
For a hotelier, the practical meaning is this: OHIP is the reason a modern tool can respond to your PMS in real time without anyone exporting files or re-typing reservation data. The PMS stays the system of record. Connected tools listen.
How OHIP differs from older OPERA interfaces
OPERA on-premise (OPERA 5) grew up in a world of point-to-point interfaces, custom builds and per-interface certification, with OXI as the best-known example. Each connection was its own project. OHIP replaces that model for OPERA Cloud with one platform: standard APIs, self-service documentation for vendors, and event subscriptions instead of scheduled file exchanges.
Two consequences matter for your property. First, integrations behave more predictably, because every vendor builds against the same platform. Second, timing improves: an event-driven connection reacts to a booking in seconds, which is the difference between messaging a guest while the reservation is fresh and messaging them tomorrow.
If you still run OPERA 5, integrations remain possible through other methods. chatlyn, for example, connects to Oracle OPERA on-premise through scheduled reports over a secured SFTP connection, and moves to OHIP when a property migrates to OPERA Cloud.
The OPERA Cloud events that matter to operations
OHIP exposes many events. For guest-facing work, five carry most of the weight:
- Booking created. The reservation exists. This is the moment for a confirmation and the first pre-arrival touchpoint.
- Arrival date. The stay is close. Arrival information, parking, check-in time, and the first upsell window: upgrades, spa slots, dinner reservations, offered while the guest is planning.
- Check-in. The guest is on property. In-stay information and service requests take over.
- Check-out. The stay ends. A thank-you and a review request, timed while the experience is fresh.
- Cancellation. The reservation is gone, and every pending message for that stay stops with it. This event is what keeps automation polite.
A guest communication platform built on these five events can run the whole journey from the PMS outward: the property changes nothing about how it works in OPERA, and the messages follow the reservation.
What connecting a vendor through OHIP actually involves
The vendor does the building. Your property’s role is authorisation and coordination: granting the vendor access to your OPERA Cloud environment, and aligning with Oracle on credentials for each property. Two things are worth knowing before you start:
- Setup is per property. OHIP supports multi-chain organisations, but each property runs its own integration. A ten-property collection is ten authorisations, not one.
- The coordination is the work. The technology side is standardised; the timeline usually depends on how quickly the Oracle-side authorisation for your property completes. With chatlyn, our integration team runs that process together with your IT contact and Oracle, property by property.
You do not need your own developers. You need someone who can approve access and answer questions about how your properties are set up in OPERA.
What OHIP costs, honestly
There are usually two sides to the bill. Oracle meters integration usage on its platform, and vendors charge for building and operating the connection. The total depends on your property’s event volume, so a flat number quoted without asking about your volume is a number to distrust. Whichever vendor you evaluate, chatlyn included, ask for the full figure in writing, Oracle side and vendor side, before you sign.
What OHIP means for guest communication
Realtime events change what messaging can do, because timing is most of the value. A pre-arrival WhatsApp message sent minutes after the booking, with the guest’s name, stay dates and quick replies for upgrades or spa treatments, performs differently from the same message sent from a nightly export. Spa Resort Geinberg runs exactly this journey with chatlyn and sees a 95% open rate on WhatsApp, with 86% of enquiries answered by the AI on webchat and WhatsApp before staff are needed.
The division of labour stays clean: chatlyn reads reservation data from OPERA Cloud to personalise and time each message, the AI answers routine questions in more than 100 languages in around 3 seconds on WhatsApp and webchat, and your team takes over the moment a request needs a person. OPERA remains the system of record throughout.
Read how the chatlyn OPERA Cloud integration works in detail, or start with the wider question of AI for OPERA Cloud hotels. To assess where your property stands, download the free whitepaper: Is your OPERA Cloud hotel ready for AI?
Frequently asked questions about OHIP
Is OHIP the same as OPERA Cloud? No. OPERA Cloud is the property management system. OHIP is the integration platform Oracle provides so other systems can connect to it.
Does OHIP work with OPERA 5? No, OHIP is for OPERA Cloud. Properties on OPERA on-premise integrate through other methods; chatlyn connects to OPERA 5 via secured SFTP and switches to OHIP after a migration.
Do we need our own developers to use OHIP? No. The vendor builds and operates the integration. Your property authorises access and coordinates with Oracle, and a good vendor runs that process with you.
How long does an OHIP integration take? It depends mainly on the Oracle-side authorisation for your property, which is why serious vendors will not promise a fixed date before that process starts. chatlyn’s team manages the steps with you for each property.
Which chatlyn features use OHIP data? Guest journey automations triggered by the five reservation events, and reservation context shown next to each conversation in the inbox, so the front office replies with the stay details in view.
Is OHIP the Canadian health insurance plan? Different OHIP. In hospitality the acronym means Oracle Hospitality Integration Platform; Ontario’s health plan happens to share it.
