Set up OHIP authentication and required headers ahead of an OPERA Cloud integration

domain: docs.oracle.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Register your integration in the OHIP Developer Portal to receive an x-app-key and a partner/environment-specific API gateway URL.
  2. Implement OAuth2 client-credentials token acquisition against OPERA Cloud's Identity/OCIM service using that gateway.
  3. Attach the x-app-key header (app identity) and x-hotelid header (target property) to every subsequent API call.
  4. If currently using the legacy "Resource Owner" (SSD) auth scheme, follow Oracle's Client Credentials migration guide to move to the current model.
  5. Track OPERA Cloud's quarterly Release Readiness Guides since OHIP doesn't publish one standalone API version number — behavior can shift per release.

Known gotchas

Related routes

Subscribe to real-time OPERA Cloud business events using OHIP Streaming API with WebSocket
docs.oracle.com/hospitality/integration-platform · 6 steps · unrated
Read and write hotel reservations through Oracle OPERA Cloud REST APIs via OHIP
docs.oracle.com/hospitality/integration-platform · 6 steps · unrated
Create and manage group block reservations and rooming lists via the OPERA Cloud Block/Reservation API through OHIP
docs.oracle.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans