Vrbo iCal backup

Every Vrbo unit with calendar sync on also imports the listing's Repull calendar feed. If a direct calendar update to Vrbo ever fails, Vrbo still closes the nights booked elsewhere the next time it reads the feed. Repull adds it for you, so hosts almost never close dates on Vrbo by hand.

What it is

Each listing has one iCal feed at an address on api.repull.dev, named Repull. It holds the listing's bookings from every connected channel and its blocked nights, as all-day events.

  • Repull pushes availability, prices and stay rules to Vrbo directly, within a minute or two. The feed is the backup for availability only: Vrbo reads iCal feeds on its own schedule, usually every few hours, and iCal carries no prices.
  • A booking that reaches Repull therefore closes the night on Vrbo even if the direct update was refused or the Vrbo sign-in had expired.
  • The feed carries dates only, never guest names, contact details or prices.

Added automatically

You don't need to do anything. Repull adds the feed to a Vrbo unit itself, through the host's Vrbo connection:

  • when calendar sync is switched on for the unit (in Connect, or with calendarSync: true on POST /v1/connections/{id}/mappings);
  • and again by the daily Vrbo calendar check, if someone removed it on Vrbo.

On Vrbo it shows under the property's Calendar → Import calendar as a calendar named Repull.

Other tools' feeds are removed

With calendar sync on, Repull is the unit's master calendar. A feed another tool left on the unit, for example a previous PMS's, can keep nights closed on Vrbo that are open in Repull, and the host loses bookings. So while calendar sync is on, Repull removes other imported calendars from the unit, the same way it clears owner blocks it did not make. It only does this once the Repull feed is in place, and it tells you each time with the webhook below.

Connect every channel the unit sells on

A removed feed's bookings stay covered only if that channel is connected to Repull. Before turning calendar sync on, connect the other channels the listing sells on, or keep calendar sync off for that unit.

Why not to remove it

Without the feed, a failed direct update leaves the night open on Vrbo until someone notices, and a guest can book a night that is already taken. If the host removes it, Repull puts it back at the next daily check and sends listing.ical_feed_changed with reason: "repull_feed_missing".

See it in the API

GET /v1/listings/{id}/ical returns the feed address and, per Vrbo unit, whether Vrbo imports it (as of the last daily check):

{
  "listingId": "1001",
  "url": "https://api.repull.dev/ical/4f9c2d7e1a8b3c6d5e0f9a2b7c4d1e8f3a6b9c2d5e8f1a4b7c0d3e6f9a2b5c8d.ics",
  "calendarName": "Repull",
  "enabled": true,
  "vrbo": [
    { "unitId": "7001234", "calendarSync": true, "status": "imported", "otherFeeds": [], "checkedAt": "2026-11-19T05:12:40.000Z" }
  ]
}
  • imported: Vrbo imports the feed.
  • pending: calendar sync is on and Repull has not checked the unit yet. It adds the feed itself.
  • failed: Vrbo did not take it. Ask the host to add it by hand (below).
  • not_imported: checked and not there, for example because the listing's feed was turned off.
  • off: calendar sync is off, so Repull leaves the unit's imported calendars alone.

The same address is on POST /v1/connections/{id}/mappings (icalFeedUrl per mapped Vrbo unit) and on GET /v1/connections/{id}/units (meta.icalBackup).

Keep the address private

Anyone with the address can see which nights are booked (no guest details). Show it only to the host.

Add it by hand (only if Repull couldn't)

If Vrbo refuses the feed, Repull sends listing.ical_feed_changed with action: "repull_feed_add_failed", emails the workspace owner once, and hosted Connect shows the steps. Repull changes nothing else on that unit until the feed is there. The host then:

  1. In Vrbo, opens the property's Calendar, then Import calendar.
  2. Names the calendar Repull and pastes the feed address.
  3. Saves, and leaves it there.

The webhook

listing.ical_feed_changedis sent each time Repull changes a Vrbo unit's imported calendars, or tries and fails. action says what happened:

  • repull_feed_added: the Repull feed is now imported (reason: "repull_feed_missing" when it was put back).
  • repull_feed_add_failed: Vrbo did not take it. Show the host repullFeedUrl and the steps above.
  • other_feed_removed: another tool's feed (feed.name) was removed.
  • other_feed_remove_failed: removing it failed. Ask the host to remove feed.name in Vrbo → Calendar → Import calendar.
{
  "event": "listing.ical_feed_changed",
  "data": {
    "object": { "id": 1001, "customerId": 1, "channel": "vrbo", "externalListingId": "7001234", "name": "Lakeview Loft" },
    "provider": "vrbo",
    "action": "other_feed_removed",
    "feed": { "name": "Other PMS 12B", "url": "https://pms.example.com/ical/12b.ics" },
    "repullFeedUrl": "https://api.repull.dev/ical/4f9c2d7e1a8b3c6d5e0f9a2b7c4d1e8f3a6b9c2d5e8f1a4b7c0d3e6f9a2b5c8d.ics",
    "reason": "repull_is_master_calendar",
    "trigger": "drift_check",
    "error": null,
    "occurredAt": "2026-11-19T05:12:40.000Z",
    "docsUrl": "https://repull.dev/docs/channels/vrbo/ical-backup"
  }
}

See also Vrbo calendar and prices and Vrbo calendar managed by another tool (when another tool runs the account's calendar, calendar sync is off and Repull leaves imported calendars alone).

AI