Black Friday
Skip to documentation content

Channels & Calendar

Secure iCal feeds and rotate export tokens

Complete iCal source and export URLs can carry bearer secrets. The ability to read a calendar is separate from WordPress staff authority, booking access or permission to mutate a source.

Complete iCal source and export URLs can carry bearer secrets. The ability to read a calendar is separate from WordPress staff authority, booking access or permission to mutate a source.

Keep each credential with its owner

Pro stores import URLs using its authenticated cipher and installation-keyed fingerprint. Administration presents a masked safe model; it must not reveal ciphertext or recover a full stored URL for a screenshot. Use labels and bounded health errors when reporting an issue.

Only trusted public feeds should be configured. The fetcher enforces HTTPS/public-network and redirect/resource limits; do not disable those protections to fetch a private host. The iCal parser is bounded and rejects unsupported whole snapshots instead of accepting an unverified partial calendar.

Rotate a room export

With the required channel permission and entitlement, use the room OTA tab’s create/regenerate action. A fresh URL is returned once; its token is stored as a hash. Rotation checks the current revision/room state and invalidates the previous token for later requests.

Copy the new URL into all legitimate OTA consumers and verify their import status. Deleting a screenshot or rotating the token does not erase cached/downloaded calendars. The endpoint checks token and entitlement even before returning a not-modified response.

Handle installation changes

Backup and restore must protect the encryption/key context and source records. A copied database or changed salts can make protected URLs unusable; use secure re-entry/recovery rather than exposing secrets or reusing production credentials on a demo.

Do not rotate WordPress salts as a casual per-feed repair. It affects broader authentication and booking-link context and needs an operator recovery plan.

Verify and escalate

Test old-token denial and new-token access only with synthetic feeds in an isolated environment. Record labels, route patterns, timestamps, statuses and the exact package/source baseline. Do not attach raw calendars, complete URLs, tokens or guest details.

A successful export fetch or encrypted save is not proof that a provider polled it or that an import completed. Inspect source health and actual inventory separately. See iCal source security.

Was this article helpful?

Your feedback helps us improve the documentation.