Create, search, and update guest, company, and travel agent profiles via the OPERA Cloud Profiles (CRM) API through OHIP
domain: docs.oracle.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to OHIP and confirm the profiles/CRM module is enabled for the target property
Search existing profiles by name, membership number, or other identifiers before creating a new one to avoid duplicates
Select the correct profile type (Guest, Company, Travel Agent, Source, Group, or Contact) since payload fields differ by type
Create or update the profile with address, contact, membership, and preference data
Link the profile to a reservation or block so downstream folio and correspondence use it
Known gotchas
Profile type is not interchangeable after creation in OPERA Cloud, so picking the wrong type (e.g. Contact vs Guest) requires a new profile rather than a simple field edit
Duplicate-profile detection depends on matching logic configured per property; a search miss does not guarantee a profile does not already exist
CRM/profile endpoints are covered by the same OHIP entitlement and rate limits as other property APIs, so high-volume profile sync should be throttled and paginated
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?