1 Feature Summary

To learn about the new and changed APIs available through the Oracle Hospitality Integration Cloud Service, follow the links below:

OPERA Cloud:

New features | Deprecated features | Resolved issues

OPERA Distribution:

New features | Deprecated features | Resolved issues

Portal

Feature Description Operational Benefits
Self-Service Module Level Access Control Management

This enhancement introduces self-service management for Module Level Access Control in the OHIP Developer Portal.

Customer administrators can enable or disable Module Level Access Control for an environment from the Global Administration area of the Developer Portal. When enabled, customers can choose which OPERA modules and functional areas each customer-created client ID can access.

For each customer-created client ID, customers can also grant Sensitive Data Access where required. This allows approved client applications to receive certain sensitive data elements, such as identity document IDs and dates of birth, in API responses. This permission does not allow access to highly restricted information such as credit card numbers.

When a partner requests access to an environment where Module Level Access Control is enabled, the partner must select the appropriate OPERA modules and Sensitive Data Access, if required, before submitting the request. The customer can then review the requested access and approve it accordingly.

This feature helps organizations apply more precise access controls so that client applications are granted access only to the OPERA modules, functional areas, and sensitive data access required for their integration

Module Level Access Control gives customer administrators greater control over client application permissions directly from the Developer Portal.

Benefits include:
  • Customer administrators can enable or disable Module Level Access Control for an environment without contacting Oracle Support.
  • Customers can control module and functional-area access for each customer-created client ID.
  • Customers can grant Sensitive Data Access only when required for approved integration use cases.
  • Partners requesting access to Module Level Access Control-enabled environments must specify the modules required, and if applicable Sensitive Data Access before submitting the request.
  • Customers can review the access partners have requested before approving partners' access to their environment.
  • Improves governance and reduces unnecessary access across client applications and partner requests.
  • Self-service administration model for managing access controls.
Data APIs Documentation Now Available in the Developer Portal The Developer Portal APIs dashboard has a new Content option for Data APIs and a new API Category for the Reporting and Analytics Data APIs for viewing available Data APIs. Customers and partners can efficiently understand, consume, and integrate with the specified APIs.
Include enterpriseId on the Analytics Screen in the Developer Portal The Developer Portal Analytics dashboard has a new query filter for the Enterprise ID. The additional filter lets users select a specific enterprise when querying results or to search across multiple enterprises to which the application has access. This is valuable for partners managing connections with multiple customer enterprises. While customers typically operate within a single enterprise, this feature can also help identify unexpected or unfamiliar enterprise entries that may result from partner-related errors.
Pagination for Developer Portal Applications and Events Subscribed pages The Developer Portal Applications & Environment pages and some sub-pages now provide a seamless experience by automatically loading additional content when scrolling down the page, eliminating the need to manually refresh or wait for all items to load.
  • Adding Pagination on Scroll enhances the user experience for most common used developer portal pages.
  • The feature ensures proper loading of content by scrolling, faster loading of content, and decreasing performance issues while loading, especially for displaying a large number of results like lists of Applications or assigned Hotels.
Show permissions from lowest OPERA version for Affiliated customers where one chain exists in multiple environments

When an affiliated customer requests access to OPERA Cloud foundation environments that share the same chain code across multiple environments within the same Enterprise, the permission selection experience is now aligned across all associated environments.

If module-level access control is enabled in any of the environments, the system presents a unified list of permissions that are supported in every environment using that chain code. The list is based on the lowest OPERA version among the associated environments, ensuring all selected permissions can be approved and function consistently after access is granted.

This enhancement prevents affiliated customers from requesting permissions that are unavailable in some environments, streamlines the approval process, and ensures reliable access across environments.

If none of the environments have module-level access control enabled, the existing access request workflow continues unchanged.

  • Ensures affiliated customers can request only those permissions that are supported across all associated OPERA environments, reducing approval failures and rework.

  • Prevents mismatches caused by differences in OPERA versions when the same chain exists in multiple environments.

  • Simplifies customer review and approval by presenting a consistent and valid set of permissions.

  • Reduces operational support issues related to invalid or non-functional permission requests.

  • Maintains existing workflows when module-level access control is not enabled, ensuring no disruption to current operations.
Approving and Rejecting Streams Usability Improvement

The approval workflow for streaming subscription requests has been enhanced to improve usability when managing large hotel chains.

When approving, rejecting, or retrying subscription requests that include a large number of hotels, action buttons are now accessible without requiring users to scroll to the bottom of the list.

  • Improves usability for enterprise and large-chain environments.

  • Reduces time required to process subscription requests.

  • Enhances overall workflow efficiency in the Developer Portal.
Revoke an App's Access to Consume Business Events from a Given OPERA Environment

Customers who approve partner applications to consume OPERA Cloud business events enable those applications to receive event notifications generated from their OPERA environments. When such access is approved, an external system interface is automatically created in the selected OPERA environment to support the integration.

