Vrbo calendar managed by another tool

Some Vrbo accounts are run by connected software, usually the host's PMS. Vrbo then accepts price and availability changes for that account only from that software. Repull detects this, keeps bookings, inquiries, messages and reviews working, and turns calendar sync off for the account so nothing is sent that Vrbo would refuse.

What Repull does

Repull asks Vrbo when the account connects and once a day after that. While Vrbo says another tool manages the calendar:

  • Bookings, inquiries, guest messages and reviews keep importing, and your app can still answer them.
  • Calendar sync is off for every unit of the account: Repull sends no availability, prices, minimum stays or arrival / departure rules to Vrbo. The account's accessType becomes messaging.
  • Turning calendar sync on is refused with 409 calendar_managed_elsewhere.
  • Repull sends the account.calendar_access_changed webhook.

This applies to the whole Vrbo account

Vrbo reports it per account, not per listing, so every unit the account holds is treated the same way.

See it in the API

Each Vrbo account on GET /v1/connect/vrbo-login carries a calendar object:

{
  "externalAccountId": "1295468",
  "accessType": "messaging",
  "calendar": {
    "managedBy": "integrated_software",
    "detectedAt": "2026-11-16T19:06:56.653Z",
    "checkedAt": "2026-11-16T19:06:56.653Z",
    "docsUrl": "https://repull.dev/docs/channels/vrbo/calendar-managed-elsewhere"
  }
}
  • managedBy: integrated_software while another tool manages the calendar, null otherwise.
  • detectedAt: when Repull first saw it.
  • checkedAt: when Repull last asked Vrbo.

The same object is on GET /v1/connections/vrbo:{accountId}/units, where each unit's meta.calendarSync is false with meta.calendarSyncBlocked: "calendar_managed_elsewhere". On GET /v1/listings/{id}/calendar-sync, the Vrbo channel shows status: "off" with offReason: "calendar_managed_elsewhere".

The webhook

account.calendar_access_changed is sent each time the state changes, in either direction. Subscribe to it on your webhook endpoint like any other event.

{
  "event": "account.calendar_access_changed",
  "data": {
    "workspaceId": 1204,
    "provider": "vrbo",
    "accountId": "1295468",
    "connectionId": 909,
    "calendar": {
      "managedBy": "integrated_software",
      "detectedAt": "2026-11-16T19:06:56.653Z",
      "checkedAt": "2026-11-16T19:06:56.653Z",
      "docsUrl": "https://repull.dev/docs/channels/vrbo/calendar-managed-elsewhere"
    },
    "changedAt": "2026-11-16T19:06:56.653Z"
  }
}

The 409 error

Sending calendarSync: true to POST /v1/connections/{id}/mappings for such an account changes nothing and returns:

{
  "error": {
    "code": "calendar_managed_elsewhere",
    "message": "Vrbo says another tool (such as your PMS) manages this account's calendar, so calendar sync can't be turned on. Bookings and messages keep working.",
    "docs_url": "https://repull.dev/docs/channels/vrbo/calendar-managed-elsewhere",
    "connection_id": "vrbo:1295468",
    "units": ["1594829"]
  }
}

Map the units without calendarSync (or with false) and they map as usual, with bookings and messages only.

Turn calendar sync back on

  1. On Vrbo, the host disconnects the other tool from the account (or asks it to stop managing the calendar).
  2. Wait for the next check (at most a day). calendar.managedBy becomes null and account.calendar_access_changed is sent.
  3. Turn calendar sync on per unit. Repull never turns it back on by itself, so prices the host still manages elsewhere are not overwritten by surprise.
curl -X POST https://api.repull.dev/v1/connections/vrbo:1295468/mappings \
  -H 'Authorization: Bearer sk_live_...' \
  -H 'Content-Type: application/json' \
  -d '{ "mappings": [ { "unitId": "1594829", "listingId": 31124, "calendarSync": true } ] }'

To keep managing prices in the other tool, leave things as they are: Repull keeps handling bookings and messages. See Vrbo access types and Use Repull alongside a PMS.

AI