PMS Integrations

The PMS Integrations page connects your WAVER device to a supported Property Management System. Once connected, WAVER can receive reservation and guest updates and automatically create or update guest voucher credentials. 

This allows hotel guests to access the network using information associated with their reservation, while voucher availability and expiration can follow the guest's stay. PMS integrations are optional WAVER+ services and require an active subscription that includes PMS, or an eligible WAVER+ trial.

To access this page, navigate to: Integrations > PMS

Important: PMS integrations may allow the device to receive reservation, guest, and access data from supported Property Management Systems. The administrator is responsible for authorizing the connection and ensuring that the data is processed in accordance with the organization's privacy, security, and regulatory requirements.

How PMS voucher automation works

After a PMS provider is connected, reservation and access-related updates are sent to WAVER. The device uses the configured reservation fields to generate guest voucher credentials automatically.

Depending on the provider and available reservation information, WAVER can:

• Create voucher credentials for new reservations.

• Update existing vouchers when reservation or guest information changes.

• Use details such as the guest name, email address, room number, or reservation ID as credentials.

• Align voucher access with the reservation's check-in and check-out period.

• Apply optional traffic quotas to generated vouchers.

WAVER currently supports different PMS connection methods:

• Cloudbeds: Connects through the Cloudbeds account-authorization process.

• Hotelizer: Sends reservation events to a device-specific API endpoint using an integration key.

Common Voucher Generation settings

PMS Systems provide the same core voucher-generation controls. The selected settings are stored separately for each integration.

Default Check-in Time
Defines the default time at which a generated voucher becomes valid when an exact check-in time is not supplied by the PMS.

Default Check-out Time
Defines the default time at which a generated voucher expires when an exact check-out time is not supplied by the PMS.

Voucher Username
Select the reservation field used as the guest's voucher username. Available fields include:

• Reservation ID

• Guest first name

• Guest last name

• Guest email

• Room

Voucher Password
Select the reservation field used as the voucher password. The username and password must use different reservation fields.

Fallback Username and Password
The optional fallback fields define an alternative credential pair when the primary values cannot be used. Leave these fields set to Disabled if fallback credentials are not required.

For example, a property may use the room number and guest last name as the primary credentials, with the reservation ID and guest email address as the fallback pair.

Best practice: Avoid credential combinations that are too easy for other guests to guess. Select fields that are populated consistently in the property's reservation records.

Guest Traffic Quota

Choose how much traffic each generated voucher may use:

• Unlimited: No traffic quota is applied.

• Limited (Combined): Applies one total allowance, in megabytes, across download and upload traffic.

• Limited (Down/Up): Applies separate download and upload allowances, in megabytes.

When a limited mode is selected, enter the required allowance in the fields displayed below it.

Cloudbeds PMS

The Cloudbeds integration connects the WAVER device to a Cloudbeds property through the Cloudbeds authorization process. Once authorized, the device can receive the reservation information required for voucher generation and updates.

Requirements
Before connecting Cloudbeds, confirm that:

• The device has an active WAVER+ subscription that includes PMS, or an active eligible trial.

• Cloud Access is enabled on the WAVER device.

• The device can make outbound Internet connections.

• You have permission to authorize access to the required Cloudbeds property.

• The device timezone is configured correctly.

If Cloud Access is disabled, the Cloudbeds settings are shown as unavailable and the page provides a shortcut to the Cloud Access settings.

Connection status
The upper section of the Cloudbeds page displays:

• API Status: Shows whether the Cloudbeds integration is enabled, disabled, or unavailable.

• Integration: Shows whether the device is currently connected to Cloudbeds.

• Connected Since: Displays when the current connection was established.

• Cloudbeds Property: Displays the connected property name and Cloudbeds property ID.

• Device Timezone: Displays the timezone currently used by the WAVER device.

Connecting to Cloudbeds

1. Navigate to Integrations > PMS and select Cloudbeds.

2. Make sure Cloud Access is enabled.

3. Enable the Cloudbeds PMS switch.

4. Click Connect.

5. Complete the Cloudbeds authorization process in the window that opens.

6. Select or confirm the Cloudbeds property when prompted.

