Vrbo Rates & Discounts

Read the nightly price, weekday, weekly and monthly discounts and minimum stay of every night on a Vrbo listing, and set weekday prices and the two stay discounts over a date range.

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

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.

startDatestringRequired

First night, YYYY-MM-DD.

endDatestringRequired

Last night, on or after startDate, at most 3 years later.

nightlyRatenumber

One price for every night in the range.

nightlyRatesobject

{"sunday": 260, "monday": 240, …, "saturday": 310} — a price per weekday; every weekday in the range needs one.

weeklyDiscountPercentnumber

Discount on stays of 7–27 nights, 0–99.

monthlyDiscountPercentnumber

Discount on stays of 28 nights or more, 0–99.

Reading the rates

GET /v1/channels/vrbo/listings/{id}/rates?start=2026-12-01&end=2026-12-31 returns one row per night: date, weekday, nightlyRate, weeklyDiscountPercent, monthlyDiscountPercent and minStay. Without start and end it reads today and the next 13 days. Rates are always read from Vrbo (dataFreshness.source: "live").

Vrbo has two stay discounts

Weekly (stays of 7 to 27 nights) and monthly (28 nights or more). Vrbo keeps them per night, alongside the weekday prices, so a "default" discount is simply a write over the whole booking window. Vrbo has no other length-of-stay tiers.

  • A write that sends only discounts keeps the current prices, as long as each weekday has one price inside the range. If prices vary within the range, the write is refused with 422 invalid_params on nightlyRates: send the weekday prices with the discounts, or a shorter range.
  • Send nightlyRate for one price on every night, or nightlyRates for a price per weekday — not both.
  • Up to 3 years per call.

Prices belong to the calendar

Per-night prices are normally the listing calendar's job: PUT /v1/availability/{propertyId} pushes them to Vrbo for every linked listing, and the next push puts its own price back on a night you priced here. Use this section for the discounts, and for prices on nights the calendar does not manage. It shares Vrbo's calendar allowance with the price push, so avoid large rate writes while a calendar push for the same listing is still going out.

  • While the account's calendar push is writing, Vrbo can refuse a rate write. Nothing is changed; the answer is 409 vrbo_calendar_busy with retry_after (and a Retry-After header) — wait that long and send the same write again. The base rate (/pricing) answers the same way.

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

# 10% off weekly stays and 25% off monthly stays for the next year, prices unchanged
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/rates \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"startDate": "2026-12-01", "endDate": "2027-11-30", "weeklyDiscountPercent": 10, "monthlyDiscountPercent": 25}'

# Weekend prices for December
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/rates \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"startDate": "2026-12-01", "endDate": "2026-12-31",
       "nightlyRates": {"sunday": 240, "monday": 220, "tuesday": 220, "wednesday": 220, "thursday": 230, "friday": 310, "saturday": 310}}'

Response

{
  "data": {
    "start": "2026-12-01",
    "end": "2026-12-14",
    "currency": "USD",
    "days": [
      { "date": "2026-12-01", "weekday": "tuesday", "nightlyRate": 220, "weeklyDiscountPercent": 10, "monthlyDiscountPercent": 25, "minStay": 2 },
      { "date": "2026-12-02", "weekday": "wednesday", "nightlyRate": 220, "weeklyDiscountPercent": 10, "monthlyDiscountPercent": 25, "minStay": 2 }
    ]
  },
  "written": ["startDate","endDate","weeklyDiscountPercent","monthlyDiscountPercent"],
  "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