Reference · built on requestConnectorHospitality & property systems

Oracle OPERA Cloud

Reservations, guest profiles, housekeeping, and business events from Oracle OPERA Cloud through the Oracle Hospitality Integration Platform.

Request accessPricing ↗

About

Oracle OPERA Cloud is Oracle's property management system for hotels. Its published interface is the Oracle Hospitality Integration Platform (OHIP). Property APIs are grouped by module: rsv for reservations, fof for front desk, hsk for housekeeping, csh for cashiering, crm for profiles, blk for blocks, inv for inventory, and par for price and availability. Business events reach you by a Streaming API over WebSocket or by a Polling API. OPERA Cloud Foundation includes access to OHIP.

Through Fibric, an operator watches the events a property emits, reads the reservation or room behind each one, and proposes a check-in, a room status change, or an out-of-order block for your approval. Each proposal leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Oracle OPERA Cloud and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Reservations by hotel through getReservations and getReservation in the rsv module, with traces per reservation and per room
  • Business events for reservations, profiles, and rooms, delivered by the Streaming API (GraphQL over WebSocket) or the Polling API
  • Housekeeping room status, room conditions, discrepancies, and task sheets through the hsk module
  • Guest and company profiles with preferences through the crm module: getProfile, getGuestProfile, getCompanyProfile, getPreferenceForProfile
  • Queued reservations and reservation status statistics through the fof module: getReservationsInQueue, getReservationStatusStatistics
  • Blocks and block statistics through blk; hotel availability through par; hotel inventory and sell limits through inv
  • Folio history and deposit folios through the csh module

Proposed actions

  • Target capability: propose a check-in with postCheckIn, or an advance check-in with postAdvanceCheckIn, in the fof module
  • Target capability: propose a housekeeping room status update with putRoomRelatedStatus, or a room condition with setRoomCondition
  • Target capability: propose rooms out of order or out of service with postOutOfOrderRooms and postOutOfServiceRooms, and their completion
  • Target capability: propose a new reservation with postReservation, or changes to one with putReservation
  • Target capability: propose a guest housekeeping note with setGuestHousekeepingNotes, or a room maintenance record with postRoomMaintenance

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Set the room before the guest arrives

    Subscribe to reservation events, read the day's arrivals and housekeeping status, and propose a cleaning priority or a housekeeping note so the room is ready when the guest is.

    With Arrival Prep, Room Ready

  • Take a room out of order with a reason

    When a maintenance record or a housekeeping discrepancy appears, propose postOutOfOrderRooms with dates and a reason, and the completion when the work is done.

    With Out of Order, Predictive Maintenance

  • Recognise a returning guest

    Read the crm profile and preferences behind an arriving reservation and propose a housekeeping note and an advance check-in for the desk to approve.

    With VIP Recognition, Pre-Arrival Fix

  • Watch block pickup against cutoff

    Read blocks and block statistics from blk against hotel inventory in inv, and propose a pickup notice to the group coordinator when pickup trails the block's cutoff.

    With Block Pickup

Requirements

  • An OPERA Cloud property whose subscription includes OHIP; OPERA Cloud Foundation includes it
  • An application registered in the Developer Portal, subscribed to the API groups it calls, with an application key and an OAuth client secret
  • The gateway URL, hotel id, and enterprise id from the Environments tab of the Developer Portal
  • OPERA Cloud 22.3.0.1 or later, with business events configured in OPERA Cloud, for the Streaming API
Authentication
An application registered in the Oracle Hospitality Developer Portal, sending its application key as x-app-key, the property as x-hotelid, and an OAuth 2.0 bearer token issued with client credentials (or resource owner group credentials on older environments).

Limits

  • Property API throttling is 50 requests per second per gateway, shared by every consumer on it, with short bursts up to 100
  • The Streaming API allows 12 requests per minute, and one client per chain per gateway per application key
  • Request bodies are limited to 100KB, except named endpoints such as postReservation at 2MB
  • After a disconnection a streaming consumer must reconnect within 24 hours; Polling API calls are capped at 300 per minute per gateway

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Oracle OPERA Cloud ↗

Questions and answers

Do I need a separate Oracle product to use the OPERA Cloud APIs?
No. Oracle documents that OPERA Cloud Foundation includes access to the Oracle Hospitality Integration Platform. You receive the Developer Portal URL when the property is provisioned or migrated, register an application there, and subscribe it to the API groups you need.
How does OPERA Cloud tell Fibric that a reservation changed?
Through business events. Oracle offers two ways to consume them: a Streaming API, which is GraphQL over WebSocket, and a Polling API. Oracle recommends streaming. Business events must be configured in OPERA Cloud first, and streaming needs OPERA Cloud 22.3.0.1 or later.
Which headers does every OPERA Cloud API call carry?
Four are mandatory: x-app-key with the application key, x-hotelid with the property, Authorization with a bearer token, and Content-Type: application/json. Optional headers include x-hubid for hub-level reads across properties and x-externalSystem to stop your own changes echoing back through events.
Ask about Oracle OPERA Cloud

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Oracle OPERA Cloud through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy