Receiving the Latest Event

Scenario: A resource undergoes rapid changes, and only the latest state is of interest to your integration. The history of all changes is not of interest in this scenario.

This is a rare scenario since most systems consuming business events want a complete record of all changes to resources to keep systems in sync.

One example use case is maintaining a web cache.

Conceptual Flow

  1. Subscription Initiation: The CRM system is subscribed to the Update Reservation event and establishes a new WebSocket connection to the OHIP Streaming API and specifies the offsetType parameter.
  2. Event Emission: After connecting, the CRM system receives the latest event in the queue, skipping past the other events waiting to be consumed. Subsequently, when a reservation is created, modified, or canceled in OPERA Cloud, or a profile updated, the Streaming API emits the corresponding event.
  3. Event Consumption: The CRM system receives the event in real-time and updates its records accordingly, ensuring data consistency across platforms.
This image shows the conceptual flow for retrieving the latest events.

By implementing these use cases, hospitality businesses can ensure that their systems remain synchronized, resilient, and capable of delivering exceptional service to their guests.

Parent topic: Overview of Streaming API