> ## Documentation Index
> Fetch the complete documentation index at: https://docs.journey.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate Oracle (Opera) with Journey Rewards

> Connect Oracle (Opera) PMS to Journey Rewards in just a few clicks.

<Info>
  Prerequisites — before you start:

  * An active Journey Rewards partner account.
  * A property running Oracle Hospitality OPERA Cloud PMS with permission to enable third-party integrations.
  * Access to the Oracle Hospitality Integration Platform (OHIP) Developer Portal (hotel/chain or partner) and the ability to register an application and subscribe to APIs.
</Info>

## Overview

Connecting **Journey Rewards** to **OPERA Cloud via OHIP** lets Journey sync reservations and guest profiles so you can recognize loyal guests and power direct-booking rewards with zero manual effort. Oracle exposes OPERA Cloud capabilities through OHIP REST APIs, with standard OAuth-based authentication and application registration in the OHIP Developer Portal.

## Enable the integration

1. **Request/confirm OHIP access & partner enablement**\
   If your organization doesn’t already have OHIP access, work with your Oracle Hospitality account team to enable the **Oracle Hospitality Integration Platform** and Developer Portal access (hotelier or partner). You can start from Oracle’s OHIP pages (“Get started,” “Contact us”).
2. **Register a Journey integration application in OHIP**\
   Sign in to the **OHIP Developer Portal** and **register an application**. Provide 24×7 contact details (used by Oracle for incident notifications) and subscribe the app to the APIs you’ll need (Profiles, Reservations, etc.).
3. **Create environments & obtain credentials**\
   Add an environment (UAT/PROD), then get the **gateway URL** and **OAuth credentials** (Client ID/Secret). OPERA Cloud currently uses **OCIM client-credentials** for integrations; you’ll request an access token, then call APIs at the gateway.
4. **Activate External System in OPERA Cloud (property/chain)**\
   In OPERA Cloud, activate/configure the **External System** entry for your integration so OPERA can publish/consume data and business events with Journey (can be done at Hub/chain or property). If you use Cloud Hub auto-configure, OPERA will create interface setups, controls, and business events for you.
5. **Subscribe & verify API access**\
   From the OHIP app, ensure your application is subscribed to the relevant **Hospitality APIs** and that the hotel/chain environment identifier is known (Oracle’s sandbox uses `SAND01`; your production hotel IDs will differ). Obtain a token and test a simple read (e.g., hotel details) to confirm connectivity.
6. **Journey connects & validates sync**\
   Once credentials and OPERA External System activation are confirmed, Journey will complete the connection and validate that reservation and guest profile events are flowing as expected.

> **Property staff typically have no further setup** beyond confirming the External System is enabled and that Journey is authorized to connect.

## What gets synced (typical)

* **Guest profiles**: name, contact info, IDs/loyalty references (via Profile APIs and supported lookup/download patterns).
* **Reservations**: create/modify/cancel events, stay dates, room/Rate/Folio references (via Reservation APIs and configured business events). *(Exact payloads and event coverage depend on the specific OHIP APIs you subscribe to and the OPERA Cloud configuration for External Systems & Business Events.)*

## Authentication & access

* **OAuth 2.0 (Client Credentials)** via **OCIM** is the current scheme for OPERA Cloud integrations. Your OHIP application (per chain/partner) uses the issued **Client ID/Secret** to obtain tokens and call the gateway URL.

## Security & compliance

* Oracle manages application registration and incident procedures through the OHIP Developer Portal; ensure the app’s 24×7 contact details are accurate (Oracle may disable the integration if incident communications aren’t acknowledged).

## Validation & go-live

Journey will confirm:

* Successful token issuance and API access in your **UAT/PROD** environment.
* Initial **reservation** and **guest profile** syncs.
* Ongoing events (new bookings, modifications, cancellations, check-in/out) arrive within expected SLAs for your OHIP configuration.

If data isn’t syncing \~30 minutes after activation, contact Journey Support with your property and application details.

## Need help?

* **Oracle Hospitality (OHIP) inquiries:** Use “Contact us / Request a demo” on the OHIP page to reach the Oracle team for access, app issues, or subscription questions.
* **Journey Support:** [support@journey.com](mailto:support@journey.com) (include property name/code and your OHIP application name).

## Next steps

* Invite staff to Journey so front-desk and revenue teams can view guest loyalty profiles.
* Configure Campaigns and Offers (e.g., bonus points for direct bookings).
* Promote loyalty on your booking engine and in confirmation emails.