Vrbo Listing Content
Read and change the content of a listing that is already on Vrbo — descriptions, details, photos, rooms and beds, amenities, safety, house rules, booking settings, cancellation, fees, rates, permits and the check-in guide — on the same paths, with the same verbs and answers, as the Airbnb listing endpoints.
/v1/channels/vrbo/listings/:id/contentParameters
idpathRequiredThe Repull listing id of a listing linked to a Vrbo unit.
sectionsqueryRequiredComma-separated section names (descriptions,house-rules,fees), or all.
sourcequerystored (default): Repull's copy. live: read Vrbo now and refresh the copy.
vrboListingNumberqueryWhich Vrbo unit, when the listing is linked to more than one.
Same paths as Airbnb
If you already edit Airbnb listings through Repull, Vrbo works the same way: swap airbnb for vrbo in the path. Where both channels have the same thing it has the same name — descriptions, details, photos (with photos/cover and photos/order), rooms, amenities, safety-disclosures, booking-settings, pricing, permits, checkin-guide, checkout-guide — and the same verbs: POST adds, PATCH or PUT changes, DELETE removes. Reads answer { data, dataFreshness } from Repull's copy, as Airbnb's do.
- What goes inside
datais each channel's own: Vrbo's fields where Vrbo has them, so nothing Vrbo offers is lost in translation. - Room and bed types take Airbnb's words (
bedroom,king_bed) as well as Vrbo's (BEDROOM,KING_BED). - Vrbo adds sections Airbnb does not have:
story,additional-info,house-rules,location,cancellation,fees,rates,payment-terms,protection,taxesandvideos. - The listing itself:
GET /v1/channels/vrbo/listings/{id}(its Vrbo units, status, capacity, rating, account;?include=contentadds every section Repull holds) andPOST /v1/channels/vrbo/listings/{id}with Airbnb's actions —push,unlist,relist,delete.
The sections
Each section has its own path under the listing — /v1/channels/vrbo/listings/{id}/descriptions, /photos, /house-rules and so on. The pages below document each group.
- Descriptions (page) —
descriptions(headline and description, in the listing's language and each language written by hand, withlocale),details(property type, internal name, size, seniors-only, long-term renters),story(about you, why this property, what makes it unique),additional-info. - Photos & videos (page) —
photos: add (by URL or as base64), caption, move, remove, set the cover and the order; photos Vrbo rejected and why.videos: add from a URL, remove. - Amenities & safety (page) —
amenities: 19 groups and about 440 fields.safety-disclosures: the home-safety and safety-device groups on their own. - Rooms & beds (page) —
rooms: bedrooms, bathrooms, living rooms and offices, their beds and room amenities. - House rules & location (page) —
house-rules(check-in and check-out times, occupancy, minimum age, children, pets, smoking, events, your own rules) andlocation(exact or approximate map pin). - Booking settings & cancellation (page) —
booking-settings(instant booking or quote and hold, minimum stay, advance notice, booking window, maximum stay, access type) andcancellation. - Rates & discounts (page) —
rates: nightly prices per weekday and the weekly and monthly stay discounts, over a date range. - Fees, taxes & payments (page) —
fees,taxes,pricing(the base nightly rate),payment-terms(when the guest pays) andprotection(damage deposit and damage protection). - Permits (page) —
permits: the licence or registration details your city or region asks for. - Check-in guide (page) —
checkin-guide: check-in and check-out notes, directions, parking, door access, wifi and per-amenity instructions sent to guests before arrival;checkout-guidereads the checkout part.
Several sections in one call
GET /v1/channels/vrbo/listings/{id}/content?sections=descriptions,house-rules,fees answers several sections at once, keyed by name, each as its own read's data. Sections Repull holds answer from its copy; only the others are read on Vrbo. ?sections=all reads every section but rates; with ?source=live that is about 45 Vrbo calls — around two and a half minutes — so use it for an import, never for polling.
- One section failing never fails the others: it carries
{ error: { code, message } }.
Reads come from Repull's copy
Like the Airbnb listing reads, a Vrbo read answers { data, dataFreshness } from Repull's own copy of the listing, in milliseconds. dataFreshness.lastSyncedAt says when the data was read from Vrbo, and dataFreshness.source whether this answer came from the copy (stored) or from Vrbo just now (live).
- The first read of a section reads Vrbo (a few seconds: calls for one Vrbo account are made a few seconds apart) and keeps the answer. Every write through Repull keeps what Vrbo has after it.
- A copy older than a day still answers at once and is refreshed from Vrbo in the background: that answer says
stale: truewithreason: "refreshing", and the next read has the new one. - Add
?source=liveto read Vrbo now and refresh the copy — for example right after the host changed something on Vrbo itself. - If Vrbo signed the account out, reads still answer from the copy with
reason: "reconnect_required"andfixUrl; writes wait for the account to be reconnected. - Nightly rates are a date range and are always read from Vrbo.
Writes are partial
A write sends only the fields you want to change. A field you leave out is never changed on Vrbo, so you never have to read the whole section, edit it and send it back.
{id}is the Repull listing id of a listing linked to a Vrbo unit —listingIdinGET /v1/channels/vrbo/listings— not the Vrbo listing number. If the listing is linked to more than one Vrbo unit, name the one you mean with?vrboListingNumber=.- Reads work with either access. Writes need the Vrbo account connected with
accessType: "full_access": on amessagingconnection the host's PMS keeps the listing, so a write answers403 vrbo_messaging_accessand nothing is sent to Vrbo. nullmeans none where Vrbo allows it (no pet fee, no damage deposit, no maximum stay) and is sent as exactly that. It is never filled back in from what Vrbo had.- Some values cannot be emptied once set, because Vrbo itself has no way to clear them: you can change them, not remove them. Each page names them; sending
nullor an empty value for one is refused with422 invalid_paramsand nothing is sent to Vrbo. - Every field is optional, but send at least one. An unknown or misspelled field is refused with
422 invalid_paramsnaming it, rather than ignored, so a typo can never look like a successful write. - Writes set values: sending the same body twice leaves the listing as the first one did. The exceptions are adding a photo, a room or a video, which adds one every time.
- A successful write answers
200withwritten(the fields you sent) anddata: the section as Vrbo holds it after the write, read back from Vrbo. That read-back is the confirmation; there is nothing to poll. Repull keeps it, so the next read answers with it at once.
Or push the listing's own content
The section routes edit Vrbo directly. To keep one copy of the content for every channel instead, write it with PUT /v1/listings/{id}/content — the same write Airbnb and Booking.com publish from — then call POST /v1/listings/{id}/publish/vrbo (or POST /v1/channels/vrbo/listings/{id} with {"action": "push"}). For a listing already on Vrbo that publish pushes the content onto it rather than creating a new one.
- Pushed, section by section: headline and description, property type, amenities, house rules, booking settings, cancellation policy, fees, the base rate, and the weekly and monthly stay discounts over the booking window (
rates— nightly prices stay as Vrbo has them). Each write is partial — a field the content has no value for is left alone — and is read back from Vrbo. - Left as they are on Vrbo: rooms, photos and permits (the job lists them in
skipped). Change those with the section routes. - It is a job of a few minutes. Poll
GET /v1/listings/{id}/publish/vrbo?jobId=: every entry ofjob.sectionscarries itsstatus, what was sent, Vrbo's refusals and what Vrbo stored. Sendsectionsto push only some of them. One push per listing runs at a time (409 vrbo_push_running).
curl -X POST https://api.repull.dev/v1/listings/6199/publish/vrbo \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"sections": ["descriptions", "fees"]}'
# → 202 { "mode": "update", "job": { "jobId": "vrbo_push_6199_1763683200000", "status": "running", ... } }What Vrbo itself does not let anyone change
- The address and map pin. Vrbo changes them only through Vrbo support. You can still choose whether guests see the exact location or an approximate area (
location). - Taxes where Vrbo collects them. Where Vrbo collects and pays the tax itself, the tax rules are Vrbo's and read-only; the read says
vrboCollects: true. - Vrbo's photo tags and moderation. Vrbo tags photos itself and can reject one (a collage, people's faces); a rejected photo is listed under
rejectedwith Vrbo's reason. - The rental agreement is readable in the house rules; replacing it is done on Vrbo.
- Taking the listing off sale is not a content write:
POST /v1/channels/vrbo/listings/{id}with{"action": "unlist"}(Vrbo's "Hide listing") and"relist". Per-night prices, availability and minimum stay are calendar writes:PUT /v1/availability/{propertyId}.
Airbnb settings Vrbo has no equivalent for
Preparation time between stays, a same-day booking cutoff, request-to-book guest requirements, length-of-stay discounts beyond weekly and monthly, a non-refundable rate option, a step-by-step check-in guide with a photo per step, and kitchens or outdoor spaces as rooms are Airbnb settings. Vrbo has none of them, so there is nothing to write — the same request on Vrbo is refused naming what Vrbo offers instead. Vrbo in turn has a payment schedule, damage protection, a rental agreement, quote-and-hold booking, your host story and videos, which Airbnb does not.
Errors
A successful read or write answers 200.
422 vrbo_rejected— Vrbo refused a value (for example a headline that names another booking site). The error carries Vrbo's own message, the refused fields inerrors, anddata: what Vrbo holds now. Anything else in the same request that Vrbo accepted is saved.422 invalid_params— the request is not valid for this section (an unknown field, a time not on the half hour, payments that do not add up to 100, a room type Vrbo does not have). Nothing was sent to Vrbo; the error names the field.403 vrbo_messaging_access— the Vrbo account is connected with messaging access, which never changes the listing. Reconnect it withfull_accessto write.403 listing_inactive— activate the listing first.404 not_found— no listing with that id in your workspace, or it is not linked to a Vrbo unit.GET /v1/channels/vrbo/listingslists the linked ones.409 ambiguous_vrbo_unit— the listing is linked to more than one Vrbo unit; send?vrboListingNumber=with one of thevalid_values.409 vrbo_session_expired— Vrbo signed the account out; reconnect it, then retry.409 vrbo_calendar_busy— a rates or base-rate write met the listing's calendar push to Vrbo, which uses the same Vrbo allowance. Nothing was changed; retry afterretry_afterseconds.503 vrbo_busy— Vrbo asked Repull to slow down for this account. Nothing was changed; retry afterretry_afterseconds. Calendar and messages keep working meanwhile.502 vrbo_error— Vrbo did not complete the request; retry in a few minutes.504 vrbo_timeout— Vrbo did not answer in time and a write may still have landed, so read the section with?source=livebefore sending it again.
Example
# Three sections in one call curl 'https://api.repull.dev/v1/channels/vrbo/listings/6199/content?sections=descriptions,house-rules,fees' \ -H "Authorization: Bearer sk_live_YOUR_KEY" # Every section, read from Vrbo now (about two and a half minutes) curl 'https://api.repull.dev/v1/channels/vrbo/listings/6199/content?sections=all&source=live' \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Response
{
"sections": {
"descriptions": [{ "locale": null, "primary": true, "headline": "Lakefront cabin with hot tub", "description": "Wake up to the lake…" }],
"house-rules": { "checkInTime": "16:00", "checkOutTime": "10:00", "maxGuests": 6 },
"fees": { "error": { "code": "vrbo_timeout", "message": "Vrbo did not answer in time." } }
},
"dataFreshness": { "lastSyncedAt": "2026-11-21T18:04:12.000Z", "stale": false, "reason": "ok", "source": "stored", "accounts": [] },
"vrboListingNumber": "5506023"
}
// One section failing never fails the others: it carries { error: { code, message } }.