Booking.com Attraction Reviews Scraper

Pull guest reviews for a single tour or activity product (the same product id you see in attractions search results). Each row is one review with rating, text, language, travel-party hints, and reviewer info when available—useful for CX, quality, and partner reporting.

Who it’s for

• Operations & experience teams monitoring feedback on a specific experience.
• Product & partnerships roles tracking sentiment for one listing.
• Analysts who need structured exports instead of reading the page.

What you can do with it

• Collect many reviews across pages until you hit your cap.
• Join with search exports using productId on each row (the attraction product you queried). The review’s own identifier is the id field on that row—do not confuse it with the product id.

How it works (in plain terms)

You pass the attraction product id from searchAttractions (data.products[].id). The tool requests page 1, 2, … of reviews and stops when a page has no reviews or you reach your maximum row count.

Input

Field	Required	What it means
Product ID (id)	Yes	The experience id from the attractions search payload.
Maximum results (maxResults)	No	Upper limit on how many reviews to collect (default 100).

Output

• One row per review until your cap or the end of results.
• Review identity: id — Booking’s review id for this row (distinct from the product id).
• Text & score: content — full review text when provided (may be null); numericRating — star-style score; language — tag such as en-gb when detected.
• Timing: epochMs — review time in milliseconds since Unix epoch (convert for reporting as needed).
• Context: travelPartnerTypes — e.g. partner, family, alone; providerName — often null unless a specific provider label is returned.
• Reviewer: user — name, cc1 (country code), avatar (URL or null).
• Actor fields: productId — repeats the attraction product id you passed in; scrapedAt — when this row was written to your dataset.

Some reviews may omit content or user depending on source and platform rules.

Sample output (one dataset row)

{
  "content": "Highly recommend this tour to see a real side of Mumbai with a knowledgeable guide (Maze) who was fantastic. Changed our perspective on the slums, and fascinating to see the laundry.",
  "epochMs": 1769684730000,
  "id": "RSaDusGILZst",
  "language": "en-gb",
  "numericRating": 5,
  "providerName": null,
  "travelPartnerTypes": ["partner"],
  "user": {
    "avatar": null,
    "cc1": "gb",
    "name": "Chris"
  },
  "productId": "PR6K7ZswbGBs",
  "scrapedAt": "2026-03-25T06:19:56.648Z"
}

Good to know

• The product id must match a real attraction listing; wrong ids return empty or errors.
• Some reviews may have null text or user depending on source and platform rules.
• Use data in line with Booking.com’s terms and applicable laws.