# Eagle Suites OPERA Cloud Public-Source Discovery First Pass

Date: 08/17/2026 03:08 PM CDT

## Scope

This was a first-pass public-source run based on the approved OPERA Cloud research prompt. It was not an exhaustive full-ingest of all Oracle Hospitality documentation. The goal was to verify the main source families, test the seed URLs, confirm authority levels, and surface any safety concerns before wider use.

Current Eagle Suites working scope is now set to:

- In scope: PMS, OHIP, and Reporting & Analytics
- Out of scope unless later approved: Payments and Distribution

## Direct answer

The public Oracle source network for OPERA Cloud is real, broad, and usable. The original prompt was not nefarious. The main safety tightening was justified because Oracle's own GitHub/Postman guidance includes real-world use of Postman environments, credentials, client secrets, app keys, and hotel identifiers. That is exactly the area where Eagle Suites should stay strict about not uploading internal materials or tenant data without explicit approval.

## Key findings

- The generic OPERA Cloud hub URL resolves to the broader Oracle Hospitality Hotels page rather than behaving like a precise versioned product book. For serious research, versioned/book URLs are better starting points than the generic hub.
- Oracle exposes a versioned OPERA Cloud books page for `26.3` with direct links to the User Guide, Security Guide, Compatibility Matrix, Network and Communications Guidelines, and Licensing Information.
- Oracle exposes a versioned OPERA Reporting and Analytics documentation hub that currently presents as `26.3`, with release readiness and prior-release navigation.
- Oracle exposes a versioned Oracle Hospitality Integration Platform documentation hub that currently presents as `26.2`, including Release Notes, User Guide, Security Guide, Implementation Guides, and Books.
- Oracle's public GitHub repository `oracle/hospitality-api-docs` is live and explicitly states that it stores REST API specifications and accompanying Postman collections for Oracle Hospitality APIs.
- Oracle's OHIP documentation includes public guidance for Business Events, API Search Engine, authentication, and GitHub/Postman collections.
- The Postman workspace is publicly reachable, but lightweight fetch output is thin. It is better treated as a secondary implementation aid than as a primary authority source.

## Source manifest snapshot

| Source family | URL | Result | Authority | Notes |
| --- | --- | --- | --- | --- |
| Oracle Hospitality hub | `https://docs.oracle.com/en/industries/hospitality/` | implied live via linked pages | High | Main public Oracle docs family |
| OPERA Cloud generic hub | `https://docs.oracle.com/en/industries/hospitality/opera-cloud/` | redirected to Hotels page | High | Useful discovery signal, weak precision |
| OPERA Cloud 26.3 books | `https://docs.oracle.com/en/industries/hospitality/opera-cloud/26.3/books.html` | live | High | Better starting point than generic hub |
| OPERA Cloud 26.3 User Guide | `https://docs.oracle.com/en/industries/hospitality/opera-cloud/26.3/ocsuh/index.html` | live | High | Versioned product guide |
| OPERA Reporting and Analytics hub | `https://docs.oracle.com/en/industries/hospitality/opera-reporting-analytics/index.html` | live | High | Shows `26.3` in fetched page title |
| Integration Platform hub | `https://docs.oracle.com/en/industries/hospitality/integration-platform/` | live | High | Shows `26.2` in fetched page title |
| OHIP Business Events | `https://docs.oracle.com/en/industries/hospitality/integration-platform/ohipu/c_business_events.htm` | live | High | Confirms polling + streaming model |
| OHIP API Search Engine | `https://docs.oracle.com/en/industries/hospitality/integration-platform/ohipu/c_api_search_engine.htm` | live | High | Shows lifecycle/category/module/workflow filters |
| OHIP Auth guidance | `https://docs.oracle.com/en/industries/hospitality/integration-platform/ohipu/c_authenticating_to_oracle_hospitality_property_apis_ocim.htm` | live | High | Mentions client ID, client secret, app key, enterprise ID |
| OHIP GitHub/Postman guidance | `https://docs.oracle.com/en/industries/hospitality/integration-platform/ohipu/c_github_postman_collections.htm` | live | High | Explicitly discusses Postman environments and credentials |
| Oracle Hospitality API GitHub repo | `https://github.com/oracle/hospitality-api-docs` | live | Medium-High | Official Oracle implementation resource, not sole contract authority |
| GitHub REST API specs folder | `https://github.com/oracle/hospitality-api-docs/tree/main/rest-api-specs` | live | Medium-High | Says OAS 2.0 specs live there |
| GitHub Postman collections folder | `https://github.com/oracle/hospitality-api-docs/tree/main/postman-collections` | live | Medium-High | Explicitly references Postman environments |
| Oracle Hospitality Postman workspace | `https://www.postman.com/hospitalityapis/workspace/oracle-hospitality-apis/overview` | live but thin fetch output | Medium | Reachable, but weaker source extraction |

