OPERA Cloud (OHIP) β setup guide
Provyl connects to Oracle OPERA Cloud through the Oracle Hospitality Integration Platform (OHIP), Oracle's REST gateway for OPERA. Once connected, check-ins, check-outs, room moves and reservations in OPERA reach the rooms here: the TV greets the guest in their language, the phone pairs, the room is reset at check-out, and guests get their app link before arrival.
Provyl only reads from OPERA β it never changes a reservation, a profile or a room there.
What you need
There are two sides: Provyl's application on OHIP (once, for all hotels), and the hotel's permission for its own OPERA Cloud environment.
| What | Where it comes from | Field in Provyl |
|---|---|---|
| Application key | Provyl's application in the OHIP developer portal (Applications β the app β App key) | Application key |
| Gateway URL | The hotel's OHIP environment (Environments β the environment card), e.g. https://xxxx.hospitality-api.eu-frankfurt-1.ocs.oraclecloud.com |
Gateway URL |
| Hotel code | OPERA Cloud's code for the property, e.g. SAND01 β sent as x-hotelid |
Hotel code |
| Client id and client secret | The OAuth client of the environment (OPERA Cloud Identity Management) | Client id, Client secret |
| Enterprise id | Shown on the same environment card, next to the client | Enterprise id |
| (older environments only) Integration user and password | Created by the hotel in OPERA Cloud for integrations | Integration user, Integration user password |
Use either the OAuth client (client id, secret, enterprise id) or the integration user β new environments use OAuth client credentials. The secrets are stored encrypted and can never be shown again.
The application must be allowed to call these OHIP APIs:
- Reservations (
rsv) β in-house guests, arrivals and single reservations; - Room configuration (
rm/config) β the hotel's rooms and their room types.
Steps for the hotel
- In OPERA Cloud (or by asking the Oracle account manager), enable Provyl's application for the property's environment β on the OHIP developer portal this is the hotel subscribing the environment to our application.
- Create or find the OAuth client for the environment, and note the enterprise id, the gateway URL and the hotel code.
- Send these to the Provyl administrator of the site β or enter them yourself as below.
Steps in Provyl
- Settings β Integrations β PMS β OPERA (first in the list) β Connect. Fill in the fields above; leave Integration user empty when you use an OAuth client. Choose Reservations: All reservations, or Only rooms linked here to try it with a few rooms first.
- Test connection β Provyl gets a token and reads one room of the hotel. Connected to OPERA Cloud hotel SAND01 means it works. See Problems otherwise.
- Read rooms from OPERA β the physical rooms are read (pseudo rooms and meeting rooms are left out) and linked to
the rooms here by room number, exactly as OPERA writes them (leading zeros count: OPERA's
010is not10). Link the others by hand, or leave them unlinked β nothing happens for unlinked rooms. - Room types β OPERA's room type codes (for example DBL, KNG) appear on the same card. Link each to a room type here; before check-in a reservation only knows its room type, which decides the template and choices a guest sees before arriving.
- Sync now β a first full run: guests in house are checked in to their linked rooms, and reservations arriving in the next 90 days get their stay and app link.
- Make sure only OPERA is on β switch off any other PMS and the Local daily check-in (it pauses by itself while a PMS is on).
From then on Provyl reads OPERA every 5 minutes (OHIP sends its business events only over its streaming service, not to web addresses), so a check-in in OPERA reaches the room within about 5 minutes. Reservations arriving in the next 90 days are caught up once an hour. The connection's log shows only runs that changed something or failed; Sync now runs at once.
How OPERA's data is used
| In OPERA | In Provyl |
|---|---|
| Reserved, Due in | Booked β the stay and its app link |
| In house, Due out, Walk-in, Day use | Checked in to the linked room |
| Checked out | Checked out β TV restarts, phone disconnected, room reset |
| Cancelled, No show | Canceled β the app link says so |
| Waitlisted and others | Not shown |
| Room of the reservation | The linked room (a changed room is a room move) |
| Guest's given name and surname | Greeting on the TV (deleted at check-out; the console shows only the first letter) |
| Guest's language (EN, DE β¦) | The language of the TV and phone, if the hotel offers it (see Guest language) |
Problems
| Message | What to do |
|---|---|
| OHIP refused the credentials (401) | The client id, client secret, enterprise id or application key is wrong β type the secret again. With an integration user, check its password and that it is not locked. |
| The credentials work, but they may not read hotel β¦ | The hotel has not enabled our application for this hotel code, or the Reservations / Room configuration APIs are not allowed. |
| OPERA answered 404 | The gateway URL points to another environment, or the hotel code is wrong. |
| A guest checked in in OPERA does not appear | Wait 5 minutes or press Sync now. Then check the room is linked under Rooms and stays, and Reservations is not Only rooms linked here with that room unlinked. |
| A room stays checked in after check-out | The room here was checked in from the console β the PMS checks out only guests it checked in. Check it out in Guest Operations β Rooms. |
Testing before a hotel goes live
- Oracle's partner sandbox. OHIP partners get a shared, non-production OPERA Cloud environment (with OAuth client credentials) on the Environments page of the partner developer portal β follow Oracle's Quick Start for Partners. Calls there are billed by Oracle per use. Enter its gateway URL, hotel code, client and enterprise id in a test site (Only rooms linked here, one or two rooms), then create, check in and check out a test reservation in the sandbox and watch it arrive within 5 minutes.
- The hotel's UAT environment. Most OPERA Cloud hotels also have a test (UAT) environment β with the hotel's agreement, connect a Provyl test site to it the same way.
- Production access for a hotel needs Provyl's listing in the Oracle Hospitality Cloud Marketplace; then the hotel enables the application for its production environment.