How Weareplonet connects to Protel
Every Weareplonet module integrates with your Protel account via the official Protel API using your Protel Login. Nothing runs inside your PMS. This page lists the Protel API endpoints each module uses so your Protel administrator and IT security team can review scope before you subscribe.
Authentication
Weareplonet authenticates to your Protel installation using a scoped API token issued by your Protel administrator inside Protel. The token is granted per property, per scope (read or read-write per endpoint), and can be revoked at any time from the Protel user management. Weareplonet never sees or stores your Protel user password — only the API token, which is stored encrypted at rest and only ever transmitted over TLS 1.3.
If your Protel installation uses SSO (Azure AD, Okta, Google Workspace), the same token model applies; Weareplonet does not participate in the SSO flow because it is a machine-to-machine connection, not a user session.
Protel API endpoints used
Rates
Read and write rate codes, seasonal riders, restrictions (MinLOS, MaxLOS, CTA, CTD).
Used by: Rate Update Bridge, Corporate Ledger Manager, Group Enquiry Router
Reservations
Read reservations by arrival, departure, room, guest, market segment. Create group blocks. Modify rate overrides.
Used by: Arrivals Digest, Group Enquiry Router, OTA Reconciliation, Guest Wi-Fi Sign-On
Guests
Read guest profiles, folio notes, VIP flags, loyalty ties. Never written back — read-only.
Used by: Arrivals Digest, Guest Wi-Fi Sign-On
Folio
Post charges and payments to guest folios; read folio balances for reconciliation.
Used by: F&B POS Bridge, Nightly Trial Balance
Housekeeping
Read and write room states — Vacant Clean, Vacant Dirty, OOS, OOO — with a full state history.
Used by: Housekeeping Board
Reports
Read Protel nightly close output, cashier reports, city-ledger ageing, payment ledger.
Used by: Nightly Trial Balance, DATEV Bookkeeping Bridge, Data Warehouse Bridge
Rate limits and back-off
Every module respects the API rate limit configured on your Protel installation. When the limit is approached, requests are queued, retried with exponential back-off, and (for modules that support it) delivered in the next scheduled batch. If a scheduled module cannot complete inside the limit window, the Weareplonet dashboard raises an alert so you can decide whether to increase the limit or slow the module down.
Outbound connections and IP allow-listing
All Weareplonet outbound calls to your Protel installation originate from a fixed set of IP addresses in Frankfurt and Amsterdam. The list is published in the Weareplonet dashboard under Connection settings, so your network team can allow-list them at the firewall in front of your Protel installation.
Ready to connect?
Add a module, paste your Protel API token, and you are live in two minutes.