Wire it up. See the schema.
- 100 free requests on signup
- Every endpoint included
- No credit card required
- Same schema as paid
A quick demo might save your team weeks of engineering work.
Resources
Free Tools
Pull listing reviews, ratings, sentiment tags, and host responses from VRBO as clean JSON, and resolve any VRBO URL to a property_id.
curl "https://api.stayapi.com/v1/vrbo/listing/reviews/19006312" \ -G \ -H "x-api-key: $STAYAPI_KEY" \ -d "page=1" \ -d "page_size=10" \ -d "sort_by=newest"
curl "https://api.stayapi.com/v1/vrbo/listing/extract-id" \ -G \ -H "x-api-key: $STAYAPI_KEY" \ -d "url=https://www.vrbo.com/19006312?arrival=2025-01-01"
{
"property_id": "19006312",
"total_reviews": 15,
"page": 1,
"page_size": 10,
"has_more": true,
"sort_by": "newest",
"reviews": [
{
"id": "review_123456",
"rating": 10,
"rating_text": "Excellent",
"title": "Perfect beach getaway!",
"text": "This property exceeded all our expectations. The views were stunning and the host was incredibly helpful throughout our stay.",
"reviewer_name": "Sarah J.",
"verified": true,
"sentiments": [
"Great location",
"Clean",
"Responsive host"
],
"host_response": "Thank you so much for your wonderful review! We're thrilled you enjoyed your stay."
}
]
}
{
"success": true,
"property_id": "19006312",
"url": "https://www.vrbo.com/19006312?arrival=2025-01-01"
}
Trusted by hospitality teams at
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. You send a property_id or a VRBO listing URL and get structured JSON back: review text and ratings, sentiment tags like "Great location" and "Clean", verified-stay flags, and host responses. The same data, the same shape, on every call. This is a reviews and id-resolution API, and we say so plainly.
x-api-key in, JSON out. Listing reviews and URL-to-ID resolution behind one base URL. No SDK to install.
Fetching, parsing, proxy rotation, and source uptime are ours. You consume normalized JSON and never touch a headless browser.
Every call hits VRBO live, so review counts and host responses are current to the request, not a stale nightly snapshot.
Each returns normalized JSON in the same shape. Click any endpoint for parameters, an example response, and a live playground.
The same endpoints, pointed at different jobs. These are the ones we see most.
Stream new VRBO reviews for every listing you manage into your dashboard, sorted newest-first, with verified-stay flags and host responses attached.
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.
Benchmark a listing against nearby rentals on rating and review volume using the same fields for every property_id.
Feed structured VRBO review text and ratings into an LLM tool call so your agent answers from live guest feedback, not stale embeddings.
Flat monthly plans, every endpoint included on every plan. 1 request = 1 credit. No per-endpoint multipliers, no surprise overages.
Wire it up. See the schema.
Kick the tires in production.
Small prod workloads and growing apps.
Daily pulls in production.
Above 100k / month, annual terms, white-glove onboarding.
Every plan ships every endpoint. Same uptime, same schema, same response time.
Don't see your question? Email us at info@stayapi.com.
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.
Call /v1/vrbo/listing/reviews/{property_id} with a VRBO property_id. 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.
Call /v1/vrbo/listing/extract-id with any VRBO listing URL and it returns the property_id, query strings and all. The ID also sits in the URL path itself, for example https://www.vrbo.com/19006312 resolves to 19006312. See the extract ID docs.
You get 100 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.
Both end with live VRBO data in your stack. The fast path is on the left.
100 free requests after sign up. Fastest way to see if the schema fits.
Start free15 minutes. Volume + endpoint mix. Walk out with a quote.
Book a demo