Booking.com Reviews Scraper

Scrape all guest reviews from any Booking.com hotel page — liked/disliked text, score, date, room type, length of stay — plus the hotel's management responses, which most alternatives don't return.

Why this scraper

• ✅ Every review, not just the first ~30 — pagination runs to the end of the feed.
• ✅ A date filter that actually works — collect only reviews after (or before) a date, accurately.
• ✅ Management responses included — the hotel's official replies, which most scrapers drop.
• ✅ No blocking to deal with — residential proxies and anti-bot handling are built in and on by default.
• ✅ Lower price — $0.80 per 1,000 reviews.

What it does

• Full set of reviews. Pagination runs to the end of Booking's review feed, not just the first ~30 reviews. The Actor reads the hotel's total review count up front and collects every available review.
• Working date filter (cutoffDate). Collect only reviews newer (or older) than a given date — accurately, without over-fetching. Works with date sorting.
• Management responses (ownerResponse). The hotel's official reply to a review, whenever one exists.
• Flexible sorting and score filter. Sort by newest, oldest, score, or relevance; keep only the score bands you care about (e.g. superb only, poor only).
• Reliable by design. Runs through a real browser with Apify residential proxies and session rotation, so Booking's anti-bot blocks are handled automatically.

How to use

1. Open a hotel on Booking.com and copy its page URL from the browser address bar.
2. Paste one or more such URLs into Booking.com hotel URLs.
3. Optionally set how many reviews to collect, the sort order, a cutoff date, or a score filter.
4. Click Start and wait for the run to finish.
5. Download the results from the Output tab in JSON, CSV, Excel, XML, or HTML.

Input

Field	Type	Description
startUrls	array	Booking.com hotel page URLs (required).
maxReviewsPerHotel	integer	Max reviews per hotel. 0 — all available (default). Set a number to cap how many you collect (and how much you pay).
sortReviewsBy	enum	newest / oldest / highest_score / lowest_score / relevance. Default newest.
cutoffDate	string	Date boundary. With newest keeps reviews newer than the date; with oldest, older than it. Ignored for other sort orders.
reviewScores	array	Score bands to keep: ALL, REVIEW_ADJ_SUPERB (9+), REVIEW_ADJ_GOOD (7–8.9), REVIEW_ADJ_AVERAGE_PASSABLE (5–6.9), REVIEW_ADJ_POOR (3–4.9), REVIEW_ADJ_VERY_POOR (below 3). Empty or ALL — all scores.
proxyConfiguration	object	Proxy. Defaults to Apify Residential.
customData	object	Arbitrary JSON attached to every output record.

Example input:

{
  "startUrls": [
    { "url": "PASTE_BOOKING_HOTEL_URL_HERE" }
  ],
  "maxReviewsPerHotel": 0,
  "sortReviewsBy": "newest",
  "reviewScores": ["ALL"]
}

Output (per review)

Each collected review is one record in the dataset, including the management response (ownerResponse) when the hotel has replied.

Example records (from The Ritz London):

[
  {
    "id": "21d1476578ab253e",
    "hotelId": "gb/the-ritz-london",
    "hotelIdNumeric": "280539",
    "reviewPage": 1,
    "userName": "James",
    "userLocation": "United States",
    "roomInfo": "Deluxe Room",
    "stayDate": {
      "checkin": "2026-06-04",
      "checkout": "2026-06-10"
    },
    "nights": 6,
    "reviewDate": 1781167842,
    "reviewDateIso": "2026-06-11T08:50:42.000Z",
    "reviewTitle": "Wonderful but a bit pricey",
    "rating": 10,
    "reviewTextParts": {
      "Liked": "Immaculate room, attentive staff",
      "Disliked": "Nothing"
    },
    "customData": {},
    "ownerResponse": "Dear James,\n\nThank you for your kind review. We are delighted to read that you enjoyed your stay with us. We hope to welcome you back to The Ritz soon.\n\nBest regards,\nDuty Managers, The Ritz London",
    "helpfulVotesCount": 0,
    "isApproved": true,
    "reviewLanguage": "xu",
    "guestType": "Solo traveler",
    "countryCode": "us"
  },
  {
    "id": "e1c2562a4024fc70",
    "hotelId": "gb/the-ritz-london",
    "hotelIdNumeric": "280539",
    "reviewPage": 1,
    "userName": "Hakan",
    "userLocation": "Turkey",
    "roomInfo": "Junior Suite",
    "stayDate": {
      "checkin": "2026-04-23",
      "checkout": "2026-04-26"
    },
    "nights": 3,
    "reviewDate": 1777709921,
    "reviewDateIso": "2026-05-02T08:18:41.000Z",
    "reviewTitle": "Wonderful Stay",
    "rating": 10,
    "reviewTextParts": {
      "Liked": "Wonderful stay as always. Very best hotel, at the very best location, with the very best and smiling staff.",
      "Disliked": "Nothing."
    },
    "customData": {},
    "ownerResponse": "Dear Hakan,\nThank you for your feedback regarding your recent stay with us.\nWe hope to welcome you back in the near future.\nBest regards,\nDuty Managers, The Ritz London",
    "helpfulVotesCount": 0,
    "isApproved": true,
    "reviewLanguage": "xu",
    "guestType": "Family",
    "countryCode": "tr"
  }
]

Proxy and cost

The Actor is billed pay-per-event: $0.80 per 1,000 reviews collected, and nothing else — no charge for run time or platform usage.

Booking.com blocks datacenter IPs, so the Actor uses residential proxies (Apify Residential by default). Proxy traffic is billed to the account that runs the Actor.

Is it legal to scrape Booking.com reviews?

The Actor only reads information that guests have already chosen to publish on Booking.com — review text, score, room type, stay dates, the reviewer's display name, and the management reply. It does not log in, bypass any access restriction, or collect hidden or private data such as email addresses or profile photos. In the United States, courts have held that scraping publicly accessible pages without logging in generally does not break computer-access law (the CFAA), but that is not the whole picture: a site's Terms of Service may still restrict scraping as a matter of contract, copyright can apply to the text of individual reviews, and the rules differ by jurisdiction and by what you do with the results.

A review and its display name can also count as personal data under laws such as the GDPR, even when published publicly. You are responsible for having a lawful basis to collect and use it. The Actor keeps the output to publicly shown, non-identifying fields and does not collect contact details, exact addresses, or profile photos.

This is general information, not legal advice. If you are unsure whether your use case is allowed, check with a lawyer.

Your feedback

This Actor is actively maintained. If you hit a bug, notice a change on Booking.com that breaks the output, or want a new field or option, open an issue on the Issues tab of this Actor — it goes straight to the developer.