Vrbo Photos & Videos

Add, caption, move and remove the photos of a Vrbo listing and set its cover and order, with the Airbnb photo endpoints' verbs and fields, and add or remove its videos. Photos Vrbo rejected are listed with its reason.

POST/v1/channels/vrbo/listings/:id/photos

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.

photosarrayRequired

1–20 photos: [{"url": "https://…/living-room.jpg", "caption": "Living room"}], or "image" (base64 data) instead of url. Each item adds a photo, every time it is sent.

Reading the photos

GET /v1/channels/vrbo/listings/{id}/photos returns items in display order, each with id, url, caption, rank, the rooms it shows (roomIds), Vrbo's own tags and status; plus count and rejected — photos Vrbo refused, each with its reason.

Adding, changing and removing

The same calls as Airbnb's photos. Photo ids are the ids from the read; every answer is the photos as Vrbo has them after the change.

  • POST …/photos with {"photos": [...]} adds 1–20 photos at the end. Each takes an https url Vrbo downloads, or image: the photo itself as base64 (a data:image/jpeg;base64, prefix is fine), like Airbnb's upload — Repull hosts it for Vrbo.
  • PATCH …/photos with photo_id changes one photo: caption, and/or sort_order (1 = first) to move it.
  • DELETE …/photos?photoId=84210102 removes photos (comma-separate several ids).
  • PUT …/photos/cover with {"photo_id": "…"} makes one the first photo, the one guests see in search.
  • PUT …/photos/order with {"photo_ids": [...]} sets the order, first photo first. Photos you leave out keep their order after the ones you send.
  • Vrbo checks every new photo. One it refuses (a collage, a photo with people's faces, too small) does not appear in items; it is listed in rejected with Vrbo's reason.
  • A caption can be changed but not emptied once set: Vrbo has no way to clear one. tags are Vrbo's own and cannot be set.
# Move a photo to the front and fix its caption
curl -X PATCH https://api.repull.dev/v1/channels/vrbo/listings/6199/photos \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"photo_id": "84210377", "caption": "Hot tub at sunset", "sort_order": 1}'

# Set the whole order
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/photos/order \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"photo_ids": ["84210377", "84210351", "84210118"]}'

# Remove one
curl -X DELETE 'https://api.repull.dev/v1/channels/vrbo/listings/6199/photos?photoId=84210102' \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

Videos

GET /v1/channels/vrbo/listings/{id}/videos lists them with fileName, Vrbo's processing and review status, player and thumbnail URLs, uploadedTime and any rejectedReasons.

  • POST with { "url": "https://…" } adds one: an MP4, MOV, WEBM, AVI or QT file under 2 GB. Repull downloads it and uploads it to Vrbo within the request, so a large file takes minutes. Vrbo then processes and reviews it.
  • Each call adds a video. If a call times out, read the videos with ?source=live before sending it again.
  • DELETE ?videoId= removes videos (comma-separate several ids). Both answer with the videos as Vrbo has them now.
curl -X POST https://api.repull.dev/v1/channels/vrbo/listings/6199/videos \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://cdn.example.com/6199/tour.mp4"}'

curl -X DELETE 'https://api.repull.dev/v1/channels/vrbo/listings/6199/videos?videoId=v_31877' \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

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

# Add two photos: one by URL, one uploaded
curl -X POST https://api.repull.dev/v1/channels/vrbo/listings/6199/photos \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"photos": [{"url": "https://cdn.example.com/6199/lake-view.jpg", "caption": "View from the deck"},
                  {"image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQ…"}]}'

Response

{
  "data": {
    "count": 24,
    "items": [
      { "id": "84210377", "url": "https://media.vrbo.com/…/84210377.jpg", "caption": "Hot tub at sunset", "rank": 1, "roomIds": [], "status": "PUBLISHED" },
      { "id": "84210351", "url": "https://media.vrbo.com/…/84210351.jpg", "caption": "View from the deck", "rank": 2, "roomIds": [], "status": "PUBLISHED" }
    ],
    "rejected": []
  },
  "written": ["photos"],
  "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