Black Friday
Skip to documentation content

Security & Privacy

Protect iCal sources and room export links

Pro iCal import URLs and room export links can contain bearer credentials. Treat a complete feed URL as a secret even when it has no visible password; source labels and masked host information are safer diagnostic evidence.

Pro iCal import URLs and room export links can contain bearer credentials. Treat a complete feed URL as a secret even when it has no visible password; source labels and masked host information are safer diagnostic evidence.

Protect imported sources

Add or edit sources only through the authorized room OTA/iCal interface. The current source service stores URLs using authenticated encryption and installation-keyed fingerprints. Its safe admin model masks the URL instead of exposing ciphertext, complete paths or query tokens.

Use trusted provider feeds and preserve the fetcher’s URL/network restrictions. Do not weaken SSRF, TLS or redirect validation to make an unsupported local/private endpoint work. Keep raw calendar bodies and real guest information out of screenshots and support bundles.

A saved source URL is not proof of a successful import. Check source status, last successful sync, next due time and the bounded error class. Failed fetches must remain visible; do not delete previously known external blocks simply because a provider is temporarily unavailable.

Handle export tokens

A room-type export URL authorizes that feed, not administration or access to every booking. The current token flow returns a new URL once; a later admin visit cannot recover its plaintext and may require rotation. Store it privately when copying it into the intended OTA.

If the link is exposed, use the supported regenerate/rotate action. The old token then stops authorizing future fetches. Update every legitimate consumer, verify the new feed and monitor errors. Rotation cannot erase a calendar copy already downloaded or control how quickly an OTA polls again.

Backup, restore and license boundaries

Encrypted source storage depends on the installation’s protected key context. An arbitrary database copy or salt/key change is not a guarantee those URLs remain usable; plan secure credential re-entry/recovery rather than printing stored secrets. Protect encrypted backups as sensitive data.

Pro entitlement governs Pro source/sync operations. Core continues to enforce stored external inventory blocks when Pro is inactive or unavailable. Do not bypass entitlement or remove blocks to restore website sales without source reconciliation.

Verify safely

Test token rotation and denied old-token fetches using synthetic calendars in an isolated environment. Record only the room/source label, redacted endpoint pattern, timestamps, result and health status. A successful local feed fetch does not prove an OTA has imported it. Keep API-based Advanced Integrations separate from iCal credentials and diagnostic reports.

Was this article helpful?

Your feedback helps us improve the documentation.