Vrbo vacation rental search API

Endpoint facts

Method

POST

API path

/vrbo/search

Auth

apiKey

Credits

5 credits/request

Charged on

Successful 2xx responses only

Platform

Vrbo

Execution

Managed browser rendering where the target needs it

Response schema

#/definitions/vrbo.vrboSearchResponseDoc

Request body schema

#/definitions/vrbo.SearchOption

How this endpoint behaves

Searches public Vrbo vacation-rental listings for a selected destination and travel dates. Supply the destination label, region_id, and lat_long returned by Vrbo's destination suggestion UI. The API returns listing cards with property ID, name, URL, and fields when Vrbo provides them (price, currency, rating, review count, bedrooms, property type, and image).

Search-card prices are tied to the supplied stay dates. Returned property URLs are canonical Vrbo property links and omit per-search IDs, selected room/rate IDs, and date parameters.

When Vrbo includes the controls, total_results, filters, and sort_options describe the observed result count and available controls. Apply categorical and step filters with filters: copy an option's value and use its id as the selection ID when it differs from the parent filter group's ID. The observed popular_group includes options backed by other selection IDs. Apply a visible price control with filter_ranges, using its nested range id. Current responses have exposed nightly_price; total_price has also been exposed. sort accepts RECOMMENDED, PRICE_LOW_TO_HIGH, PRICE_HIGH_TO_LOW, REVIEW, or REVIEW_COUNT.

The response may contain fewer results than requested when Vrbo returns fewer visible cards. A blocked upstream response or a changed result payload returns an upstream error; an empty result list is returned only when Vrbo provides an explicit no-results response.

Parameters:

• destination (required): selected destination label, e.g. Miami Beach, Florida, United States of America.
• region_id (required): numeric Vrbo region identifier, e.g. 8833.
• lat_long (required): latitude,longitude, e.g. 25.790653,-80.130043.
• check_in (required): check-in date in YYYY-MM-DD format.
• check_out (required): check-out date in YYYY-MM-DD format, after check_in.
• flexibility (optional): currently observed values are 0_DAY (the default) and 3_DAY. The 3_DAY replay returned parser-ready data, but its isolated search effect is unverified. Other intervals and lower/upper bounds are not accepted.
• adults (optional): adult guest count; defaults to 2, capped at 16.
• child_ages (optional): ages 2 through 17 for children in the default single room. The URL represents these as room-indexed ages. Infants (ages 0–1) use separate traveler-form state and are not exposed because the observed URL mapping does not serialize them.
• rooms (optional): list of rooms, each with adults (1–16) and optional child_ages. Use this instead of top-level adults and child_ages for multi-room searches.
• filters (optional): list of { "id", "values" } selections. Copy IDs and values from the live filter options; use an option's id when it differs from its parent group's ID. Values are dynamic and may vary by destination and dates.
• filter_ranges (optional): list of { "id", "min", "max" } ranges. Observed IDs are nightly_price and total_price; use the range IDs returned by Vrbo. total_price comes from a saved first-party response. A fresh Box H replay returned HTTP 200 but no parser-ready search metadata, so its live selected-state behavior remains unverified.
• sort (optional): one of the observed Vrbo sort values listed above.
• limit (optional): maximum results; defaults to 20, capped at 50.

Example request:

{
  "destination": "Miami Beach, Florida, United States of America",
  "region_id": "8833",
  "lat_long": "25.790653,-80.130043",
  "check_in": "2026-10-10",
  "check_out": "2026-10-24",
  "adults": 2,
  "child_ages": [8],
  "filters": [
    { "id": "property_type_group", "values": ["<copy an option value from filters>"] }
  ],
  "filter_ranges": [
    { "id": "nightly_price", "min": 100, "max": 500 }
  ],
  "limit": 10
}

For multiple rooms, replace adults and child_ages with rooms, for example [{"adults":2,"child_ages":[8]},{"adults":1}]. The source page's URL parser maps adult counts by room and each child age to its one-based room index. The current filter inventory includes 19 multi-select groups, eight step inputs, and a price control with multiple captured range options. A live search has exposed nightly_price; a saved first-party response also includes total_price. The response's legacy range field contains the first option; ranges contains all captured options. Filter values are read from live facet data and may vary by destination and dates. Combining filter groups is serialized as separate query parameters, but the full upstream combination matrix is not live-verified. Pet counts are present in traveler-form state but absent from the observed search URL mapping, so they are not exposed.

Live monitoring

Monitored request

POST /vrbo/search

Checks passed, 7 days to 14 Oct 2026

100%

Median response time

5.93 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026

POST /vrbo/search

Items in results

3

Fields filled in every checked item

8

Fields empty in some or all items

1

Shared guides

Related