Oracle Opera Cloud

This documentation for the Oracle Opera Cloud integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Oracle Opera Cloud, visit our connection instructions.

Version

This integration utilizes the Oracle Opera Cloud Oracle Hospitality API v1.

Base URL

The base URL used for all Oracle Opera Cloud API endpoints contains the Tenant, Region identifier (e.g. "us-ashburn-1"), and Domain environment suffix (ocs.oc.com for production and ocs.oc-test.com for test):

https://tenant.hospitality-api.region.domain_env_suffix"

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	/crm/v1/profiles	Validate credentials
POST	/oauth/v1/tokens	Get OAuth Token for Client Credentials environments

---

Authentication & Authorization

The DataGrail Oracle Opera Cloud integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to Oracle Opera Cloud API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

---

Limits

Limits in Oracle Opera Cloud are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's Oracle Opera Cloud integration provides Synchronous Access capabilities for the following supported identifier categories: Email and Phone Number.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search profiles using configured identifiers.
2. For all collected Profiles:
   • Fetch attachments.
   • Fetch e-certificates.
   • Fetch commission accounts.
   • Fetch cashiering details.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/crm/v1/ecertificates	Fetch profiles e-certificates
GET	/crm/v1/profiles	Search profiles
GET	/crm/v1/profiles/profile_id/attachments	Fetch profiles attachments
GET	/crm/v1/profiles/profile_id/cashieringDetails	Fetch profiles cashiering details
GET	/crm/v1/profiles/profile_id/commissionAccount	Fetch commission accounts of profiles

---

Deletion

DataGrail's Oracle Opera Cloud integration provides Synchronous Deletion capabilities for the following supported identifier categories: Email and Phone Number.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

Delete profile.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
DEL	/crm/v1/profiles/profile_id"	Delete profile

---