With this enhancement, customers can now revoke a partner application's access to consume business events directly from the OHIP Customer Portal. This lets customers discontinue integrations when required, such as when a contract with a partner ends or when access to operational data must be restricted.

  • Improved Data Control - Customers can quickly revoke a partner application's access to business events, ensuring that operational data is only shared with authorized integrations.

  • Centralized Integration Management - Partner integrations can be managed directly through the OHIP Customer Portal, eliminating the need to manually manage external systems within OPERA.

  • Faster Deactivation of Integrations - When access is revoked, the associated external system and event subscriptions are automatically disabled or removed, preventing further event delivery.

  • Automated Communication - Partners are automatically notified via email when their access is revoked, ensuring transparency and reducing the need for manual communication.
Ask Oracle Now Available in the OHIP Developer Portal

The OHIP Developer Portal introduces an AI-powered assistant, Ask Oracle, which enables users to ask questions in natural language while working with OHIP integrations.

Ask Oracle provides contextual responses based on OHIP knowledge sources, including documentation, implementation guides, and integration best practices. The assistant helps users quickly find relevant information and guidance without navigating multiple documentation sources.

This capability is managed through the Global Administration feature controls framework, allowing administrators to enable or disable AI-powered functionality for their organization as needed.
  • Faster Access to Information - Users can ask questions directly and receive relevant answers without searching across multiple documentation sources.
  • Improved Developer Productivity - Real-time responses help resolve integration questions more efficiently during development.
  • Contextual Guidance - Responses are tailored to OHIP APIs, integration patterns, and common integration scenarios.
  • Faster Onboarding - New developers and partners can learn OHIP capabilities more quickly using conversational queries.
  • Multi-Language Support - Users can interact with the assistant in multiple languages, improving accessibility across global teams.
Copy and Share Customer Environment Details with Partners

Customers onboarding partner integrations often need to share their enterprise details, such as Enterprise ID, Chain Code, Region, and Environment Type. Previously, these details had to be gathered manually from multiple fields within the portal, which could be time-consuming and prone to errors.

With this enhancement, enterprise details are now presented in a single consolidated view within the portal. Customers can copy all required enterprise details with a single click, allowing them to quickly share accurate and structured information with partners during onboarding or integration setup.

The copied information is formatted in a clear and structured format, making it easier to paste into emails, documentation, or communication channels used when coordinating with vendor partners.

This improvement simplifies the onboarding experience and reduces the effort required to provide enterprise configuration details to integration partners.

  • Improved Customer Experience - Customers can quickly access and copy enterprise details from a single location.

  • Faster Partner Onboarding - Required information can be shared with partners immediately without manually collecting it from multiple fields.

  • Reduced Errors - Structured copying ensures consistent and accurate enterprise details are shared.

  • Lower Support Overhead - Simplifies the process and reduces customer confusion during integration setup.
Extend Customer Admin Opt-Out for AI Features in OHIP

The Global Administration area of the OHIP Developer Portal now provides administrators with a centralized control to enable or disable selected platform features across their organization.

This capability allows administrators with the OHIPADMIN role to manage optional features directly from the Developer Portal without requiring Oracle operational support. These controls can be used to manage the availability of optional capabilities, including features such as AI-powered functionality, across the organization.

By providing a centralized opt-in and opt-out mechanism, administrators can control when specific capabilities are enabled within their environments.
  • Centralized Feature Management - Administrators can enable or disable selected platform capabilities from a single location in the Developer Portal.
  • Improved Governance and Compliance - Organizations can control the availability of optional capabilities to align with internal policies, regulatory requirements, or regional constraints.
  • Controlled Feature Rollout - Administrators can pilot new capabilities, roll them out gradually, or disable them if needed.
  • Reusable Platform Framework - The opt-in and opt-out mechanism provides a standardized framework for managing optional platform capabilities as new features are introduced.

Streaming

Feature Description Operational Benefits
Automatically enable Streaming API for newly provisioned customers

This enhancement simplifies access to the OHIP Streaming API by automatically enabling streaming capabilities for newly provisioned customer environments.

Previously, access to the Streaming API required customers or partners to submit a request and complete training before the feature could be enabled. This requirement was introduced to reduce the risk of poor integrations when the streaming capability was first introduced.

With improved documentation, including the Streaming Implementation Guide, and broader support for streaming protocols in modern development frameworks, the risk of incorrect implementations has decreased.

This change aligns OHIP with current market expectations by making streaming functionality readily available while maintaining guidance through existing implementation documentation.

  • Simplified Access to Streaming - New customers can begin using the Streaming API without submitting enablement requests.

  • Faster Integration Setup - Streaming capabilities are available immediately when eligible environments are provisioned.

  • Reduced Operational Overhead - Provisioning teams no longer need to manually enable streaming for new environments, and existing environments are enabled as part of rollout activities.

  • Improved Developer Experience - Integrators can start implementing streaming integrations immediately using available documentation