September 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

The profilesIndividuals GraphQL API will now return only Guest profile types.

Following this update, the API will no longer returns non-Individual profile types. Currently, Travel Agent, Company, and Source profile types may be included in results to the profileIndividuals GraphQL API.

The profilesIndividuals GraphQL API now returns only guest profile types. Other profile types that were previously included in the response will no longer be returned.

To fetch the Profiles of Company, Travel Agent, Source use the Profile Accounts GraphQL API.

Reporting & Analytics 26.4

The profilesIndividuals GraphQL API will no longer return non-Individual profile types. Any consumer logic that expects Travel Agent, Company, or Source profiles must be updated.

Use the profileAccounts GraphQL API to retrieve data for Travel Agent, Company, and Source profile types.

Prepare Now:

Review any integrations or applications that consume the profilesIndividuals GraphQL API and ensure they expect only Individual (D) profile types in the response.

Once the Change is Live:

Validate that integrations that need data for Travel Agent, Company, and Source profile types use profileAccounts GraphQL API.

Support for limit and offset pagination has been removed from GraphQL Data API export requests. Export requests using these parameters will now be rejected. Customers must migrate to the supported streaming export behavior.

Data APIs have been updated to remove support for limit and offset pagination on export requests. The API specification has been aligned with this behavior, and any export request that includes limit, offset, or both will be rejected with a clear client-facing error message. Streaming export is now the only supported approach for exporting large data sets. Existing GraphQL Data API functionality outside of export pagination is unchanged.

Streaming export behavior in a GraphQL Data API means returning a large export progressively instead of waiting for the entire dataset to be generated. In the Data API, streaming is commonly implemented through incremental delivery (for example, @stream).

Reporting & Analytics 26.4

Data API calls that use limit and/or offset parameters in GraphQL Data API export requests will no longer function as before. These requests will be rejected, and clients must update their export workflows to use the supported streaming export mechanism. GraphQL Data API operations unrelated to export pagination are not affected.

Prepare Now:

Review any Data API call that uses limit or offset in GraphQL Data API export requests. Plan to update it to use the supported streaming export mechanism and validate the changes before upgrading.

Before the next release, review and update your GraphQL Data API export queries to use the @stream directive. Remove any limit or offset parameters previously used for pagination. See the below example for the required query changes: 

query profilesAccounts($input:
  ProfilesAccountsQueryArgumentsType!) {
profilesAccounts(input: $input) @stream {

Once the Change is Live:

Verify that all GraphQL Data API export requests use the supported streaming export mechanism and confirm that no requests include the deprecated limit or offset parameters.

This is an update to the major change announced in August 2026 for the Streaming API. In addition to the previously announced change, business data elements where both the old and new value are null will also no longer be included in payloads from the streaming API.

Unlike the polling API, the streaming API no longer includes a business data element if the oldValue is null and the newValue is null.

OHIP 26.2

Integrations expecting business data elements to be in the payload even with null values will find them missing.

This change does not affect the polling API.

Prepare Now:

Once the Change is Live:

  • Ensure your integration is not expecting to business data elements whose value is null in the detail array.

This is an update to the major change announced in February 2026 announcing the deprecation of may GET APIs. Most of the affected operations will now be sunsetted (no longer available) from OPERA 27.3.

See the original announcement for the change.

OPERA 27.3

See the original announcement for the impact.

Prepare Now:

Once the Change is Live: