Vrbo

The host signs in with their own Vrbo account. From then on your app reads their Vrbo bookings, inquiries, guest messages and reviews through the same endpoints as every other channel, and answers them: messages, inquiry pre-approvals and quotes, review replies. With full access, Repull also keeps the Vrbo calendar and prices in step with the listing, and can create a new Vrbo listing from a listing's content.

Works alongside the host's PMS

Connecting Vrbo to Repull does not disconnect or replace the PMS or channel manager that already runs the host's Vrbo listings. With accessType: "messaging" Repull never writes the Vrbo calendar, prices or content — the PMS keeps them. See Use Repull alongside a PMS.

Choose the access

accessTypeUse it whenWhat Repull does on Vrbo
messagingThe host keeps their PMS or channel managerReads bookings, inquiries, messages and reviews; sends messages, pre-approvals, quotes and review replies. Never pushes the calendar.
full_access (default)Repull is the channel managerEverything above, plus availability, prices, minimum stay and closed to arrival / departure pushed to Vrbo for each linked listing, listings taken off sale and back, and new listings created on Vrbo.

Set accessType when you create the session to decide it for the host. Leave it out and the host chooses on the hosted page.

Connect

  1. Your server creates a Connect session for vrbo-login and sends the host to its URL.
  2. The host signs in with their Vrbo email and password. If Vrbo sends them a verification code, they enter it on the same page.
  3. The host picks which Vrbo units belong to which of your listings. On a workspace with no listings yet there is nothing to pick: every unit becomes a listing on its own (past a plan limit, created inactive) and the import starts at sign-in.
  4. Once they confirm, the import starts: upcoming bookings and the last 30 days of messages first, then the rest of the account's history in the background.
curl -X POST https://api.repull.dev/v1/connect \
  -H 'Authorization: Bearer sk_live_...' \
  -H 'Content-Type: application/json' \
  -d '{
    "redirectUrl": "https://yourapp.com/connected",
    "allowedProviders": ["vrbo-login"],
    "accessType": "messaging"
  }'

Check the connection and the import with GET /v1/connect/vrbo-login. Each signed-in account comes back with its access and where its import stands (importing → importing_history → imported).

curl https://api.repull.dev/v1/connect/vrbo-login \
  -H 'Authorization: Bearer sk_live_...'

To map units in your own UI instead of the hosted page, create the session with "mapping": "api". Connect then finishes right after sign-in and skips its mapping step. Use the connection handle vrbo:{externalAccountId}, where externalAccountId is Vrbo's own account id (accounts[].externalAccountId on GET /v1/connect/vrbo-login, e.g. vrbo:7001234): GET /v1/connections/{id}/unitslists the account's units with a suggested listing for each. The unit_id is the Vrbo listing number, which doesn't change, and meta.address is the address as Vrbo has it. POST /v1/connections/{id}/mappings maps them. Mapping the first unit starts the import. On a workspace with no listings yet the units are already mapped to new listings when sign-in finishes, and the import is running.

A host who leaves the hosted mapping before every unit is mapped can come back to it without signing in to Vrbo again. While units are left, the Vrbo connection on GET /v1/connect carries action.reason: "needs_mapping" (required is true when none are mapped yet) and a fixUrl. Send the host to the fixUrl: it opens Connect straight on that account's unit mapping. The Connections page in the dashboard shows the same link as Map units.

Ask every host for one more step: adding the account's notification address on Vrbo as a secondary email, with message and reservation notifications on. Vrbo's notification emails are how new bookings, inquiries and guest messages reach Repull within a minute; the scheduled check every few minutes is the backup. Hosted Connect asks for it on its mapping screen. With "mapping": "api" that screen is skipped, so ask in your own flow: the address comes back as notification_email on GET /v1/connections/vrbo:{externalAccountId}/units and as notifications.address on GET /v1/connect/vrbo-login, next to notifications.state, which says whether the emails are arriving. See Vrbo notification address.

Listings and reservations

  • GET /v1/channels/vrbo/listings — the Vrbo units linked to your listings.
  • GET /v1/channels/vrbo/reservations, or GET /v1/reservations for every channel at once.

Vrbo bookings are managed on Vrbo: creating, accepting or cancelling them through Repull is not supported.

Guest messages

Vrbo threads are conversations like any other. Filter them with platform=vrbo and reply with the usual send call — the reply goes out on Vrbo. Messages are text only; files are refused with attachments_not_supported.

curl 'https://api.repull.dev/v1/conversations?platform=vrbo' \
  -H 'Authorization: Bearer sk_live_...'

curl -X POST https://api.repull.dev/v1/conversations/{id}/messages \
  -H 'Authorization: Bearer sk_live_...' \
  -H 'Content-Type: application/json' \
  -d '{ "message": "Hi Anna — the hot tub is ready for your arrival." }'

A reply Vrbo takes right away answers 200 with status: "sent". When Vrbo is busy, the reply is recorded and delivered in the background: the call answers 202 with status: "queued". Do not send it again. The message's status on GET /v1/conversations/{id}/messages becomes sent, or failed with statusReason, and conversation.message.status_changed tells you when. See Delivered in the background.

New guest messages arrive within about a minute when the account's notification address is set up on Vrbo, and on a slower scheduled check when it is not.

Inquiries: pre-approve or send a quote

Answer a Vrbo inquiry from its conversation. A pre-approval invites the guest to book at the listed price; a special offer is Vrbo's edited quote — send the rent, the fees by Vrbo fee type and a damage deposit, and Vrbo adds its taxes and service fee to reach the guest total. Both can carry a message to the guest.

# Pre-approve
curl -X POST https://api.repull.dev/v1/conversations/{id}/pre-approval \
  -H 'Authorization: Bearer sk_live_...' \
  -H 'Content-Type: application/json' \
  -d '{ "message": "Those dates are free — book whenever you are ready." }'

# Send a quote
curl -X POST https://api.repull.dev/v1/conversations/{id}/special-offers \
  -H 'Authorization: Bearer sk_live_...' \
  -H 'Content-Type: application/json' \
  -d '{
    "checkIn": "2026-11-06", "checkOut": "2026-11-09", "guests": 4,
    "rentalAmount": 780,
    "fees": [{ "type": "CLEANING", "value": 120 }],
    "message": "Here is a quote for your dates."
  }'

# Read or withdraw the current quote
GET    /v1/conversations/{id}/special-offers/current
DELETE /v1/conversations/{id}/special-offers/current

Withdraw a pre-approval with DELETE /v1/conversations/{id}/pre-approval.

Reviews

List Vrbo reviews with GET /v1/reviews?platform=vrbo and reply publicly with POST /v1/reviews/{id}/reply. Vrbo signs the reply with a name — the host name on the account, or the name you send. Vrbo takes one reply per review.

curl -X POST https://api.repull.dev/v1/reviews/{id}/reply \
  -H 'Authorization: Bearer sk_live_...' \
  -H 'Content-Type: application/json' \
  -d '{ "message": "Thank you, Katherine — come back soon!", "name": "The Pine Cabin team" }'

Calendar and prices (full access)

With full_access, a calendar write on a linked listing — PUT /v1/availability/{propertyId} or PATCH /v1/availability/batch— is pushed to Vrbo too: availability, nightly prices, minimum stay, and closed to arrival / closed to departure (Vrbo's check-in and check-out day rule for each night). Repull only opens or closes nights it blocked itself or that the host blocked; guest bookings on Vrbo are never touched. With messaging access nothing is pushed.

Calendar run by the host's PMS

When Vrbo says another tool manages the account's calendar, Vrbo refuses price and availability changes from anyone else. Repull detects it, switches the account to messaging and refuses calendar sync with 409 calendar_managed_elsewhere. See Vrbo calendar managed by another tool.

iCal backup on every unit

With calendar sync on, Repull also adds the listing's Repull calendar feed to the Vrbo unit (Vrbo → Calendar → Import calendar), so a booking still closes the night on Vrbo if a direct update fails, and removes other tools' imported feeds. See Vrbo iCal backup.

Vrbo calendar writes are queued per Vrbo account and sent at about 90 writes a minute; only nights that differ from what Vrbo already holds are sent, and each is read back. A single change usually lands within a minute or two; repricing a whole portfolio at once can take an hour or two. GET /v1/listings/{id}/calendar-sync shows the queue and lists any night Vrbo shows differently, with the reason. Maximum stay is not sent to Vrbo: Vrbo has no maximum stay per night, only one property-wide setting the host manages on Vrbo.

A Vrbo markup belongs to the Vrbo account: PUT /v1/listings/{id}/markups with "channel": "vrbo" sets it for every listing linked on that account and re-sends their prices.

curl -X PUT https://api.repull.dev/v1/listings/{id}/markups \
  -H 'Authorization: Bearer sk_live_...' \
  -H 'Content-Type: application/json' \
  -d '{ "channel": "vrbo", "markupPercent": 20 }'

Take a listing off sale (full access)

POST /v1/listings/{id}/offline hides the linked Vrbo listing from Vrbo search, and POST /v1/listings/{id}/onlinebrings it back, along with the listing's other channels. Both read the state back from Vrbo, which takes about ten seconds to show the change.

Create a listing on Vrbo (full access)

POST /v1/listings/{id}/publish/vrbocreates the listing on Vrbo, in the host's connected account, from the listing's content: title and description, property type, rooms and beds, amenities, photos, house rules, check-in and check-out times, minimum stay, advance notice and booking window, the nightly price, cleaning, pet and extra-guest fees, the cancellation policy and the licence number. Vrbo's automatic new-listing discount is turned off so the listing sells at your prices.

Vrbo's onboarding takes 5 to 15 minutes, so the call starts a job. Poll GET /v1/listings/{id}/publish/vrbo?jobId= for each finished step. When Vrbo has published the listing, that read links it to your listing with calendar sync on and sends the whole calendar: keep polling until linked is true. A run that stops part-way is completed by publishing again, not duplicated.

curl -X POST https://api.repull.dev/v1/listings/{id}/publish/vrbo \
  -H 'Authorization: Bearer sk_live_...'

# → 202 { "job": { "jobId": "vrbo_13_1762790000000", "status": "running", ... } }

curl 'https://api.repull.dev/v1/listings/{id}/publish/vrbo?jobId=vrbo_13_1762790000000' \
  -H 'Authorization: Bearer sk_live_...'

Missing content (street address, city, photos, nightly price or description) is refused with 422 listing_incomplete naming what is missing. With several Vrbo accounts, name one with accountId ("vrbo:7001234", Vrbo's account id). Editing the content of a listing that is already on Vrbo is done on Vrbo. See the capability matrix for the full list.

AI