Vrbo Descriptions

Read and change the headline and description of a Vrbo listing in every language, its property details, host story and additional details — descriptions and details work like Airbnb's.

PUT/v1/channels/vrbo/listings/:id/descriptions

Parameters

idpathRequired

The Repull listing id of a listing linked to a Vrbo unit.

vrboListingNumberquery

Which Vrbo unit, when the listing is linked to more than one.

localestring

Leave out for the listing's own language. A language code (fr-FR) writes that language's translation by hand.

headlinestring

Up to 80 characters; Vrbo asks for at least 10.

descriptionstring

The listing description, up to 10,000 characters.

Headline and description, in every language

GET /v1/channels/vrbo/listings/{id}/descriptions lists the listing's own text first (primary: true, locale: null, with Vrbo's length limits) and then every language written by hand (locale: "fr-FR"…), plus the languages a translation can be written in. ?locale=fr-FR returns one language.

  • PUT with headline and/or description changes the listing's own text. Add locale to write that language instead: a hand-written translation replaces Vrbo's automatic one for that language. A field you leave out keeps the text Vrbo has.
  • DELETE ?locale=fr-FR removes your translation, so Vrbo translates that language automatically again. The listing's own text can be changed, not removed.
  • Vrbo refuses some text: the characters ( ) * $ €, the names of other booking sites, and a few words it blocks. The write answers 422 vrbo_rejected with Vrbo's own message, for example Remove "airbnb" to save.
  • Every answer — read or write — is the full list of languages, as GET returns it.
# French, by hand
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/descriptions \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"locale": "fr-FR", "headline": "Chalet au bord du lac avec spa", "description": "Réveillez-vous face au lac…"}'

# Back to Vrbo's automatic German
curl -X DELETE 'https://api.repull.dev/v1/channels/vrbo/listings/6199/descriptions?locale=de-DE' \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Property details

GET / PUT /v1/channels/vrbo/listings/{id}/details.

  • propertyType — one of the propertyTypeOptions the read lists, e.g. house, condo, townhome, cabin.
  • propertyName — your internal name for the property; guests do not see it.
  • interiorSize — { "value": 1450, "unit": "sqft" } or "sqm".
  • seniorsOnly, longTermRentersWelcome — true / false.
  • propertyType and propertyName can be changed but not emptied once set.
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/details \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"propertyType": "cabin", "interiorSize": {"value": 1450, "unit": "sqft"}}'

Your story

GET / PUT /v1/channels/vrbo/listings/{id}/story — the host story shown on the listing: aboutYou, whyThisProperty, uniqueBenefits.

Additional details

GET / PUT /v1/channels/vrbo/listings/{id}/additional-info — free text about the property, the bedrooms and the bathrooms.

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: true with reason: "refreshing", and the next read has the new one.
  • Add ?source=live to 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" and fixUrl; 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 — listingId in GET /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 a messaging connection the host's PMS keeps the listing, so a write answers 403 vrbo_messaging_access and nothing is sent to Vrbo.
  • null means 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 null or an empty value for one is refused with 422 invalid_params and nothing is sent to Vrbo.
  • Every field is optional, but send at least one. An unknown or misspelled field is refused with 422 invalid_params naming 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 200 with written (the fields you sent) and data: 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.

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 in errors, and data: 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 with full_access to 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/listings lists the linked ones.
  • 409 ambiguous_vrbo_unit — the listing is linked to more than one Vrbo unit; send ?vrboListingNumber= with one of the valid_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 after retry_after seconds.
  • 503 vrbo_busy — Vrbo asked Repull to slow down for this account. Nothing was changed; retry after retry_after seconds. 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=live before sending it again.

Example

# Change only the headline
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/descriptions \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"headline": "Lakefront cabin with private hot tub"}'

Response

// 200
{
  "data": [
    { "locale": null, "primary": true, "headline": "Lakefront cabin with private hot tub", "description": "Wake up to the lake…" },
    { "locale": "fr-FR", "primary": false, "headline": "Chalet au bord du lac avec spa", "description": "Réveillez-vous face au lac…" }
  ],
  "written": ["headline"],
  "dataFreshness": {
    "lastSyncedAt": "2026-11-21T18:04:12.000Z",
    "stale": false,
    "reason": "ok",
    "source": "live",
    "accounts": [{ "accountId": "1", "accountName": "Lakeside Rentals", "lastSyncedAt": "2026-11-21T18:04:12.000Z", "stale": false, "reason": "ok" }]
  },
  "vrboListingNumber": "5506023"
}

// 422 — Vrbo refused the headline; data is what Vrbo still has
{
  "error": {
    "code": "vrbo_rejected",
    "message": "Vrbo refused a change to the headline and description: Remove \"airbnb\" to save",
    "section": "descriptions",
    "errors": [{ "field": null, "message": "Remove \"airbnb\" to save" }],
    "data": [{ "locale": null, "primary": true, "headline": "Lakefront cabin with hot tub", "description": "Wake up to the lake…" }]
  }
}
AI