Feature Summary

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	Documentation
Enhanced Subscription Naming Conventions	The Developer Portal Subscriptions section has been renamed when registering an application.	Improves the clarity and consistency of subscription names, making subscriptions easier to identify and understand.	Registering an Application
Enterprise Analytics API and Cross-Chain Visibility	The Enterprise Customer Developer Portal is now available as the primary access point for the Enterprise Analytics API. In this initial release, the portal provides: Access to the Enterprise Analytics API View-only capabilities for selected developer resources and information such as Applications and Environments	Provides enterprise-wide access to analytics data and centralized visibility of applications and environments across all chains, enabling enterprise reporting, automation, and operational insights.	Working in the Enterprise Context in the Developer Portal
Partner Access to the OHIP Analytics API	Partners can access the OHIP Analytics API for analytics-related use cases without requiring broader access to Oracle Hospitality APIs. This capability supports partners who need programmatic access to OHIP Analytics data that relates to their own API usage. Access is limited to analytics-specific use cases and does not require customer approval because the usage data belongs to the partners. Partners can use a self-service process to add or remove the required OHIP APIs environment for either UAT or Production, generate the required client credentials, and call the OHIP Analytics API according to their assigned role permissions.	Provides partners with secure, least-privilege access to their own analytics data through a self-service experience without granting unnecessary access to other Oracle Hospitality APIs.	Adding an Environment
On-Demand Analytics Search	The Developer Portal Analytics dashboard now loads results when you select Search rather than automatically.	Improves Analytics dashboard performance by allowing users to retrieve data only when they select Search, giving greater control over queries and reducing unnecessary processing.	Analytics Using Analytics
Application Type Removed from the Developer Portal	Developer Portal Applications no longer require selection of Application Type.	Simplifies application registration and management by removing the unnecessary Application Type field from the Developer Portal.	Not applicable
Developer Portal Application Limit Increased	The Developer Portal Applications limit has been increased from 100 to 200.	Supports platform scalability by increasing the maximum number of Developer Portal applications from 100 to 200, improving the overall developer experience.	Registering an Application
Re-issue Client IDs Using the New Naming Format	Added the ability to re-issue the OHIP Environment clientId to the new consistent , more descriptive naming format consistent with that generated for new clientIds.	Makes client IDs easier to identify and manage, improving administration, auditing, and troubleshooting.	Environments (Gateways and Credentials) with Client Credentials Authentication Scheme (OCIM)

Streaming

Feature	Description	Operational Benefits	Documentation
Automatic Management of Inactive Event Streams	Event streams that have not had a successful streaming connection are now automatically managed based on inactivity. If a stream has not had a successful connection for 4 days, a warning email is sent to the email address associated with the application. The email advises that streaming will be automatically disabled if the streaming consumer does not connect within the next 3 days. If a stream has not had a successful connection for 7 days, streaming is automatically disabled. Event processing stops, the stream configuration is retained, and the existing stream allocation is retained. The streaming toggle is shown in the disabled state in the Developer Portal. Turning on the streaming toggle does not reset the inactivity counter. The counter is reset only when the streaming consumer successfully connects to the stream. If a stream remains inactive for 30 days, the stream is permanently deleted. The associated configuration and queued events are also removed.	Helps users spot inactive streams through automatic notifications and automatic disablement while retaining configuration, reducing unnecessary resource consumption and reclaiming unused capacity after prolonged inactivity.	Working with Events in the Developer Portal
Enable or Disable Event Streaming for an Environment	Users can temporarily disable event streaming for a selected environment within an application from the application’s Events > Subscribed tab. When event streaming is disabled, events from the selected environment are not sent to the application and are not available for later delivery. The existing event subscription configuration is retained. Event streaming is managed independently for each application and environment combination. Disabling streaming for one environment does not affect other environments in the same application or the same environment in another application. Users can enable streaming again from the Events > Subscribed tab.	Allows users to temporarily pause event streaming without removing subscription configuration, reducing administration and making it easy to resume streaming when required.	Working with Events in the Developer Portal

Feature

Description

Operational Benefits

Documentation

Automatic Management of Inactive Event Streams

Event streams that have not had a successful streaming connection are now automatically managed based on inactivity.

If a stream has not had a successful connection for 4 days, a warning email is sent to the email address associated with the application. The email advises that streaming will be automatically disabled if the streaming consumer does not connect within the next 3 days.

If a stream has not had a successful connection for 7 days, streaming is automatically disabled. Event processing stops, the stream configuration is retained, and the existing stream allocation is retained. The streaming toggle is shown in the disabled state in the Developer Portal.

Turning on the streaming toggle does not reset the inactivity counter. The counter is reset only when the streaming consumer successfully connects to the stream.

If a stream remains inactive for 30 days, the stream is permanently deleted. The associated configuration and queued events are also removed.

Helps users spot inactive streams through automatic notifications and automatic disablement while retaining configuration, reducing unnecessary resource consumption and reclaiming unused capacity after prolonged inactivity.

Working with Events in the Developer Portal

Enable or Disable Event Streaming for an Environment

Users can temporarily disable event streaming for a selected environment within an application from the application’s Events > Subscribed tab.

When event streaming is disabled, events from the selected environment are not sent to the application and are not available for later delivery. The existing event subscription configuration is retained.

Event streaming is managed independently for each application and environment combination. Disabling streaming for one environment does not affect other environments in the same application or the same environment in another application.

Users can enable streaming again from the Events > Subscribed tab.

Allows users to temporarily pause event streaming without removing subscription configuration, reducing administration and making it easy to resume streaming when required.

Working with Events in the Developer Portal