VRBO logo VRBO API

The VRBO API for vacation-rental discovery and reviews.

Pull listing reviews, ratings, sentiment tags, and host responses from VRBO as clean JSON, and resolve a VRBO listing URL to the property_id required for reviews.

REQUEST GET
USE CASE Native dated discovery; prices omitted and availability not verified.
curl "https://api.stayapi.com/v1/vrbo/search" \
  -G \
  -H "x-api-key: $STAYAPI_KEY" \
  -d "region_id=2693" \
  -d "check_in=2027-02-10" \
  -d "check_out=2027-02-12" \
  -d "adults=2" \
  -d "currency=USD"
RESPONSE 200 OK
2.41s
{
  "count": 0,
  "properties": [],
  "availability_verified": false,
  "next_offset": null,
  "next_limit": null
}
99.9% uptime Live, not cached

Trusted by hospitality teams at

Overview

What the VRBO API gives you.

VRBO has no public data API for the guest reviews vacation-rental managers actually want to track. The usual answer is a scraping stack: headless browsers, rotating proxies, and a parser that breaks every time the listing page changes. VRBO is a vacation-rental marketplace, so the unit is a listing, not a hotel.

StayAPI is that layer, run for you. Resolve a VRBO listing URL with the extract-id endpoint, then send the returned property_id to the reviews endpoint for structured JSON: review text and ratings, sentiment tags like "Great location" and "Clean", verified-stay flags, and host responses. Search results also include a property_id you can send directly to reviews. The same data, the same shape, on every call. Search omits prices and does not confirm availability; native property-name lookup is unavailable.

01

Discovery and listing data.

x-api-key in, JSON out. Listing reviews and URL-to-ID resolution behind one base URL. No SDK to install.

02

We run the hard part.

Fetching, parsing, proxy rotation, and source uptime are ours. You consume normalized JSON and never touch a headless browser.

03

Real-time, not cached.

Every call hits VRBO live, so review counts and host responses are current to the request, not a stale nightly snapshot.

Use cases

What teams build on the VRBO API.

The same endpoints, pointed at different jobs. These are the ones we see most.

01

Review monitoring for rental managers.

Stream new VRBO reviews for every listing you manage into your dashboard, sorted newest-first, with verified-stay flags and host responses attached.

02

Reputation and sentiment analysis.

Run topic clustering and sentiment scoring on the full review text and the VRBO sentiment tags to see what guests praise and what they flag.

03

Comp-set benchmarking for short-term rentals.

Benchmark a listing against nearby rentals on rating and review volume using the same fields for every property_id.

04

AI agents and review context.

Feed structured VRBO review text and ratings into an LLM tool call so your agent answers from live guest feedback, not stale embeddings.

Pricing

50 free requests on signup.
Pick a plan when you need more.

Flat monthly plans, every endpoint included on every plan. 1 request = 1 credit. No per-endpoint multipliers, no surprise overages.

01 Free

Wire it up. See the schema.

$0 to start
50 credits on signup
  • 50 free requests
  • Every endpoint included
  • No credit card required
  • Same schema as paid
Start free
02 Basic

Kick the tires in production.

$49 per month
1,500 requests / mo
  • 1,500 requests / month
  • Every endpoint included
  • Per-endpoint usage dashboard
  • Email support
Start Basic
50% off
04 Scale

Daily pulls in production.

$900 $450 per month
100,000 requests / mo
  • 100,000 requests / month
  • Every endpoint included
  • Per-endpoint usage dashboard
  • Priority email support
Start scaling
05 Custom

Above 100k / month, annual terms, white-glove onboarding.

Let's talk
1M+ requests / mo
  • 1M+ requests / month
  • Volume rate on the call
  • Per-endpoint usage dashboard
  • Priority email + Slack support
Book a scoping call

Every plan ships every endpoint. Same uptime, same schema, same response time.

Questions

What people ask about the VRBO API.

Don't see your question? Email us at info@stayapi.com.

Does VRBO have a public API?

VRBO (part of Expedia Group) has no public data API for pulling guest reviews or listing data. Access is gated and aimed at connectivity partners, not at teams that want review text and ratings over plain REST. StayAPI gives you that data with a key you get in 30 seconds.

How do I get VRBO reviews?

Call /v1/vrbo/listing/reviews/{property_id} with the property_id returned by /v1/vrbo/listing/extract-id or VRBO search. The public listing ID in a VRBO URL may be different. You get paginated review text, ratings on a 1 to 10 scale, sentiment tags, verified-stay flags, and host responses as JSON. Sort with sort_by (recommended, newest, highest, lowest). See the listing reviews docs.

How do I get a VRBO listing ID?

Call /v1/vrbo/listing/extract-id with a VRBO listing URL and use the returned property_id for reviews. For example, https://www.vrbo.com/2351862 resolves to 68762412. Some URLs already contain an ID accepted by reviews; the resolver returns that ID unchanged. Do not assume the URL path is the required ID or remove an alphanumeric suffix. See the extract ID docs.

Is the VRBO API free?

You get 50 free requests on signup, both endpoints included, no credit card. After that it is flat monthly plans starting at $49. One request equals one credit, with no per-endpoint multipliers.

Two ways to start.

Both end with live VRBO data in your stack. The fast path is on the left.

01 · the fast path

Try it free

50 free requests after sign up. Fastest way to see if the schema fits.

Start free
  • Live API key in 30 seconds
  • No credit card required
  • Same schema as paid
02 · the scoped path

Book a scoping call

15 minutes. Volume + endpoint mix. Walk out with a quote.

Book a demo
  • Quote on the call, not after
  • Engineering, not sales
  • No deck, no slides