How to scrape flight and hotel prices from Skyscanner, Booking.com, and Google Flights in 2026. Covers proxy strategy, Python code, anti-bot bypass, geo-pricing, and building a fare alert system.
Flight and hotel prices change hundreds of times per day. Airlines and OTAs (online travel agencies) run dynamic pricing engines that adjust fares based on demand, time-to-departure, competitor pricing, and even your browsing history. To monitor prices at scale — whether you're building a fare alert tool, a hotel rate aggregator, or a travel intelligence platform — you need proxies.
Without them, you'll get blocked within minutes.
This guide covers how travel pricing works, which sites block scrapers (and how), the right proxy strategy, and working Python code for Skyscanner, Booking.com, and Google Flights.
Travel sites have more incentive than almost any other industry to block scrapers:
Revenue protection: Bots that compare fares hurt dynamic pricing strategies OTA agreements: Airlines restrict third-party aggregation in contracts API monetization: Amadeus, Sabre, and Travelport charge for the same data via APIs Legal pressure: Some OTAs pursue bot operators under the CFAA
The result is a layered defense stack:
| Detection Layer | Technique | What It Catches | |---|---|---| | IP reputation | ASN + CIDR blacklists | Datacenter / VPS IPs | | Rate limiting | Token bucket per IP | Automated bursts | | Browser fingerprint | Canvas, WebGL, fonts | Headless Chrome | | Behavioral analysis | Mouse, scroll, timing | Non-human patterns | | Fare encryption | JS-generated tokens | Raw API calls | | CAPTCHA | hCaptcha, Cloudflare Turnstile | Unattended scrapers | | Price cloaking | Different prices by IP | Proxy detection |
Residential proxies are the minimum. Datacenter IPs are blocked by every major OTA. For high-volume or high-value targets (Google Flights, Booking.com), mobile proxies give the best success rate because:
Mobile IPs appear as real traveler searches on phones Travel apps are mobile-first — mobile UAs get more lenient treatment Carrier NAT hides you among thousands of real users
| Target Site | Min. Proxy Tier | Notes | |---|---|---| | Google Flights | Mobile / ISP residential | Heavy bot protection, Cloudflare | | Skyscanner | Residential | Rate limits by IP + fingerprint | | Booking.com | Residential / Mobile | Geo-pricing — use country-matched IPs | | Kayak | Residential | Aggressive CAPTCHA on bursts | | Expedia | Residential | Cookie + session binding | | Airbnb | Residential | GraphQL API, token rotation needed | | Direct airline sites | Mobile | Most strict — AA, UA, Delta all use Akamai Bot Manager |
Skyscanner uses an internal JSON API that the web app calls. It's rate-limited but accessible with residential IPs and a proper Chrome TLS fingerprint.
Booking.com renders prices client-side and uses heavy bot detection. Playwright with a mobile user agent and residential/mobile proxies gives the most reliable results.
Google Flights makes internal API calls to https://www.google.com/travel/flights/.... The trick is intercepting network requests during page load to grab the JSON response directly — much faster than DOM parsing.
The real value isn't a one-time scrape — it's tracking price changes over time to catch deals.
| System | Used By | Bypass Strategy | |---|---|---| | Cloudflare Bot Management | Most OTAs | curl_cffi Chrome TLS + residential IP | | Akamai Bot Manager | Airlines (AA, Delta, United) | Mobile proxy + full browser rendering | | DataDome | Kayak, Expedia | Playwright + real mouse movement simulation | | PerimeterX | Some OTAs | Mobile proxy rotation, no headless detection | | hCaptcha / Turnstile | Booking.com | Avoid triggering (slow down, use real UA) |
Key rules: Never scrape from the same IP twice within 10 minutes on aggressive sites Always use geo-matched proxies (US proxy for US prices, EU for EUR prices) Use a full browser (Playwright) for Akamai/DataDome targets — pure HTTP won't work Randomize delays between 5–20 seconds for price monitoring (not real-time)
Travel sites show different prices based on your IP's country. This is intentional:
Booking.com shows hotel prices in local currency and adjusts fees by market Airlines show different base fares for US vs. EU vs. APAC IPs (legal requirement + pricing strategy) Google Flights adjusts results based on locale and inferred location
For accurate price monitoring, always use a proxy from the user's target country. A Paris hotel search from a US IP may show 15–25% higher prices than from a French IP.
Travel fare scraping in 2026 requires:
Residential or mobile proxies — datacenter IPs are blocked universally curlcffi for direct API calls — Python requests gets flagged by TLS fingerprinting Playwright** for JavaScript-heavy pages (Booking.com, Google Flights)