Resolving pending OTA date changes

Keyio never silently overwrites your calendar from Airbnb or Booking.com — you always approve conflicting changes.

Why this exists

Keyio treats your own calendar as the source of truth. When an imported iCal feed reports a date change that conflicts with what's already recorded in Keyio (for example, a guest's stay shortened on Airbnb after you'd already registered them), Keyio doesn't apply the change automatically — it flags the booking as "pending" and asks you to Accept or Reject the incoming change.

  1. 1A pending-dates notification appears on your dashboard when a conflict is detected.
  2. 2Open it to see the current dates in Keyio side by side with the incoming dates from the platform.
  3. 3Accept to apply the platform's change, or Reject to keep what's in Keyio — either way, nothing changes until you decide.

This safety net matters most when a guest is already registered for compliance or a tourist-tax calculation exists for the original dates — accepting a silent overwrite could leave your records out of sync with reality.

When a booking is cancelled on the platform

If a booking that has not started yet disappears from the Airbnb or Booking.com calendar (cancelled, or a block the platform issued again under another reference), Keyio waits six hours to be sure it is really gone — platforms sometimes leave a booking out of their calendar for a while and put it back — and then deletes it, as long as you added nothing to it.

If it holds something of yours — guests, payments, documents, a link you sent or copied — it is never deleted on its own: it appears in Action required as "No longer on Airbnb", and you choose Delete or Keep. If its guests were already reported to the police, cancel that filing from the booking first.