Export Rezi availability to other platforms

Importing each platform’s calendar tells Rezi about their bookings. Exporting Rezi’s calendar back to them closes the loop so every channel knows about every booking.

Think of Rezi as the hub in a hub-and-spoke: it’s the one place that already sees everything, every platform’s feed you’ve imported, plus your manual blocks for owner stays and direct bookings. Exporting that merged picture back to each platform means each platform effectively learns about all the others through Rezi, without you connecting every platform to every other platform pairwise. One export feed, imported everywhere, and the loop is closed.

1. 1

   Copy Rezi’s export link

   In the building’s Calendars tab, copy Rezi’s iCal export URL.

2. 2

   Add it to each platform

   Paste it into Airbnb, VRBO, or Booking.com’s “import calendar” field.

3. 3

   Repeat per channel

   Each platform should import every other platform’s calendar for full protection.

What the export contains

Rezi’s export feed carries every block Rezi knows about: reservations imported from each platform, and manual blocks you created in Rezi. Like all iCal, it’s dates only, no guest names, no prices, so importing it into a platform reveals nothing sensitive. Platforms display imported blocks as unavailable dates, typically labeled as coming from an external calendar, and they make those dates unbookable, which is the whole point.

Where to paste it on each platform

The import lives next to the export you already used: on Airbnb, Availability → Connect calendars → Import calendar; on VRBO, Calendar → Import & Export → Import; on Booking.com, Calendar → Sync calendars → Import. Give the imported calendar a recognizable name like “Rezi, [building]” so future-you knows what it is. After importing, trigger or await the platform’s own refresh, platforms poll imported calendars on their own schedules, generally comparable to Rezi’s.

Verify the loop, then trust it

After setup, run one end-to-end test: create a manual block in Rezi for a far-future date, then confirm it appears as unavailable on each platform within their refresh window (minutes to an hour). Delete the test block afterward and confirm it frees up. Once verified, the mesh runs itself, a new Airbnb booking flows into Rezi on the next sync and out to VRBO on VRBO’s next poll of Rezi’s feed, with total propagation typically inside half an hour.

A note on echoes

If you’re wondering whether re-importing Rezi’s feed, which itself contains Airbnb’s blocks, back into Airbnb causes loops: no. A platform importing a block for dates it already has booked simply shows the same dates unavailable, which they were. The merge logic everywhere is “blocked anywhere = blocked,” which is idempotent, echoes are harmless by construction.