Vrbo Amenities & Safety
Read and set the amenities of a Vrbo listing, group by group — including location and view, nearby attractions, sustainability and checkout instructions — and its safety disclosures.
/v1/channels/vrbo/listings/:id/amenitiesParameters
idpathRequiredThe Repull listing id of a listing linked to a Vrbo unit.
vrboListingNumberqueryWhich Vrbo unit, when the listing is linked to more than one.
groupsobject{"<group>": {"values": {"<field id>": <value>}}}. Only the fields you name change.
groups (GET)queryComma-separated groups to read, e.g. essentials,internet. Leave it out for all 19.
Groups and fields
Vrbo keeps about 440 amenity fields in 19 groups: essentials, internet, climateControl, general, office, kitchenAndDining, parking, poolAndSpa, sustainability, entertainment, outdoor, onsiteService, accessibility, homeSafety, safetyDevices, enhancedCleaning, locationAndView, localAttractionsAndActivities and checkoutInstructions.
- Read the group first. Each field comes back with its
id(the key to write),title,typeand currentvalue, plusoptionsfor a choice andmin/max/maxLengthwhere Vrbo has a limit. - Value by type:
checkbox→true/false;choice→ one of itsoptions[].value;text→ a string;numberandmeasurement→ a number. - Some fields only show once another one is set — whether there is wifi only once there is internet. Those carry
shownWhen, naming the parent field and value. Setting the parent to "no" clears its children, as Vrbo's own form does. - Checkout instructions (what guests do before leaving) are the
checkoutInstructionsgroup.
# Read two groups curl 'https://api.repull.dev/v1/channels/vrbo/listings/6199/amenities?groups=internet,kitchenAndDining' \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Safety disclosures
GET / PUT /v1/channels/vrbo/listings/{id}/safety-disclosures — the same path as Airbnb's guest-safety disclosures. On Vrbo they are two amenity groups, read and written field by field as above: homeSafety (smoke and carbon-monoxide detectors, fire extinguisher, deadbolt lock, exterior lighting, first-aid kit and where it is, emergency exit instructions, hospital and police contacts) and safetyDevices (smoke and carbon-monoxide detectors, gas-powered appliances). The detector questions are choices: "yes" or "no", as each field's options list. The field ids are Vrbo's own (the smoke-detector question in homeSafety is spelled smockDetector).
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/safety-disclosures \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"groups": {"homeSafety": {"values": {"smockDetector": "yes", "carbonMonoxideDetector": "yes", "firstAidKit": true}}}}'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
# Internet with wifi, and a dishwasher
curl -X PUT https://api.repull.dev/v1/channels/vrbo/listings/6199/amenities \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"groups": {
"internet": {"values": {"haveInternet": "yes", "haveInternet:yes:haveWifi": "yes"}},
"kitchenAndDining": {"values": {"dishwasher": true}}
}}'Response
{
"data": {
"groups": {
"internet": {
"groupId": "INTERNET",
"fields": [
{ "id": "haveInternet", "type": "choice", "title": "Internet", "value": "yes", "options": [{ "value": "yes", "label": "Yes" }, { "value": "no", "label": "No" }] },
{ "id": "haveInternet:yes:haveWifi", "type": "choice", "title": "Wifi", "value": "yes", "shownWhen": { "id": "haveInternet", "value": "yes" } }
]
}
}
},
"written": ["groups"],
"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"
}