Booking.com Reviews Scraper
Pricing
from $1.95 / 1,000 review scrapeds
Booking.com Reviews Scraper
Scrape Booking.com hotel reviews: reviewer, country, score, liked/disliked text, review and stay dates, room, traveller type, hotel reply, photos, review ID, and hotel score with category ratings. Filter by language, score, traveller type and date. JSON, CSV, Excel.
Pricing
from $1.95 / 1,000 review scrapeds
Rating
5.0
(1)
Developer
Automation Lab
Maintained by CommunityActor stats
0
Bookmarked
97
Total users
12
Monthly active users
3 days ago
Last modified
Categories
Features
Share
Scrape guest reviews from any hotel on Booking.com. Each review comes with the reviewer's name and country, score, liked and disliked text, review date, check-in and check-out dates, room, traveller type, the hotel's reply, guest photos and a stable review ID. Every row also carries the hotel's overall score, total review count and category scores (Staff, Cleanliness, Location, Value for money and more).
Features
- Multiple hotels in a single run -- provide a list of Booking.com hotel URLs
- All the reviews you ask for -- pages through Booking.com's review list 25 at a time until your limit or the last review
- Booking.com's own filters -- language, review score band (Superb, Good, Passable, Poor, Very poor) and traveller type (families, couples, groups, solo, business), applied before paging, so the limit counts only matching reviews
- Only new reviews -- set
cutoffDateto collect reviews written since a date; ideal for scheduled monitoring - Sort options -- relevance, newest/oldest first, or highest/lowest scores
- Rich data -- 29 fields per review, including hotel replies, exact stay dates, review language, photos and hotel category scores
- Reliable -- if Booking.com withholds the review list from one session, the hotel is retried in a fresh session and through Apify Proxy
- Clear results -- the run status says how many reviews were saved against your limit, and runs that could not reach Booking.com fail instead of returning an empty dataset
- Pay per result -- you pay for the reviews you get; invalid input and runs that could not reach Booking.com cost nothing
- Export -- download results in JSON, CSV, Excel, or connect via API
Input
| Field | Type | Default | Description |
|---|---|---|---|
hotelUrls | Array of strings | (required) | Booking.com hotel URLs to scrape reviews from |
maxReviews | Integer | 50 | Maximum reviews per hotel (0 = every matching review) |
sortBy | String | most_relevant | Sort order: most_relevant, newest_first, oldest_first, highest_scores, lowest_scores |
cutoffDate | String | (none) | Only reviews written on or after this date (YYYY-MM-DD); sorts newest first |
language | String | all | Only reviews in this language (en, de, fr, es, it, pt-br, ja, zh, etc.) |
scoreFilter | String | all | Score band: superb (9+), good (7-9), passable (5-7), poor (3-5), very_poor (1-3) |
travellerType | String | all | families, couples, groups, solo or business |
How to get hotel URLs
- Go to Booking.com
- Search for a hotel or city
- Click on a hotel to open its page
- Copy the URL from your browser
The URL should look like: https://www.booking.com/hotel/gb/the-savoy.html
Example input
{"hotelUrls": ["https://www.booking.com/hotel/gb/the-savoy.html","https://www.booking.com/hotel/us/the-plaza.html"],"maxReviews": 50,"language": "en","sortBy": "newest_first","cutoffDate": "2026-01-01","travellerType": "couples"}
Output
Each review is output as a JSON object with the following fields:
| Field | Type | Description |
|---|---|---|
hotelName | String | Hotel name as shown on Booking.com |
hotelUrl | String | Hotel URL from your input |
hotelId | Integer | Booking.com hotel ID |
hotelScore | Number | Hotel overall score (1-10) |
hotelReviewCount | Integer | Total reviews the hotel has on Booking.com |
hotelCategoryScores | Object | Category scores, e.g. {"Staff": 9.7, "Location": 9.8} |
reviewId | String | Stable Booking.com review ID (use it to de-duplicate) |
reviewerName | String | Name of the reviewer |
reviewerCountry | String | Country of the reviewer |
reviewerCountryCode | String | Reviewer country as a 2-letter code |
isAnonymous | Boolean | True when the review was posted anonymously |
score | Number | Review score from 1 to 10 |
title | String | Review title/headline |
positive | String | What the guest liked |
negative | String | What the guest disliked |
reviewDate | String | When the review was posted (e.g., "November 15, 2026") |
reviewedAt | String | When the review was posted, ISO timestamp |
reviewLanguage | String | Language of the review text |
stayDate | String | Month and year of the stay (e.g., "November 2026") |
checkInDate | String | Check-in date (YYYY-MM-DD) |
checkOutDate | String | Check-out date (YYYY-MM-DD) |
nightsStayed | Integer | Number of nights stayed |
roomType | String | Room booked |
roomId | Integer | Booking.com room ID |
travellerType | String | Couple, Family, Group, Solo traveller, Business traveller |
helpfulVotes | Integer | Readers who marked the review helpful |
propertyResponse | String | The hotel's public reply, or null |
photos | Array | Guest photo URLs |
scrapedAt | String | ISO timestamp when the review was scraped |
Values Booking.com does not show are null (or an empty string for text the guest left blank).
Example output
{"hotelName": "The Savoy","hotelUrl": "https://www.booking.com/hotel/gb/the-savoy.html","hotelId": 280149,"hotelScore": 9.4,"hotelReviewCount": 1408,"hotelCategoryScores": { "Staff": 9.7, "Cleanliness": 9.8, "Location": 9.8, "Value for money": 8.5 },"reviewId": "e8d08daf98664484","reviewerName": "David","reviewerCountry": "United Arab Emirates","reviewerCountryCode": "AE","isAnonymous": false,"score": 10,"title": "Excellent and it will be my always option in London","positive": "Everything was excellent","negative": "Nothing","reviewDate": "November 15, 2026","reviewedAt": "2026-11-15T12:52:06.000Z","reviewLanguage": "en-us","stayDate": "November 2026","checkInDate": "2026-11-13","checkOutDate": "2026-11-14","nightsStayed": 1,"roomType": "Superior Queen Room","roomId": 28014901,"travellerType": "Couple","helpfulVotes": 0,"propertyResponse": null,"photos": ["https://q-xx.bstatic.com/xdata/images/xphoto/max1280x900/769649111.jpg?k=f92438a6f8a6f97ac866a8c4b277d409c508f0b1ac9f9611cd60894128d815c5&o="],"scrapedAt": "2026-11-16T11:40:36.305Z"}
How much does it cost?
The scraper uses a pay-per-result pricing model:
| Event | Price |
|---|---|
| Run started | $0.01 (one-time per run) |
| Review scraped | $0.003 per review |
Example costs:
- 50 reviews from 1 hotel: $0.01 + (50 x $0.003) = $0.16
- 100 reviews from 2 hotels: $0.01 + (100 x $0.003) = $0.31
- 500 reviews from 5 hotels: $0.01 + (500 x $0.003) = $1.51
The run-start fee is charged once per run. Invalid input and runs that could not reach Booking.com cost nothing. Platform usage is included in these prices.
Use cases
Hotel market research
Compare guest satisfaction across competing hotels in the same area. Analyze what guests like and dislike about each property to identify competitive advantages.
Sentiment analysis
Feed review data into NLP tools to analyze guest sentiment trends over time. Track how renovations, management changes, or seasonal factors affect reviews.
Travel planning
Collect reviews for hotels you're considering to make informed booking decisions. Filter by language to find reviews from travellers who share your background.
Hospitality benchmarking
Monitor review scores and common complaints across your hotel portfolio. Identify properties that need attention and track improvement over time.
Content creation
Gather authentic guest feedback for travel blogs, hotel comparison sites, or recommendation engines.
Build travel content workflows with structured accommodation reviews
Use Booking.com Reviews Scraper after collecting hotel URLs with Booking.com Scraper to enrich programmatic destination pages, travel affiliate sites, hotel comparison workflows, and AI-assisted CMS drafts with guest scores, positive/negative comments, stay dates, room types, traveller types, and language-filtered review text.
Supported URL formats
The scraper accepts standard Booking.com hotel URLs:
https://www.booking.com/hotel/gb/the-savoy.htmlhttps://www.booking.com/hotel/us/the-plaza.htmlhttps://www.booking.com/hotel/fr/hotel-le-bristol-paris.htmlhttps://www.booking.com/hotel/it/hassler-roma.html?aid=12345&label=testhttps://www.booking.com/hotel/fr/hotel-le-bristol-paris.en-gb.html
The scraper extracts the country code and hotel identifier from the URL path. Query parameters and language suffixes are handled automatically.
Language codes
Common language filter values:
| Code | Language |
|---|---|
all | All languages (default) |
en | English |
de | German |
fr | French |
es | Spanish |
it | Italian |
pt | Portuguese |
ja | Japanese |
zh | Chinese |
ko | Korean |
ru | Russian |
ar | Arabic |
nl | Dutch |
pl | Polish |
sv | Swedish |
Tips
- Start small: Test with
maxReviews: 10to verify the data format meets your needs before running larger scrapes. - Use language filter: If you only need English reviews, set
language: "en"to skip reviews in other languages and reduce run time. - Sort by newest: Use
sortBy: "newest_first"to get the most recent reviews first. Useful for monitoring. - Multiple hotels: You can scrape reviews from multiple hotels in a single run. The scraper processes them sequentially.
- URL format: Make sure your URLs follow the pattern
https://www.booking.com/hotel/{country_code}/{hotel-slug}.html.
Who is it for?
This actor is useful for hospitality analysts, hotel owners, travel-tech teams, reputation managers, travel bloggers, and data teams that need structured Booking.com guest feedback without manually opening each property page.
API usage
Run the actor from code with the same input you use in the Apify Console.
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('automation-lab/booking-reviews-scraper').call({hotelUrls: ['https://www.booking.com/hotel/gb/the-savoy.html'],maxReviews: 20,language: 'all',sortBy: 'most_relevant',});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
from apify_client import ApifyClientimport osclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('automation-lab/booking-reviews-scraper').call(run_input={'hotelUrls': ['https://www.booking.com/hotel/gb/the-savoy.html'],'maxReviews': 20,'language': 'all','sortBy': 'most_relevant',})items = client.dataset(run['defaultDatasetId']).list_items().itemsprint(items)
cURL
curl -X POST "https://api.apify.com/v2/acts/automation-lab~booking-reviews-scraper/runs?token=$APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"hotelUrls":["https://www.booking.com/hotel/gb/the-savoy.html"],"maxReviews":20,"language":"all","sortBy":"most_relevant"}'
MCP
You can call this actor from Apify MCP-compatible agents by selecting automation-lab/booking-reviews-scraper and passing the input JSON above. This is helpful when an AI workflow needs fresh hotel review evidence before summarizing sentiment, extracting complaints, or comparing properties.
Claude Code
$claude mcp add --transport http booking-reviews "https://mcp.apify.com/?tools=automation-lab/booking-reviews-scraper"
Claude Desktop, Cursor, and VS Code
Add this server block to the MCP configuration for Claude Desktop, Cursor, or VS Code:
{"mcpServers": {"booking-reviews": {"url": "https://mcp.apify.com/?tools=automation-lab/booking-reviews-scraper"}}}
Example prompts showing MCP usage
- "Using the Apify MCP server, run
automation-lab/booking-reviews-scraperforhttps://www.booking.com/hotel/gb/the-savoy.htmland summarize the top guest complaints." - "Use MCP to collect 20 Booking.com reviews for these two hotel URLs and compare their staff and location sentiment."
- "Call the Booking.com Reviews Scraper through MCP for my hotel shortlist, then return a table with score, reviewer country, and positive/negative text."
Error reporting
When a run fails, the Actor sends sanitized diagnostic information (the error, a scrubbed copy of the input with secret fields and URL query strings removed, and the Actor, build and run IDs) to our private GlitchTip service so we can fix it. Reports are kept for 30 days.
Legality
This actor extracts publicly available Booking.com review information. Use the data responsibly, respect Booking.com's terms, avoid collecting personal data you do not need, and comply with privacy laws that apply to your use case. If you publish analysis based on reviews, aggregate or anonymize where appropriate.
Related actors
- Booking.com hotel/property scrapers for discovering hotel URLs before collecting reviews
- Tripadvisor review scrapers for cross-platform hotel reputation analysis
- Google Maps review scrapers for local hospitality benchmarking
Integrations
Connect Booking.com Reviews Scraper with your existing tools:
- Google Sheets -- automatically export reviews to a spreadsheet
- Slack -- get notified when new reviews are scraped
- Zapier / Make -- build automated workflows with review data
- API -- access results programmatically via the Apify API
- Webhooks -- trigger actions when a scraping run completes
Limitations
- Only public reviews that Booking.com shows on the hotel page are available. Removed or private reviews are not.
- Booking.com shows up to about the latest few thousand reviews per hotel and filter; very old reviews may not be reachable.
- Hotels are processed one after another. A run with many hotels and
maxReviews: 0can take a while; raise the run timeout if needed.
FAQ
Q: Can I scrape reviews for any hotel on Booking.com? A: Yes, as long as you have the hotel's Booking.com URL, you can scrape its public reviews.
Q: How many reviews can I scrape?
A: There is no hard limit. Set maxReviews to 0 for unlimited. The scraper will paginate through all available reviews.
Q: Can I filter reviews by score?
A: Yes. Set scoreFilter to superb, good, passable, poor or very_poor. Booking.com applies the filter, so maxReviews counts only matching reviews.
Q: How do I collect only new reviews?
A: Set cutoffDate to the date of your last run (for example 2026-11-01). The scraper sorts newest first and stops at the first older review. Use reviewId to de-duplicate across runs.
Q: How fresh is the data?
A: Reviews are scraped in real-time from Booking.com. The scrapedAt timestamp shows exactly when each review was collected.
Q: Can I run this on a schedule? A: Yes! Use Apify's scheduling feature to run the scraper daily, weekly, or at any interval to monitor new reviews.
Q: What happens if a hotel URL is invalid? A: The scraper skips URLs that are not Booking.com hotel pages and says so in the run status. If none of the URLs is valid, the run fails at once and nothing is charged.
Q: Do I need a Booking.com account? A: No. The scraper extracts publicly available review data. No login or account is required.
Q: Can I combine this with other Apify actors? A: Absolutely. Use the Booking.com Scraper to find hotel URLs, then feed them into this Reviews Scraper for detailed review data. Chain actors together using Apify's API or integration tools.