Booking Reviews Scraper
Under maintenancePricing
from $0.01 / 1,000 review items
Booking Reviews Scraper
Under maintenanceFetch normalized public Booking.com hotel reviews by property URL, including ratings, liked/disliked text, reviewer metadata, stay details, dates, and typed upstream status.
Pricing
from $0.01 / 1,000 review items
Rating
0.0
(0)
Developer
jts
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
17 days ago
Last modified
Categories
Share
What this Actor does
Fetch normalized public Booking.com hotel reviews by property URL, including ratings, liked/disliked text, reviewer metadata, stay details, dates, and typed upstream status.
Input example
Input fields
Provide Booking.com hotel URLs to fetch. Actor is intended for private/authorized data-illustration use; do not use it to resell raw Booking.com review content.
propertyUrls(array, user input): Up to 100 public Booking.com hotel URLs per run.rows(integer, user input): Number of reviews to request per property, from 1 to 100.offset(integer, user input): Review offset for pagination.language(string, user input): Booking locale such as en-us or en-gb.apiBaseUrl(string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.
Output dataset
Each dataset item is one normalized Booking.com review or one typed per-property error.
propertyUrl: Original Booking.com hotel URL.pagename: Booking.com review widget pagename.reviewId: Booking review identifier when available.rating: Review rating.reviewerName: Public reviewer display name.reviewerCountry: Public reviewer indicated country.liked: Positive review section.disliked: Negative review section.publishedAt: Review publication date when parsed.errorType: Typed error for failed property lookups.
Developer notes
Set BOOKING_REVIEWS_SCRAPER_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API.
Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json.
For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.
Run locally
Deploy
