Vrbo Rooms & Beds
Add, change and remove the bedrooms, bathrooms, living rooms and offices of a Vrbo listing, with their beds and room amenities — with the Airbnb room endpoints' verbs and words.
/v1/channels/vrbo/listings/:id/roomsParameters
idpathRequiredThe Repull listing id of a listing linked to a Vrbo unit.
vrboListingNumberqueryWhich Vrbo unit, when the listing is linked to more than one.
room_typestringRequiredbedroom, bathroom, living_room or office (or Vrbo's BEDROOM, BATHROOM, LIVING_ROOM, OFFICE).
room_numberintegerNames the room ("Bedroom 3") when no name is given.
namestringThe room's name.
bedsarray[{"type": "king_bed", "quantity": 1}] — every bed in the room.
sub_typestringBathrooms: FULL_BATH (default) or NO_TUB_OR_SHOWER (half bath).
descriptionstringAbout the room. Can be changed, not emptied once set.
amenitiesobjectRoom amenities: {"<amenity id>": true | false}.
Reading the rooms
GET /v1/channels/vrbo/listings/{id}/rooms returns spaces, each with spaceId, type (BEDROOM, BATHROOM, LIVING_ROOM, OFFICE), subType for a bathroom, name, description, beds and room amenities. It also lists the bed types with their sizes (bedTypes) and the bathroomTypes.
Adding, changing and removing rooms
The same calls as Airbnb's rooms: POST adds one, PUT ?roomId= changes one, DELETE ?roomId= removes one. roomId is the room's spaceId from the read. Every answer is the rooms as Vrbo has them after the change.
- Room types are Airbnb's words or Vrbo's. Vrbo has bedrooms, bathrooms, living rooms and offices only; a kitchen, outdoor space or garage is described with the amenities, and sending one as a room is refused with
422 invalid_paramsnaming the types Vrbo takes. - Bed types:
king_bed,queen_bed,double_bed,small_double_bed,single_bed,bunk_bed,sofa_bed,couch,toddler_bed,crib(Airbnb's words), or Vrbo's own —KING_BED,QUEEN_BED,FULL_BED,TWIN_BED,BUNK_BED,SOFA_BED,FUTON,MURPHY_BED,CRIB,CHILD_BED. Beds that come in several sizes on Vrbo (bunk beds, sofa beds, futons, Murphy beds) takesizefrombedTypes[].sizes; without it the usual size is used. bedsreplaces the room's beds: send every bed, not just the changed one. Quantity is 1 to 20 per bed type.- Vrbo cannot change the type of an existing room: delete it and add one of the new type.
- A room
descriptioncan be changed but not emptied once set.
# Change the beds in a room
curl -X PUT 'https://api.repull.dev/v1/channels/vrbo/listings/6199/rooms?roomId=31877410' \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"beds": [{"type": "king_bed", "quantity": 1}]}'
# Remove a room
curl -X DELETE 'https://api.repull.dev/v1/channels/vrbo/listings/6199/rooms?roomId=31877456' \
-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: 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.
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
# Add a third bedroom with two twin beds
curl -X POST https://api.repull.dev/v1/channels/vrbo/listings/6199/rooms \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"room_type": "bedroom", "room_number": 3, "beds": [{"type": "single_bed", "quantity": 2}]}'Response
{
"data": {
"spaces": [
{ "spaceId": "31877410", "type": "BEDROOM", "name": "Bedroom 1", "beds": [{ "type": "KING_BED", "size": "KING", "quantity": 1 }] },
{ "spaceId": "31877455", "type": "BEDROOM", "name": "Bedroom 3", "beds": [{ "type": "TWIN_BED", "size": "TWIN", "quantity": 2 }] }
]
},
"written": ["room_type","room_number","beds"],
"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"
}