August 2026 ReadMe

Overview

This document contains a list of upcoming major changes to Oracle Hospitality APIs.

What will Change Details of the Change Target Product and Version Impact Call to Action

What will Change	Details of the Change	Target Product and Version	Impact	Call to Action
OPI Cloud APIs are being separated to a dedicated Oracle Payment Interface Cloud Gateway endpoint. OHIP Developer Portal will display the OHIP Gateway Endpoint and the OPERA Payment Interface (OPI Cloud) Gateway Endpoint in the related Chain Environment details.	Consumers calling the OPI APIs (OPI Token Exchange Service, Cloud OPI Tokenization ECommerce) should no longer send them to the OHIP Gateway Endpoint but to the dedicated OPERA Payment Interface (OPI Cloud) Gateway Endpoint.	OPI Cloud 26.4 and OHIP 26.4	This is a change for integrations consuming OPI API calls. Once the new OPI Gateway Endpoint is available, the OPI API calls should no longer be sent to the OHIP Gateway Endpoint. Transition to move to the new OPI Gateway Endpoint is covered by a six-months deprecation time from the time OHIP 26.4.0 is released where the existing OHIP Gateway will still allow the OPI calls.	Prepare Now: Once the Change is Live: Check your integrations that use OPI API calls. Make sure you adjust your integration to enable using the new OPI Gateway endpoint for OPI API calls. Update and test your integration once the Chain Environment details show the new OPI Gateway Endpoint.
The elements in the `detail` array in the payload of an event sent by the Streaming API will now include only those fields ticked as filters in the OHIP developer portal.	Today, when an event is sent from the Streaming API it can (when `detail` is included in the subscribe request) include a `detail` array containing all the business data elements of the changed resource, their old and new values. Additionally, filters can be configured via the OHIP developer portal, which determine whether an event will be generated: for example, on a New Profile event only if the Firstname field is selected as a filter and the Firstname field changes then an event will be emitted. If the Firstname field does not change, no event will be emitted. This is now changing so that the `detail` array will only include business data elements which are selected as filters: If only the Firstname field is selected as a filter then only the Firstname field will be included in the `detail` array.	OHIP 26.2	Integrations expecting that all business data elements are included in the `detail` array will find business data elements missing from the payload of events that they have not ticked as a filter in the OHIP developer portal. This does not affect the polling API.	Prepare Now: Once the Change is Live: If your integrations use the `detail` array of streamed events, ensure you have ticked all business data elements required in the payload as filters in the OHIP developer portal.

OPI Cloud APIs are being separated to a dedicated Oracle Payment Interface Cloud Gateway endpoint. OHIP Developer Portal will display the OHIP Gateway Endpoint and the OPERA Payment Interface (OPI Cloud) Gateway Endpoint in the related Chain Environment details.

Consumers calling the OPI APIs (OPI Token Exchange Service, Cloud OPI Tokenization ECommerce) should no longer send them to the OHIP Gateway Endpoint but to the dedicated OPERA Payment Interface (OPI Cloud) Gateway Endpoint.

OPI Cloud 26.4 and OHIP 26.4

This is a change for integrations consuming OPI API calls. Once the new OPI Gateway Endpoint is available, the OPI API calls should no longer be sent to the OHIP Gateway Endpoint.

Transition to move to the new OPI Gateway Endpoint is covered by a six-months deprecation time from the time OHIP 26.4.0 is released where the existing OHIP Gateway will still allow the OPI calls.

Prepare Now:

Once the Change is Live:

Check your integrations that use OPI API calls.
Make sure you adjust your integration to enable using the new OPI Gateway endpoint for OPI API calls.
Update and test your integration once the Chain Environment details show the new OPI Gateway Endpoint.

The elements in the detail array in the payload of an event sent by the Streaming API will now include only those fields ticked as filters in the OHIP developer portal.

Today, when an event is sent from the Streaming API it can (when detail is included in the subscribe request) include a detail array containing all the business data elements of the changed resource, their old and new values. Additionally, filters can be configured via the OHIP developer portal, which determine whether an event will be generated: for example, on a New Profile event only if the Firstname field is selected as a filter and the Firstname field changes then an event will be emitted. If the Firstname field does not change, no event will be emitted.

This is now changing so that the detail array will only include business data elements which are selected as filters: If only the Firstname field is selected as a filter then only the Firstname field will be included in the detail array.

OHIP 26.2

Integrations expecting that all business data elements are included in the detail array will find business data elements missing from the payload of events that they have not ticked as a filter in the OHIP developer portal.

This does not affect the polling API.

Prepare Now:

Once the Change is Live:

If your integrations use the detail array of streamed events, ensure you have ticked all business data elements required in the payload as filters in the OHIP developer portal.