Supported PMS Systems
Table of Contents
API's PMS Setup & API Info Oracle Phase 1: Information Gathering Email Template for Information Gathering 1: Initial Request (Start of Project) Phase 2: Portal Setup (Our Side) Phase 3: Hotel Approval (Crucial Step) Email Template Approval Instructions (Send after Phase 2) Phase 4: PMS Configuration (Hotel Side) Phase 5: PBX Configuration & Testing Troubleshooting & Extra Help Stay-N-Touch UC Hospitality Setup: Infor Hotel Key Cloud Beds Mews PMS API Matrix Known Working PMS Systems PMS System by Hospitality Brand PMS Call AccountingThe heart of a successful hotel lies in its technology. At the center of that ecosystem is the Property Management System (PMS). UC Hospitality bridges the gap between the front desk and your hosted phone system using proprietary interface technology. By synchronizing data in real time, we ensure your operations run leaner, and the hotel staff stays focused on the guest, not the hardware.
API's
API integrations provide a direct cloud-to-cloud PMS connection for UC Hospitality and do not require a Serial Box.
These APIs are currently not available for UC Hospitality.
- Oracle OHIP
- Jazzware
- SkyTouch
- Stay-N-Touch (Beta)
- Hotel Key (Beta)
- Cloudbeds (Beta)
- Mews (Beta)
PMS Setup & API Info
UC Hospitality can connect to PMS API systems. Unlike all other PMS systems, this is a direct hosted connection (similar to TCP/IP) and does not require an on-site serial box.
Oracle
For Hyatt hotels, the only thing we need to start with is the hotel ID (property code) from the Hotel. Please contact our support team to have us add this to your system.
Oracle Setup Instructions & Email Templates (updated 12/15/2025)
Overview: This guide outlines the setup process for connecting our PBX to Oracle OPERA Cloud using the newer OHIP OCIM (Client Credentials) API (not the older SSD style connection).
Phase 1: Information Gathering
Before starting any setup, you must obtain specific identifiers from the hotel. Without these, we cannot initiate the connection.
Enterprise ID: (e.g., ENT0000123)
Chain/Tenant Code: (e.g., CHA or HTL01)
Region: (e.g., us-ashburn-1, eu-frankfurt-1)
Email Template for Information Gathering 1: Initial Request (Start of Project)
Subject: Action Required: Setup Information for PBX Integration (Oracle OPERA Cloud)
Dear [Hotel Contact],
To connect your PBX system to OPERA Cloud, we utilize the Oracle Hospitality Integration Platform (OHIP). Please provide the following details so we can initiate the connection request:
Enterprise ID: (Found in your OHIP Portal under Environments)
Chain / Tenant Code:
Hotel ID: (The specific property code in OPERA)
Region: (e.g., US Ashburn, Frankfurt, etc.)
Once we receive this, we will send a connection request to your Oracle environment.
Phase 2: Portal Setup (Our Side)
Provide the details gathered to our support team so that we can add the environment.
- This will trigger an email to the Hotel's Chain Admin.
Phase 3: Hotel Approval (Crucial Step)
The hotel often misses this step. They must approve our specific request in their portal.
Action Required: Send "Email Template #2" (below) to guide them.
Once approved, the status in our portal changes to Active, and we can generate the Client ID and Client Secret.
Email Template Approval Instructions (Send after Phase 2)
Subject: Action Required: Please Approve PBX Partner Connection in OHIP
Dear [Hotel Contact],
We have initiated the connection request from our side. You should have received an automated email from Oracle indicating a pending partner connection.
To finalize the connection, please follow these steps:
- Log in to your Oracle Hospitality Developer Portal (OHIP).
- Navigate to Environments (Top Menu).
- Click on Partner Connections.
- Locate [Your Company Name] in the list (Status will be "Pending").
- Select the checkbox for your property/hotel.
- Click Approve.
In addition, please verify the following settings in OPERA Cloud Administration:
- Create External System
- Go to Administration > Interfaces > External Systems.
- Create a New External System (Code: PHONESUITE).
- Ensure the "Active" checkbox is selected.
- Configure Business Events (Required for Room Status Updates)
- Go to Administration > Interfaces > Business Events > External Systems.
- Select the External System created above (PHONESUITE).
- Add the following Modules and Business Events:
- Reservation: Check In, Check Out, Create Wakeup Call, Delete Wakeup Call, Update Wakeup Call.
- Housekeeping: Update Room Status.
- Cashiering: New Posting.
- Cashiering & Transactions (Required for Call Accounting)
- Please provide the Transaction Code (Trx Code) we should use for posting call charges.
- Ensure the Cashier ID used for the interface is valid and has "Posting" privileges.
Once approved, please reply to this email so we can complete the setup on our end.
Thank you,
Phase 4: PMS Configuration (Hotel Side)
The API connection alone does not enable features. The hotel must configure OPERA Cloud to "talk" to us.
- External System: They must create a system record (e.g., Code: PHONESUITE).
-
Business Events: They must subscribe that the External System to events:
- Reservation: Check In, Check Out, Create Wakeup Call, Delete Wakeup Call, Update Wakeup Call
- Housekeeping: Update Room Status
- Cashiering: New Posting.
- Transaction Codes: For posting calls/minibar, they must provide a valid Transaction Code (Trx Code) and ensure the Cashier ID is open (i.e. 4001)
Phase 5: PBX Configuration & Testing
- Input the following into the PBX Interface:
- Gateway URL: (From the Oracle portal, normally https://hyattcu1.hospitality-api.us-ashburn-1.ocs.oraclecloud.com)
- Client ID & Secret: (Generated in the Oracle portal after approval)
- App Key: (From the Oracle portal App Registration)
- Hotel ID: (Provided by hotel)
- Transaction Code: (Provided by hotel)
- Scope: (Normally:
- Test: Wait 10 minutes to see the check-in events. Have the hotel run a test check-in as needed.
Troubleshooting & Extra Help
If the API shows as online in UC Hospitality but we are not receiving any events, here is what Oracle suggested.
The issue was related to the configuration of the external system and to the business events not being properly set up for this OHIP connection. I have attached the user guide outlining how to configure both within Opera Cloud.
As a first step, the property will need to set up the external system. Once that is completed, they can proceed with configuring the necessary business events.
OHIP user guide:
External systems
Business events
Stay-N-Touch
To set up a new interface:
The hotel should drop an email to onboarding@stayntouch.com authorizing you to access their data in production. Mention both UC Hospitality, Phonesuite and ConnectWare in the email to ensure they know we are an approved vendor.
Stay-N-Touch onboarding team will configure any webhooks if used. We operate on 3 PMS instances. Below are the API endpoints. Our onboarding team will provide guidance on which endpoints to utilize. The team will also specify the hotel_id(s) and will provide API credentials.
auth.stayntouch.com and api.stayntouch.com/connect
auth.us.stayntouch.com and api.us.stayntouch.com/connect
auth.eu.stayntouch.com and api.eu.stayntouch.com/connect
As Stay-N-Touch is a chain-level application, the access is per chain, so adding new hotels within a chain does not necessitate a new set of credentials. The token expires every 30 days.
UC Hospitality Setup:
Client ID: [Provided by Stay-N-Touch]
Client Secret: [Provided by Stay-N-Touch]
Authentication Endpoint: https://auth.us.stayntouch.com/oauth/token
API Endpoint: https://api.us.stayntouch.com/connect
Hotel ID: [Three-digit code]
Charge Code ID: [Five-digit code]
Infor
Infor uses a hosted Voiceware system as a "Serial Box" to connect via TCP/IP using the FOSSI PMS interface.
The Setup will use a hosted Voiceware system as a Serial Box (an actual Serial Box can't be used). The system needs to be updated with changes to the FOSSI interface. Once done, the system can be connected to Infor via TCP/IP and to ConnectWare via the standard MQTT process.
Please contact support to have this set up at least 4 days before the cut-over.
Hotel Key
This PMS uses a simple API that requires the following information from the Hotel Key / the hotel.
Username (i.e. user_phonesuite)
Password
Hotel Key URL (i.e. https://00.us-east-1.hkdemo.hotelkeyapp.com)
Property ID (long password-like string)
Property Code (i.e. HTNGX)
Provide this information to support so that we can set up a Web Hook URL.
Note that as of November 3, 2025, room moves work only once; if the guest is moved a second time, they will not move in UC Hospitality.
Cloud Beds
To start, request an API key from Cloud Beds. Note: The API key must have the following permissions: Item (Read & Write), Guest (Read), Room (Read), Reservation (Read), Housekeeping (Read & Write). Also, request an Item ID, the identifier of the item to be used when creating a custom post charge for a billable call.
On the hotel page, click PMS setup, then Setup PMS. Select CloudBeds, enter the API Key and Item ID, then click Save. After a few minutes, you should see new events on the PMS logs page.
To disconnect the API, simply change the status to "Disabled". To disconnect from the CloudBeds side, see this article. For assistance, please contact support.
Mews
This API requires:
- Client (i.e. PARIS Hotel)
- Client Token (Long password string)
- Access Token (Another password-looking string)
- Billable Call Product ID (i.e. 67cec5e8-436f-4d10-…)
You should be able to request these items from the hotel. Once provided, simply add them to UC Hospitality, and the interface should show them as online.
PMS API Matrix
|
Oracle |
Stay-N-Touch |
Jazzware |
SkyTouch |
Hotel Key |
Mews |
Cloudbeds |
|---|---|---|---|---|---|---|---|
Check in |
|
|
|
|
|
|
|
Check out |
|
|
|
|
|
|
|
Name update |
|
|
|
|
|
|
|
Room move |
|
|
|
|
|
|
|
Room calling restrictions |
|
|
|
|
|
|
|
Room status code update (from PBX to PMS) |
|
|
|
|
|
|
|
Billable call (from PBX to PMS) |
|
|
|
|
|
|
|
Group code |
|
|
|
|
|
|
|
VIP status / code |
|
|
|
|
|
|
|
Wakeup call setup |
|
|
|
|
|
|
|
Wakeup call cancel |
|
|
|
|
|
|
|
Wakeup call result (from PBX to PMS) |
|
|
|
|
|
|
|
Voicemail message count (from PBX to PMS) |
|
|
|
|
|
|
|
Drop in voicemail message upon check in |
|
|
|
|
|
|
|
DND on / off |
|
|
|
|
|
|
|
Message waiting lamp on / off |
|
|
|
|
|
|
|
Set / Clear DID number |
|
|
|
|
|
|
|
Guest language code |
|
|
|
|
|
|
|
Credit limit |
|
|
|
|
|
|
|
Known Working PMS Systems
PMS System by Hospitality Brand
| Hospitality Brand | PMS |
| Hyatt | Opera / Micro |
| Hilton |
OnQ (PEP replacement for OnQ) Hilton FIAS (Approved September 2025 requires the latest Psip-PMS Version) |
| Marriot | Opera |
| IHG | Opera |
PMS
The following PMS platforms integrate with UC Hospitality via Serial Box, FIAS, or approved middleware configurations.
| PMS Brand | Notes (if applicable) |
| Anand Systems | use the FIAS interface |
| Atrio | via Comtrol |
| Autoclerk | |
| Brilliant | |
| Choice Advantage | |
| COMTROL | |
| FOSSE | |
| Galaxy | |
| Hilton FIAS | (Approved September 2025 requires latest Psip-PMS version) |
| HSS/Cendant | |
| Infor HMS (vis FIAS TCP/IP) | Part Number: HMS(-S)-EAI-L066D PSTE-TMS – TMS interface for HM |
| InnSoft | |
| InnQuest | |
| Maestro | |
| MSI | |
| Nova Plus | Use Default2 settings 1200/ 8 / N / 1 |
| ONQ | |
| Opera |
|
| Opera FIAS | |
| PEP | (Approved September 2025 requires latest Psip-PMS version |
| Remco | |
| RemCo Nite Vision | |
| RDP Win Interface Monitor | V 5.3.002.05 |
| RoomMaster | |
| SkyTalk | |
| SkyTouch | |
| SoftHotel | |
| Springer-Miller |
SMS
|
| Visual Matrix | |
| WebRezPro |
Call Accounting
| Brand | Notes (if applicable) |
| Anand Systems | use the FIAS interface |
| Autoclerk | |
| Choice Advantage | |
| FOSSE | |
| Genesis | |
| HOBIS | |
| InnQuest | |
| Opera | |
| Remco RAW | |
| SkyTouch | |
| Visual Matrix | |
| WebRezPro |