7. Return to the WAVER interface and reload the page.

8. Confirm that Integration is shown as Connected and verify the displayed property.

9. Configure the Voucher Generation settings and click Save.
   
   

If the authorization window is blocked by the browser, allow pop-ups for the WAVER interface and try again.

Managing the Cloudbeds integration

• Click Save to apply the Voucher Generation and traffic-quota settings.

• Click Reload to retrieve the current configuration. Unsaved changes are discarded.

• Use the Cloudbeds PMS switch to enable or disable the integration.

• Click Disconnect to remove the current Cloudbeds connection. The status changes to Not Connected, and the property and connection details are cleared from the page.

After changing the credential format, review newly generated vouchers to confirm that the selected Cloudbeds reservation fields are being received correctly.

Hotelizer PMS

The Hotelizer integration uses webhooks to send reservation events to the WAVER device. Each device provides a unique API Endpoint and Integration Key, which must be configured in Hotelizer.

Hotelizer does not require a separate account-authorization window. Hotelizer authenticates its webhook requests using the integration key.

Requirements
Before configuring Hotelizer, confirm that:

• The device has an active WAVER+ subscription that includes PMS, or an active eligible trial.

• Cloud Access is enabled on the WAVER device.

• You have access to the Hotelizer integration or webhook settings. (contact Hotelizer support)

• The device timezone is configured correctly.

If Cloud Access is disabled, the Hotelizer API status is shown as Unavailable and the configuration fields are disabled.

Hotelizer API information
The upper section of the Hotelizer page displays:

• API Status: Shows whether the Hotelizer integration is enabled, disabled, or unavailable.

• Device Timezone: Displays the timezone used when processing reservation dates and times.

• API Endpoint: The unique HTTPS address to which Hotelizer sends webhook events.

• Integration Key: The secret used to authenticate Hotelizer webhook requests.

Use the eye button to reveal or hide the Integration Key. When the key is visible, use the copy button to copy it to the clipboard.

Security: Treat the Integration Key like a password. Do not publish it, include it in screenshots, or share it with anyone who is not authorized to configure the Hotelizer integration.

Connecting Hotelizer

1. Navigate to Integrations > PMS and select Hotelizer.

2. Make sure Cloud Access is enabled.

3. Enable the Hotelizer PMS switch.

4. Copy the displayed API Endpoint.

5. Reveal and copy the Integration Key.

6. Open the integration or webhook configuration in Hotelizer.

7. Enter the WAVER API Endpoint and Integration Key in the corresponding Hotelizer settings.

8. Save the configuration in Hotelizer.

9. Return to WAVER, configure the Voucher Generation settings, and click Save.

10. Send or create a test reservation event and confirm that the expected voucher is generated.

Enter the endpoint exactly as displayed. It is assigned to this specific WAVER device and should not be reused for another device.

Regenerating the Integration Key
Use the regenerate button next to the Integration Key if the current key may have been exposed or needs to be replaced.

Regenerating the key immediately invalidates the previous one. Hotelizer webhook requests will be rejected until the new key is entered in the Hotelizer dashboard.

After generating a new key:

1. Copy the new Integration Key.

2. Replace the previous key in Hotelizer Dashboard.

3. Save the Hotelizer configuration.

4. Send a test event to confirm that communication has been restored.

Managing the Hotelizer integration

• Click Save to apply the Voucher Generation and traffic-quota settings.

• Click Reload to retrieve the current configuration. Unsaved changes are discarded.

• Use the Hotelizer PMS switch to enable or disable the API.

Disabling the integration prevents Hotelizer events from being processed until it is enabled again.

Important notes and best practices

• Cloud Access is required for PMS integrations.

• Confirm that the selected PMS property corresponds to the property served by the WAVER device.

• Incorrect timezone or check-in/check-out settings may cause vouchers to become active or expire at the wrong time.

• PMS data availability depends on the information supplied by the provider and the property's reservation records.

• Credential fields should be selected according to the data that the property collects consistently.

• Disconnecting or disabling an integration stops future PMS synchronization. Review existing vouchers separately if they must also be removed or disabled.

• Test the complete reservation-to-login workflow with a non-production reservation before enabling the integration for all guests.