## Product and interface map

- OPERA Cloud PMS: core hotel property-management surface
- OPERA Reporting and Analytics: reporting, analytics, dashboards, analysis, and related security/admin guidance
- Oracle Hospitality Integration Platform / OHIP: API discovery, app registration, authentication, streaming, polling, business events, and implementation guidance
- GitHub `hospitality-api-docs`: public REST specs and sample collections
- Postman workspace: public sample workflows and collections, secondary to official docs

## Safety observations

- The public Oracle docs are not asking for anything covert or abnormal.
- The highest-risk practical area is not hidden behavior. It is accidental operational sloppiness around Postman environments, credentials, or tenant data.
- Oracle's own docs and GitHub materials openly discuss environment variables, client secrets, app keys, usernames/passwords, and hotel IDs for API calling.
- That makes the following guardrail mandatory for Eagle Suites use:
  - never upload internal Eagle Suites documents, screenshots, configs, exports, secrets, or tenant data into third-party workspaces or sample tooling without explicit approval

## Validated claims from source

- Oracle Hospitality Integration Platform documents two business-event consumption methods, polling and streaming, and says Oracle recommends streaming because polling has many limitations.
  - Source: `https://docs.oracle.com/en/industries/hospitality/integration-platform/ohipu/c_business_events.htm`
- Oracle's API Search Engine documentation says users can filter by module, workflow, lifecycle, method, category, and related attributes, and that `V1` APIs are production-ready and backward compatible while deprecated APIs should be exited.
  - Source: `https://docs.oracle.com/en/industries/hospitality/integration-platform/ohipu/c_api_search_engine.htm`
- Oracle's authentication guidance states that calling Oracle Hospitality APIs may require OAuth Client ID and Client Secret, Application Key, Scope, and Enterprise ID, with tokens sent through the gateway URL shown in the Developer Portal.
  - Source: `https://docs.oracle.com/en/industries/hospitality/integration-platform/ohipu/c_authenticating_to_oracle_hospitality_property_apis_ocim.htm`
- Oracle's GitHub/Postman guidance explicitly says the Postman environment contains variables such as hostname, username/password for some environments, client ID, client secret, application key, and hotel ID.
  - Source: `https://docs.oracle.com/en/industries/hospitality/integration-platform/ohipu/c_github_postman_collections.htm`

## Known gaps from this first pass

- This run did not crawl every OPERA Cloud book, release note, or module page.
- This run did not enumerate every API operation or schema from the GitHub specs.
- This run did not verify whether all referenced Oracle docs are current for Eagle Suites' purchased modules or tenant entitlements.
- This run did not ingest customer-specific Oracle training, sandbox setup, or implementation documents.
- The Postman workspace itself is public, but fetch extraction is thin; GitHub plus docs.oracle.com are better anchors for automated citation work.

## What Eagle Suites must confirm locally

- Actual OPERA Cloud release/version in use or planned for pilot
- Enabled modules and entitlements
- Identity/authentication pattern in use
- Whether OXI or OWS are actually needed inside the broader PMS + OHIP + R&A decision
- Approved internal customer documents that may be added as customer-only sources
- Rules for sandbox vs production handling, especially for credentials and sample tooling

## Recommendation

- Use the safer approved Claude prompt file as the starting prompt:
  - `/Users/bobeagle/.openclaw/workspace/shared/reports/eagle-suites-opera-cloud-approved-claude-prompt-2026-08-17.md`
- Treat Oracle docs as primary authority.
- Treat GitHub and Postman as implementation aids only.
- Keep a hard internal rule that no Eagle Suites secrets, screenshots, configs, exports, or tenant data go into third-party workspaces without explicit approval.
- If you want the next step, run a second-pass ingestion focused on:
  - OPERA Cloud 26.3 books
  - OHIP API/auth/business-events/streaming
  - Reporting and Analytics
  - release-readiness and deprecations
  - exclude Payments and Distribution unless Eagle explicitly reopens those lanes

## Run status

- What was found: live official Oracle docs, versioned product books, OHIP integration guidance, Oracle GitHub API specs repo, and public Postman references
- What changed: a safer approved prompt was created with stronger anti-upload and anti-sprawl guardrails
- What could not be fully accessed: rich extraction from the Postman workspace itself was limited
- Authoritative sources: `docs.oracle.com` first, then Oracle GitHub implementation materials, then Oracle public Postman materials
- Customer confirmations still needed: actual Eagle Suites tenant/version/module/auth scope