-
Booking's own review digest on hotel records (reviewSummary): what guests praise and complain about, each point with its topic, how many reviews mention it and the sentiment. No other Booking.com scraper on the store returns this.
-
Per-category review scores on hotel details (categoryScores) - Staff, Facilities, Cleanliness, Comfort, Value for money, Location and Free WiFi, each with the destination average it is measured against. Previously these only came out of Reviews mode; Hotel details / All now carry them at no extra request.
-
Price calendar summary (Prices mode with "days ahead"): one extra row per hotel with minPricePerNight, avgPricePerNight, maxPricePerNight, cheapestDate, mostExpensiveDate, availableDays, soldOutDays, occupancyRate and the first/last bookable date - rate-shopping and occupancy tracking without post-processing the day-by-day rows. Derived from rows that were already billed, so the summary itself is free.
-
Bookable deep links (bookingUrl) on every property, price, hotel, review and host record: the hotel page with the dates, guests, rooms and currency pre-filled, so the link opens on the same availability the record was priced against.
-
Record provenance (searchQuery / inputUrl): every row now says which destination or input URL produced it, so multi-destination runs can be split without guessing.
-
New hotel-detail signals: Travel Proud (LGBTQ+ friendly) badge, breakfast score and its review count, bed-comfort review count, guest-question count, whether the property opted out of Q&A, its average answer time, brand logo, photo and room-type counts, single-type-property, third-party-exclusive and property-booked flags.
-
Reviews now carry stayDate ("August 2026") and an explicit isAnonymous flag.
-
Prices now include the hotel url and discountPercentage; search results include discountPercentage too.
-
Much cheaper runs: the Actor now uses Apify's datacenter proxy by default instead of residential. Booking.com serves datacenter egress fine once the built-in AWS WAF challenge is solved, and datacenter transfer is not billed per GB - this removes ~97% of the platform cost of a run. If datacenter IPs get blocked, the Actor escalates to residential automatically mid-run, so results are unaffected.
-
Reviews mode is dramatically faster and lighter: review pages are now pulled straight over GraphQL using the tokens from the search page, so scraping reviews for N hotels downloads one page instead of N. A ~1.5 MB property page per hotel is no longer fetched at all when the hotels come from a search query.
-
Fixed: pay-per-event charges were being dropped silently when the charging API rejected a call, so runs could return data without billing for it. Charges are now batched, reported in the run log ("Billed events: ...") and any failure is logged as a warning instead of being swallowed.