Vrbo Fees, Taxes & Payments

Read and change the cleaning, pet, extra-guest and other fees, the taxes, the base nightly rate, the payment schedule and the damage deposit of a Vrbo listing.

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

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.

cleaningobject | null

{"amount": 120, "type": "PER_STAY", "taxable": true}. null removes the fee.

petsobject | null

Same shape as cleaning.

extraGuestsobject | null

{"amount": 25, "type": "PER_NIGHT_PER_GUEST", "afterGuests": 4} — or PER_STAY_PER_GUEST.

customarray

Other fees by Vrbo fee code. Replaces the current list.

Fees

GET / PUT /v1/channels/vrbo/listings/{id}/fees. Amounts are in the listing's Vrbo currency (currency on the read).

  • Types: PER_STAY or PER_NIGHT. The extra-guest fee is PER_NIGHT_PER_GUEST or PER_STAY_PER_GUEST, charged for each guest above afterGuests.
  • custom fees use Vrbo's fee codes, listed for the listing in the read's customFeeCodes (e.g. PARKING, LINENS, HOT_TUB…). Sending custom replaces all of them, so send the full list; [] removes them all.
  • null for cleaning, pets or extraGuests removes that fee.

Taxes

GET / PUT /v1/channels/vrbo/listings/{id}/taxes. The read returns taxSource, vrboCollects, the rules (jurisdiction, level, rate, type, what it applies to) and raw: Vrbo's tax settings as Vrbo holds them, which is the shape a write takes.

  • Where Vrbo collects and pays the tax itself (vrboCollects: true), the rules are Vrbo's and cannot be changed; a write answers 422 vrbo_rejected with Vrbo's reason.
  • Elsewhere, send tax (in the shape of raw), stayTax ({ "amount", "minAge" }) or partnerTaxSettings ({ "category", "attributes" }).

Base nightly rate

GET / PUT /v1/channels/vrbo/listings/{id}/pricing — { "baseRate": 240 }, the same path as Airbnb's pricing. The base rate is one value for the whole listing; weekday prices and the weekly and monthly discounts are set per date range on Vrbo Rates & Discounts. The answer comes once Vrbo shows the new base rate.

  • Prices for particular nights, availability and minimum stays are calendar writes: PUT /v1/availability/{propertyId} or PATCH /v1/availability/batch, which Vrbo shows over the base rate. See Update pricing.

Payment schedule

GET / PUT /v1/channels/vrbo/listings/{id}/payment-terms — { "percentDueNow": 50, "payments": [{ "percent": 50, "daysBeforeArrival": 30 }] }. percentDueNow plus every payments[].percent must add up to 100.

Damage deposit and protection

GET / PUT /v1/channels/vrbo/listings/{id}/protection — damageDeposit ({ "amount": 500 }, or null for none) and damageProtection, in the shape the read returns with its options.

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

# Cleaning fee 140 per stay, no pet fee, parking and linens as other fees
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/fees \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "cleaning": {"amount": 140, "type": "PER_STAY", "taxable": true},
    "pets": null,
    "custom": [
      {"productCode": "PARKING", "amount": 15, "type": "PER_NIGHT"},
      {"productCode": "LINENS", "amount": 30, "type": "PER_STAY"}
    ]
  }'

# Half now, half 30 days before arrival
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/payment-terms \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"percentDueNow": 50, "payments": [{"percent": 50, "daysBeforeArrival": 30}]}'

Response

{
  "data": {
    "currency": "USD",
    "cleaning": { "amount": 140, "type": "PER_STAY", "taxable": true },
    "pets": null,
    "extraGuests": { "amount": 25, "type": "PER_NIGHT_PER_GUEST", "taxable": false, "afterGuests": 4, "maxOccupancy": 8 },
    "custom": [
      { "productCode": "PARKING", "amount": 15, "type": "PER_NIGHT", "taxable": false },
      { "productCode": "LINENS", "amount": 30, "type": "PER_STAY", "taxable": false }
    ]
  },
  "written": ["cleaning","pets","custom"],
  "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"
}
AI