PMS Connection
Connect your Property Management System (PMS) to AVA Streamliner to sync reservations automatically.
Opera Cloud connections need enterpriseId in both OCIM and SSD modes. Ask Oracle for it first.
If you are using AVA PMS, you can skip this page and continue with the setup checklist.
In Settings → Essentials → PMS Integration, the AVA card shows first under Select PMS Provider. This is normal. Select your PMS to connect it.
Each PMS card shows the fields that apply to that provider. Some values arrive through OAuth or deployment configuration instead of manual entry.
Provider-specific fields
The settings page and Assisted Check-In Setup use the same provider field rules. After you select a card, AVA shows only the fields for that PMS.
| Provider | Enter or confirm | Important behavior |
|---|---|---|
| Cloudbeds | Connect your Cloudbeds account | OAuth supplies the Property ID and API key. |
| Opera | OHIP connection fields | OHIP Enterprise ID is required in OCIM and SSD. SSD also needs username and password. |
| Mews | Access Token | Client Token and Client ID usually come from AVA deployment settings. |
| Furama iPMS | Base URL, Organisation Unit, User Code, and API Key | Control Unit and Business User Code are optional. |
| eZee | Hotel Code and Auth Code | Base URL and Use Demo Environment are optional. |
| AVA | Nothing | AVA uses your property settings. |
Keep saved credentials safe
AVA masks saved secret values instead of displaying them again.
-
Leave a masked value unchanged when you save other settings.
-
Select Edit Secret or Edit Token to replace a saved credential.
-
For an Opera OHIP Password, leave the field blank to keep the existing password.
✓ AVA keeps the stored credential unless you enter a replacement.
When you save active pre-arrival settings, AVA checks the PMS webhook subscription in the background. If a Cloudbeds webhook is missing or broken, saving again repairs it. Mews webhook subscriptions stay managed at the integration level.
If Cloudbeds rejects the webhook credentials, AVA stops retrying that repair. Reconnect Cloudbeds, then save your active pre-arrival settings again.
After a successful PMS credential or provider change, AVA refreshes the connection across all active servers. You do not need to wait for an automatic cache timeout or restart your browser. The next PMS operation uses the new settings, even if an older refresh was still running.
Supported Systems
| PMS | Sync Type | Setup Time |
|---|---|---|
| Cloudbeds | Real-time | 10 minutes |
| Opera Cloud | Real-time | 15 minutes |
| Mews | Real-time | 10 minutes |
| eZee | Real-time | 2 minutes |
| Furama iPMS | Real-time | 10 minutes |
Before You Start
You'll need:
- Admin access to your PMS
- Integration access approved in your PMS provider
- Admin access to AVA Streamliner
-
enterpriseIdfrom Oracle for your Opera property
Time Required: 10-15 minutes
Cloudbeds Connection
Step 1: Connect in AVA
- Go to Settings → Essentials
- Find the PMS Integration section
- Under Select PMS Provider, click Cloudbeds
- Click Connect Cloudbeds Account
- Complete the Cloudbeds authorization flow
- Return to AVA and confirm the status shows Cloudbeds Account Linked
Step 2: Verify Connection
- Wait 2-3 minutes for sync
- Go to Operations View
- Check that bookings appear
✅ Success: You see today's reservations from Cloudbeds.
Opera Cloud Connection
Step 1: Request OHIP Access
- Contact your Oracle OPERA representative
- Request OHIP credentials for AVA integration
- You'll receive:
- OHIP Host Name
- Application Key
- Hotel ID
- Identity Management mode (OCIM or SSD)
- Client ID
- Client Secret
enterpriseIdfor either OCIM or SSD- Username and Password if you use SSD
Step 2: Connect in AVA
- Go to Settings → Essentials
- Find the PMS Integration section
- Under Select PMS Provider, click Opera
- Enter your OHIP credentials
- Include
enterpriseIdfor either identity mode
- Include
- Click Save
- Confirm status shows Opera Integration Configured
Mews Connection
Step 1: Get Mews Credentials
- Log in to Mews Commander
- Go to Settings → Integrations
- Find Vouch AVA in the marketplace
- Copy the Access Token
If you return later and the field looks masked, keep it and save again.
Step 2: Connect in AVA
- Go to Settings → Essentials
- Find the PMS Integration section
- Under Select PMS Provider, click Mews
- Enter the Access Token
- Click Connect
eZee Connection
Step 1: Get Your eZee Credentials
- Request your Hotel Code and Auth Code from eZee support
- Note any Base URL if your property uses a custom endpoint
Step 2: Connect in AVA
- Go to Settings → Essentials
- Find the PMS Integration section
- Under Select PMS Provider, click eZee
- Enter:
- Hotel Code
- Auth Code
- Base URL (optional)
- Confirm Use Demo Environment is OFF for live operations
- Click Save
✅ Success: Status updates to "Connected."
Need more detail? See Connect eZee PMS.
Furama iPMS Connection
Furama iPMS uses property credentials supplied by your Furama contact.
-
Go to Settings → Essentials.
-
Find PMS Integration.
-
Under Select PMS Provider, click Furama iPMS.
-
Enter the required connection details.
-
Click Save PMS Settings.
✓ The status changes to Furama Integration Configured.
Need field details? See Connect Furama iPMS.
Troubleshooting
Connection Failed
What you see: Error message when clicking Connect
Try this:
- Double-check your credentials
- Make sure Oracle provided
enterpriseIdfor your identity mode - Make sure you have API permissions in your PMS
- Check your internet connection
- Try again in a few minutes
Reservations Not Syncing
What you see: No reservations appear after connecting
Try this:
- Click Refresh in Operations View
- Wait 5 minutes for initial sync
- Check that reservations exist in your PMS
- Verify the connection status in Settings
Sync Delays
What you see: Reservations are delayed
Note: Initial sync can take a few minutes depending on PMS and API load.
Still Stuck?
Contact success@vouch-technologies.com if:
- ❌ Required fields keep returning after you complete them
- ❌ Your PMS remains disconnected after saving
- ❌ Reservations do not appear after the first sync window