Consume OPERA Cloud outbound/async Distribution notification APIs (Outbound Lookup and Outbound Content Notification) for near-real-time ARI and lifecycle updates
domain: docs.oracle.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Complete channel/partner onboarding so the property enables outbound notifications for the integration
Stand up an HTTPS endpoint able to receive Distribution Outbound Content Notification calls
Handle lifecycle messages (channel onboarding, hotel/room-type/rate-plan mapping) separately from operational updates (rate amounts, inventory by day, restrictions)
Return the correct synchronous HTTP status and error payload defined in the OHIP spec when a message cannot be processed
Use the Distribution Outbound Lookup API to reconcile and recover any notifications that were missed or failed
Known gotchas
These are asynchronous, at-least-once, webhook-style deliveries with retry and circuit-breaker behavior on Oracle's side, so the receiving endpoint must be idempotent
Updates must be applied honoring the property's effective dates and time zone, not the time the notification arrived
This outbound/async mechanism is separate from the previously covered OHIP Streaming (WebSocket) business-events API; they use different subscription and delivery models
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?