Skip to main content

Enabling Streaming API for Oaky – Opera Cloud Integration

Learn how to enable the Opera Cloud Streaming API for Oaky integrations, ensuring near real-time updates for reservations and events.

Written by Darrel

Oaky has introduced Streaming API support for Opera Cloud OHIP integrations, moving away from the Polling API. This ensures near real-time updates for reservation events.
​

Note: All previously configured OHIP settings remain unchanged. The Streaming API configuration described in this guide is used only for reservation business event consumption by Oaky. It does not replace or modify any other Business Events that are already configured in your Opera Cloud environment for other integrations or applications. Those existing event configurations should remain in place.

Polling API vs Streaming API

Feature

Polling API (Current)

Streaming API (New)

Data Delivery

Oaky requests data from OHIP every 30 minutes

OHIP continuously sends data to Oaky as it becomes available

Latency

Potential delay; not real-time

Near real-time updates

Connection

Intermittent

Persistent open connection

Prerequisites for Enabling Streaming API

Before enabling Streaming API for a hotel/chain:

  1. OPERA environments must be added for event consumption (handled by Oaky during initial onboarding).

  2. The OPERA environment must have streaming enabled.
    ​

  3. Events template must be prepared by Oaky for the Reservation module.
    ​

  4. Oaky submits a request to subscribe the chain to these events.
    ​

  5. Chain admin must approve the request and select the hotels to consume events.

Important

The Streaming API configuration for Oaky only subscribes to the Reservation business events required by the Oaky integration (for example, reservation creation, updates, check-in, check-out and cancellations).

If your Opera Cloud environment already has other Business Events configured for different applications or integrations, do not remove or modify them. Enabling Streaming API for Oaky only adds the required reservation event subscription and does not impact any existing event templates or subscriptions already configured in Opera Cloud.

Approving Events in Developer Portal

Chain/Hotel admins with Developer Portal access can approve event consumption to protect their data.

Steps to Approve Event Subscriptions

  1. Open the Developer Portal and click the Applications tab.

  2. Search for and click an application to open it.

  3. Click the Partner Applications tab. (Note: Applications with pending event subscriptions appear with a red ribbon icon on the application card.)

  4. Click an application with a pending event to open it.

  5. Click the Events tab.

  6. Click Next to proceed with approval.

  7. Select the properties for the event subscription and click Next.

  8. Click Approve.

After approval, the event status changes to ‘In Progress’ and then to ‘Approved’. Partners (Oaky) can monitor this status in the Developer Portal.

Verify Opera Cloud external system setup (OHIP592)

When Streaming API is enabled for an Opera Cloud OHIP integration, Oracle automatically adds a new external system for Oaky:

  • Code: OHIP592

  • Description: OHIP External System for Application(ID): Oaky(OHIP592)

You can see this under Configuration > Setup > External Systems in Opera Cloud (alongside entries such as OAKY1, SYNXIS2, etc.).

External System OHIP592

Required publisher configuration

To ensure that reservation business events from other channels such as SYNXIS (creation, updates, cancellations) are sent to Oaky via Streaming:

  1. Open the External Systems configuration in Opera Cloud.

  2. Locate the external systems OHIP592 and SYNXIS2.

  3. In the Publishers/Subscribers configuration, make sure there are two-way subscriptions:

    • OHIP592 → SYNXIS2 (OHIP592 subscribed to changes coming via SYNXIS2)

    • SYNXIS2 → OHIP592 (SYNXIS2 subscribed to send its reservation events to OHIP592)

This should mirror the existing 2-way setup between OAKY and SYNXIS2 that is already in place for the Polling API.

If your CRS/external system is not named SYNXIS2, apply the same principle: ensure mutual publisher/subscriber links between that CRS external system and OHIP592.

Keep OAKY1 for rate and product updates

  • Do not remove or disable OAKY1 or its publishers.

  • OAKY1 continues to be used for:

    • Rate and availability updates

    • Package / product updates

Streaming API (via OHIP592) only takes over reservation event delivery; existing Polling/API flows via OAKY1 remain required for pricing and product data.

Reference

For more details, see Oracle documentation: Streaming API - Working with Events in the Developer Portal.

Did this answer your question?