Airbnb vacation rental guest reviews by URL, id or place. One row per review: rating, text, host replies, translation, language, date, reviewer, location. Lowest rated first and minRating keep only negative reviews (complaints) and bill only those. For sentiment, reputation, competitor research.
2026-10-16 — Keyword Planner and locale documentation
Validated search terminology against Google Ads Keyword Planner and Store shelves. Added localized usage guidance and bounded examples; retained existing English phrases. Clarified locale limitations where measured. No runtime, output fields, defaults, or pricing changed.
1.2 — listing and input form reworded, 2026-10-11
No behaviour, output or price changed; the same inputs return the same rows.
Title: "Guest Reviews" and "Ratings" kept; "Replies" became "Host Replies", the phrase people type.
Description says what one row is (star rating, text, translation, language, date, reviewer, location, host reply), the three ways in, that lowest-rated-first and minRating keep only complaints and bill only those, and the research it serves (sentiment, reputation, competitors).
Input form: proxyConfiguration moved next to sessions and perIp; captions say where the bill is decided. Nothing was renamed or removed.
Every input now says what to pass, with an example, its default, what it changes and what it costs.minRating says in capitals that it keeps reviews AT OR BELOW the rating and quotes the measured 441 → 4 rows; maxReviewsPerListing states the per-review price and the verified 300 from one listing; startUrls says a search URL harvests every listing it returns.
The pricing text lists what is never charged, that each review is billed once per run, that there is no start fee, and that a run stops at the maximum cost you set.
README: a section mapping common requests to the exact input and the status contract, including what the actor does not do (no "since a date" filter, stays only). seoDescription carries host replies, negative reviews and the Spanish, German and French words for reviews.
1.2 — 2026-09-24
Fix: Airbnb sometimes answers the reviews request with a cut-down page of 2 reviews whatever the requested count, which ended the listing early (a run asking for 10 reviews per listing delivered 2). That answer now fetches again from a fresh IP, and a short page only ends a listing once its review count is reached, so every requested review is delivered. Billing is unchanged: one charge per delivered review.
2026-08-30
Reliability: a run that cannot act on its input — a URL from the wrong site, a name nothing resolves to, an empty target list, a number outside the documented range — now ends cleanly with the reason on the run card instead of as a failed run. Nothing is charged in either case; a blocked or throttled source still fails loudly.
Store listing: moved into the categories buyers actually browse (the old Business category has no Store page).
1.1 — 2026-08-28
The prefilled input now runs out of the box: a place search for Lisbon capped at 5 listings × 20 reviews (about $0.50 at most, under a minute). Before, the prefilled form had no listing, URL or place, so a "Run" without edits — including Apify's automated quality check — stopped with Invalid input. Defaults for API callers are unchanged.
Example run input aligned with the prefill.
1.0 — 2026-08-26
First release.
Every guest review of any Airbnb listing: rating, the review as written, Airbnb's translation, the language it was written in, reviewer name/id/location, date, stay type and the host's public reply.
Three ways in: listing ids, Airbnb listing or search URLs, or a place name — a place harvests reviews for every listing it returns.
Order by most recent, highest rated, lowest rated or most relevant; minRating keeps only reviews at or below a rating, so a complaints feed costs nothing for the happy ones (filtered reviews are never charged).
Billing: pay per delivered review row. Listing rows, status rows, filtered reviews, listings with no reviews and unrecognised places are all free, and a listing is harvested once per run however many inputs point at it.
Reliability: unrecognised places are reported instead of returning listings from all over the world; per-job failures come back as status rows; runs under limited permissions.
