Channels & Calendar

Distinguish Website, API and iCal sources Read channel labels in bookings and calendars so website reservations, API reservations and iCal external blocks are not mixed. → Export room availability with iCal Create one secure iCal export URL per room type and connect it to an OTA without exposing guest data or partial inventory. → Import an iCal source Attach an OTA iCal feed to a room type with a source label, safe URL and bounded quantity so occupied dates block website sales. → Monitor iCal schedule, retries and health Read iCal health states, understand the 30-minute scheduler and recover failed or stale feeds without clearing safe inventory blocks. → Secure iCal URLs and rotate tokens Protect imported feed URLs and one-time export tokens, rotate a leaked link and preserve inventory during license or cache incidents. → Understand external inventory blocks Interpret iCal external blocks, interval and quantity semantics so staff can explain why website inventory is unavailable. → Use the unified booking calendar Read website bookings, API reservations and iCal blocks together while keeping source ownership and read-only restrictions visible. → Operate Booking.com and Agoda API integration Use the retained Booking.com and Agoda API module separately from iCal and preserve its existing credentials, mapping and reservation semantics. → Avoid and recover from channel overbooking Reduce stale-calendar and duplicate-source risk, then preserve evidence and apply the approved recovery path when channel inventory conflicts. →