integrations@takumo.jp). Registers the environment in the OHIP portal, generates the OAuth credentials, and finishes the setup in Takumo.ℹ NOTE Oracle onboarding happens in two stages. The hotel only enters three identifiers up front. The OAuth credentials and gateway/property details only exist AFTER the hotel approves the connection, so Technical Support add those afterwards |
An active OPERA Cloud Foundations license.
The following Oracle identifiers ready:
Enterprise ID
Chain Code
Region (the hotel's Oracle data-center region)
A Takumo Pro account with Administrator role.
Access to the OHIP Developer Portal (Partner) with a certified Production app.
The shared Oracle application key configured in Takumo (a one-time setup; ask the dev/DevOps team if unsure).
Go to PMS Configuration => Add New PMS.
Select Oracle as the provider.
Fill in the three fields and click Submit:
Enterprise ID: The hotel's Oracle Enterprise ID.
Chain Code: Identifies the hotel chain within Oracle.
Region: The hotel's Oracle region. Choose from: Ashburn, Frankfurt, Sydney, Melbourne, Hyderabad, Singapore, Mumbai.
On submit:
The Oracle configuration is created with status Pending.
A notification email is sent to integrations@takumo.jp with the Hotel Name, submitter, Enterprise ID, Chain Code, and Region.
The new entry appears in the PMS list with status Pending.
When the notification email arrives:
In the OHIP Developer Portal, open the Environments tab.
Click Add Environment.
Enter the Enterprise ID, Chain Code, and Region from the email.
Select Production and submit. The request shows as Pending in the portal.
This step happens entirely OUTSIDE Takumo. Oracle emails the hotel's account holder.
The hotel's IT administrator logs into the Oracle Customer Developer Portal.
Navigate to Environments => Partner Connections.
Locate the pending request from Takumo.
Select the specific properties (hotels) Takumo may access, and click Approve.
Expected turnaround for the Oracle email is within 24 hours of submission.
Once approved, the environment status in the OHIP portal changes to Active.
Open the environment and click Generate OAuth Credentials.
Oracle outputs a Client ID and a Client Secret.
Enter these details into the Oracle configuration in Takumo:
Gateway URL (the region-specific OHIP API base URL)
Client ID
Client Secret
Hotel ID (the property granted during approval)
Takumo verifies the connection with Oracle. If it succeeds, the status becomes Connected and the integration goes live. If it fails, the status stays Pending so it can be corrected and retried.
⚠ IMPORTANT The Client Secret is shown only once. Store it securely |
The Hotel Admin sees the configuration as Connected in the PMS list.
Guest search and other PMS-backed features now work for that hotel.
Pending: Submitted by the hotel; awaiting Oracle approval and the credential setup. Not active yet.
Connected: Credentials configured and the connection verified - live.
⚠ IMPORTANT [No Configuration] -- submit --> [Pending] -- finish setup (verified) --> [Connected] |