How to scrape Booking.com in 2026 (complete guide)

Booking.com is the world's reference for accommodation bookings. Its pages concentrate a much sought-after kind of data: room prices, availability and ratings, which vary by date, currency and the visitor's country. That's valuable for price monitoring in travel, but the site keeps a close watch on automated access. Here's how to collect it cleanly.

What data you can collect on Booking

• Prices: rate per night, per room type, by date.
• Availability: rooms left, cancellation conditions.
• Ratings: average score, number of reviews, sub-scores (cleanliness, location).
• Properties: name, location, amenities, photos.

What blocks a naive scraper

Booking runs an anti-bot protection that reacts to the client's behaviour and fingerprint. Too many requests from the same IP, a script fingerprint, an abnormal pace, and the content degrades or a verification page appears. The site is also heavily geolocalised: the displayed price depends on the exit country and the currency, which makes the choice of IP decisive.

On Booking, geolocation is not a detail: without the right exit country, you won't see the same prices as a real local visitor.

How to get the data cleanly

curl -G "https://api.wyndpath.com/v1/" \
  --data-urlencode "api_key=YOUR_KEY" \
  --data-urlencode "url=https://www.booking.com/searchresults.fr.html?ss=Paris" \
  --data-urlencode "render_js=1" \
  --data-urlencode "country=fr"

WyndPath drives a real browser with a French IP, to see prices like a local visitor, and handles rotation and retries. You only pay on success. To browse several dates or pages, keep the same session and space out your requests.

The legal framework

Prices and availability are public, but subject to the site's terms of use and to database rights. Reviews contain personal data (usernames) that falls under the GDPR. Minimise your collection and respect robots.txt. See web scraping and the GDPR in France.