# Booking.com Proxies: 26 Words, 20 Rows in 6 s

> We measured Booking.com through residential proxies: the home page gives a plain client 26 words, the browser 0 words, the collector 20 priced rows in 5.9 s.

[Home](https://quanticdata.io/)/[Blog](https://quanticdata.io/blog/)/Booking.com Proxies: 26 Words, 20 Rows in 6 s

# Booking.com Proxies: 26 Words, 20 Rows in 6 s

Use casesSep 28, 2026·9 min read·By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData

Booking.com measured on 28 September 2026 through residential proxies: 3,962 bytes and 26 words over plain HTTP, 857,992 bytes and 0 words rendered, 20 priced properties in 5.9 seconds from the booking_stays collector

On this page [The search term is asking for a scraper, not a proxy](/blog/booking-proxies/#the-search-term-is-asking-for-a-scraper-not-a-proxy) [26 words without JavaScript, 0 words with it](/blog/booking-proxies/#26-words-without-javascript-0-words-with-it) [What robots.txt and the terms say](/blog/booking-proxies/#what-robots-txt-and-the-terms-say) [The collector returns 20 priced properties in 5.9 seconds](/blog/booking-proxies/#the-collector-returns-20-priced-properties-in-5-9-seconds) [What a gigabyte buys on Booking.com, and what it does not](/blog/booking-proxies/#what-a-gigabyte-buys-on-booking-com-and-what-it-does-not) [The setting that works on Booking.com](/blog/booking-proxies/#the-setting-that-works-on-booking-com)

Booking.com is the one travel site where the proxy on its own returns nothing you can sell. On 28 September 2026 we fetched the home page through residential exits in Italy and the United States: a plain HTTP client received 3,962 bytes and 26 words, a full browser render received 857,992 bytes and zero words of content, and the numbers were identical from both countries. The setting for Booking.com proxies is therefore not a fetch mode. It is the [Booking.com stays collector](https://quanticdata.io/collectors/booking-com-scraper-api/), which returned 20 priced properties for Rome in 5.9 seconds on the same afternoon.

## The search term is asking for a scraper, not a proxy

Google autocomplete has nothing to say about Booking.com proxies: the phrase returns no suggestions in the United States, and "proxies for booking.com" completes to bots, browsing and Ticketmaster. The demand lives one word over. "Booking.com scraper" completes to scraper api, scraping policy, review scraper and price scraper, and the question people actually type is "can you scrape booking com".

The first page for that intent is hosted actors, four scraping-API vendor pages, a GitHub project and two Reddit threads titled, in effect, has anyone managed it. The best of the tutorials is 2,586 words long and correct about the mechanics: find hotel pages through the sitemaps, replicate the search endpoint, pin the proxy country to fix the currency. It never weighs a response. So we did, and the weight is the whole story.

## 26 words without JavaScript, 0 words with it

We audited `booking.com/` twice from an Italian residential exit, once as a pure HTTP client and once fully rendered, then repeated both from the United States.

| Fetch | Exit | Bytes | Words | Title | Canonical |
| --- | --- | --- | --- | --- | --- |
| Plain HTTP | Italy | 3,962 | 26 | none | none |
| Rendered | Italy | 857,992 | 0 | Booking.com \| Sito ufficiale \| I migliori hotel... | /index.it.html |
| Plain HTTP | United States | 3,962 | 26 | none | none |
| Rendered | United States | see note | 0 | Booking.com \| Official site \| The best hotels... | / |

The plain HTTP body is 3,962 bytes and its h1 is the three words "JavaScript is disabled". There is no title tag, no canonical, no description and no JSON-LD. Twenty-six words arrive and not one of them is a hotel, and the response is the same size from Rome and from New York.

Rendering costs 216 times the bytes and 46.7 seconds of browser time, and it returns the head of the page and nothing else: a title, a canonical, zero words in the body. The browser is not a partial answer here. It is a more expensive way to get the same answer. If your pipeline currently opens a headless browser on Booking.com, that line item buys you a title tag.

What the second country shows is the only useful signal the home page gives away: Booking.com localises off the exit IP alone. From Italy the rendered title is Italian and the canonical is `/index.it.html`; from the United States the title is English and the canonical is the root. No Accept-Language header was sent. The site decided from the address, and it makes the same decision about currency, which is why the collector below pins the exit country and the currency explicitly instead of hoping.

## What robots.txt and the terms say

`booking.com/robots.txt` is 39,491 bytes and 684 lines, and most of it is a map. Four hundred and thirty-four lines are `Sitemap:` entries pointing at gzipped indexes for hotels, cities, districts, landmarks, airports and themes. The rule section is thirteen user-agent blocks. Four crawlers are shut out entirely with a bare `Disallow: /`: psbot, TurnitinBot, NPBot and NPBot-1/2.0. Everyone else, including the wildcard, gets 77 disallow lines and 6 allow lines that fence off search fragments, availability endpoints and internal review indexes while leaving the hotel pages themselves crawlable.

The terms are stricter than the robots file. Clause A15.2 of the customer terms, in the Italian version we fetched, says that whether or not you have a commercial purpose you may not access, monitor, copy, extract, download or otherwise use any content on the platform using robots, spiders, scrapers or other automated means, and it names AI assistants that drive a browser as one of those means, without Booking.com's prior written permission. The same clause states that automated means may not be used to make reservations. That is one plain line and we will not argue with it: reading the public site with a script is something Booking.com's terms prohibit, and no proxy setting changes what a contract says.

The licensed route is the Demand API, version 3.1, for affiliate partners: REST over HTTPS POST, JSON responses, a production host at `demandapi.booking.com/3.1` and a sandbox, authenticated with an affiliate ID and token. It covers accommodation search, availability, bookings and reporting. If you are a travel business that can pass the affiliate programme, that is the front door, and it comes with the permission attached.

## The collector returns 20 priced properties in 5.9 seconds

For public price and availability monitoring, competitive sets and market research, we ran the [booking_stays collector](https://quanticdata.io/collectors/booking-com-scraper-api/) once on 28 September 2026 with the input Rome, Italy, check-in 20 October, check-out 22 October, two adults, one room, currency EUR, exit country Italy, up to 20 results. The run resolved the place to 41.89671, 12.48220, finished in 5.9 seconds and delivered 20 properties, none partial.

| Field | What the 20 rows contained |
| --- | --- |
| Two-night price | €440.61 to €4,595.32, every row priced |
| Struck-through price | present on all 20, implied discount 6% to 34% |
| Review score | 6.8 to 9.7 on 18 rows; 2 rows with no reviews yet |
| Distance from the searched point | 20 m to 100 m |
| Star class | 3 hotels (4, 4 and 5 stars); 17 apartments and rooms without one |
| Free cancellation | 5 of 20 |
| Breakfast included | 4 of 20 |
| Rooms left at this price | 1 on 17 rows, 2 on two rows, 3 on one |

Three details in that output matter more than the row count. Every price is for the exact dates you asked for and in the currency you asked for, because the collector sends both; the home page fetch above could not have told you the currency at all. The struck-through price and the discount percentage arrive as separate numeric fields, so the classic parser trap of two prices glued together in one text node does not exist here. And the distance is measured from a point, which means you can pass a street address instead of a city and get the properties around a specific hotel: that is how a competitive set is built, and it is why the run above clustered inside 100 metres of one square.

The other limit is stated on the collector page and worth repeating: it paginates 20 properties per page up to 100 per run. For a whole city you shape the job as many points, not one wide search, which is also what the best tutorial on the SERP recommends and what Booking.com's own result cap forces.

## What a gigabyte buys on Booking.com, and what it does not

Every measurement above came through [residential proxies](https://quanticdata.io/residential-proxies/) on the Basic line at $0.80/GB, and the arithmetic looks like this, counting a gigabyte as 10^9 bytes:

| Request | Bytes | Requests per GB | Cost per request | What you get |
| --- | --- | --- | --- | --- |
| Home page, plain HTTP | 3,962 | 252,397 | $0.0000032 | 26 words, no hotel |
| Home page, rendered | 857,992 | 1,165 | $0.00069 | a title tag |
| booking_stays, one property | billed per row | n/a | $0.02 | price, strike price, score, distance |

The first two rows are the point. A gigabyte of the cheapest residential bandwidth buys a quarter of a million responses to Booking.com that contain nothing, and 1,165 rendered responses that contain a title. The collector is priced per delivered property, failed rows are never billed, and the run above cost $0.40 for 20 rows. Budget by what a request yields, not by what it costs; our note on [how much proxy data you need](https://quanticdata.io/blog/how-much-proxy-data-do-i-need/) does the same arithmetic for targets where the fetch does return content, and [how to price monitor](https://quanticdata.io/blog/how-to-price-monitor/) covers the cadence once the rows are flowing.

Mobile exits at $2.30/GB and ISP addresses at $2.50/IP a month do not change any number in this post. The home page returned the same 26 words to every exit we tried; the barrier was JavaScript and a verification step, not the reputation of the address. Do not buy the expensive network for a surface that never asked about your IP.

## The setting that works on Booking.com

**Network**: residential, Basic line at $0.80/GB, and only underneath the collector; a raw fetch of the site is not worth routing through any network. **Fetch mode**: neither `engine: tls` nor rendered, because they return 26 and 0 words respectively; the fetch that works is the [booking_stays collector](https://quanticdata.io/collectors/booking-com-scraper-api/) at $0.02 per delivered property. **Country to pin**: the market whose prices you want, passed as both the exit country and the currency, because the site localises title, canonical and currency off the IP alone: Italy gave us `/index.it.html` and euros, the United States gave the root and English. **When the proxy is not enough**: on this target that is always, and the collector answered with 20 rows in 5.9 seconds; for rate comparison across sellers, the [Google Hotels collector](https://quanticdata.io/collectors/google-hotels-api/) returns the same stay from the metasearch side, and for anything else on the domain the [web scraping API](https://quanticdata.io/web-scraping-api/) with render is the fallback, with the numbers above telling you what to expect, and every account gets $2 of free API usage per month, which is 100 delivered properties before you pay anything.

The same measurement on the neighbouring platforms lands differently: [Airbnb](https://quanticdata.io/blog/airbnb-proxies/) serves its listings inside a hydration island that a plain fetch can read, and [Kayak](https://quanticdata.io/blog/kayak-proxies/) hands a no-JavaScript client 2,451 words. Booking.com is the one that hands it 26.

### Sources & further reading

- [booking.com/robots.txt (fetched 28 September 2026)](https://www.booking.com/robots.txt)

- [Booking.com customer terms of service, clause A15 intellectual property rights](https://www.booking.com/content/terms.html)

- [Booking.com Demand API 3.1 reference](https://developers.booking.com/demand/docs/open-api/demand-api)

## FAQ

Quick answers on booking.com proxies.

[Something else? Ask us →](mailto:hello@quanticdata.io)

### Can you scrape Booking.com with a residential proxy alone?

Not the site itself. On 28 September 2026 the home page returned 3,962 bytes and 26 words to a plain HTTP client through a residential exit, and 857,992 bytes with zero words of content when rendered, identically from Italy and the United States. The fetch that returns hotel data is the booking_stays collector, which delivered 20 priced properties for Rome in 5.9 seconds.

### Does Booking.com allow scraping?

No. Clause A15.2 of the customer terms prohibits accessing, monitoring, copying or extracting any content with robots, spiders, scrapers or other automated means, including AI assistants that drive a browser, without prior written permission, and separately prohibits automated reservations. robots.txt is 39,491 bytes, publishes 434 sitemap lines and fully blocks 4 named crawlers. The permitted route is the Demand API 3.1 for affiliate partners.

### How do I get Booking.com prices in a specific currency?

Pin the exit country and pass the currency explicitly. The site localises off the IP alone: from an Italian exit the rendered title was Italian and the canonical was /index.it.html, from a United States exit it was English at the root, with no Accept-Language header sent. Our Rome run set country it and currency EUR and every one of the 20 rows came back in euros with a numeric price_value field.

### How much does it cost to monitor Booking.com hotel prices?

The collector is billed at $0.02 per delivered property and failed rows are never charged, so the 20-row Rome run cost $0.40. A gigabyte of Basic residential bandwidth at $0.80 would instead buy 252,397 plain fetches of the home page that contain no hotel, or 1,165 rendered fetches that contain a title, counting 1 GB as 10^9 bytes, and every account gets $2 of free API usage per month, which is 100 properties.

### Does the browser render help on Booking.com?

No. Rendering the home page took 46.7 seconds and 857,992 bytes and returned a title tag, a canonical and zero words in the body, against 26 words for 3,962 bytes over plain HTTP. The browser is 216 times the bytes for the same absence of content. Skip it and route the job through the collector, which reads the page for you.

### How many properties can one Booking.com collector run return?

Up to 100 per run, 20 per page, all within the search radius of a place, an address or a coordinate pair. Our Rome run asked for 20 and delivered 20 within 100 metres of the resolved point, with prices from €440.61 to €4,595.32 for two nights and a struck-through price on every row. For a whole city, run many points rather than one wide query.

## Get the rows, not the shell

The booking_stays collector returned 20 priced properties in 5.9 seconds where a rendered fetch returned none; run it for any place, address or coordinate pair with your own dates and currency. Every account gets $2 of free API usage each month, and failed rows are never billed.

[Start free — $2/month included](https://quanticdata.io/signup/)[Explore Residential Proxies from $0.80/GB](https://quanticdata.io/residential-proxies/)

## Related reading

[Use cases Kayak Proxies: 2,451 Words With No Browser Kayak measured on 28 September 2026 through residential exits in the United States and the United Kingdom. The home page hands a plain HTTP client 2,451 words, an h1, a canonical and three JSON-LD blocks including a four-question FAQPage, for 1,656,272 bytes. A full browser render returns 2,455 words for 2,415,047 bytes and 40.7 seconds. Every tutorial on the SERP opens Selenium first; the measurement says close it. Read →](https://quanticdata.io/blog/kayak-proxies/) [Use cases Skyscanner Proxies: 0 Words, 15 Fares in 34 s Skyscanner measured on 28 September 2026 through residential exits in the United Kingdom and the United States. The home page returns a title, a description, a canonical and a WebSite JSON-LD block, and zero words of body text, to a plain HTTP client and to a full browser alike, in both countries. No fetch mode changes that. The google_flights collector, asked for London Heathrow to New York JFK on 20 October in pounds, returned 15 itineraries in 33.7 seconds. Read →](https://quanticdata.io/blog/skyscanner-proxies/) [Use cases Tripadvisor Proxies: 713 Words Over Plain HTTP Tripadvisor measured on 28 September 2026 through residential exits in the United States and Italy. The home page hands a plain HTTP client 713 words, the h1 "Where to?", a canonical and three kinds of JSON-LD, including 19 LocalBusiness objects with URLs and countries, for 388,397 bytes in 3.6 seconds. From Italy the same URL returns the same English page with 757 words. The browser spends 46 seconds and returns 5,915 bytes. The setting is plain HTTP; the tripadvisor_search collector returned 30 Chicago restaurants in 8.1 seconds. Read →](https://quanticdata.io/blog/tripadvisor-proxies/)

## Also on this site

Quantic**Data**

Residential proxies & web data APIs for AI.

#### Proxies

- [Residential Basic](https://quanticdata.io/residential-proxies/#basic)

- [Residential Premium](https://quanticdata.io/residential-proxies/#plans)

- [Cheap Residential](https://quanticdata.io/cheap-residential-proxies/)

- [Mobile Proxies](https://quanticdata.io/mobile-proxies/)

- [Datacenter Proxies](https://quanticdata.io/datacenter-proxies/)

- [ISP Proxies](https://quanticdata.io/isp-proxies/)

- [Rotating Proxies](https://quanticdata.io/rotating-proxies/)

- [Sneaker Proxies](https://quanticdata.io/sneaker-proxies/)

- [SOCKS5 Proxies](https://quanticdata.io/socks5-proxies/)

- [IPv6 Proxies](https://quanticdata.io/ipv6-proxies/)

- [Proxy locations](https://quanticdata.io/proxies/)

#### Data APIs

- [MCP Server](https://quanticdata.io/mcp-server/)

- [Web Scraper API](https://quanticdata.io/web-scraping-api/)

- [SERP API](https://quanticdata.io/serp-api/)

- [Collectors](https://quanticdata.io/collectors/)

- [Web Data for AI](https://quanticdata.io/web-data-api-for-ai/)

- [Quantic AI](https://quanticdata.io/ai-web-scraping-service/)

- [Crawl & Map](https://quanticdata.io/crawl-map/)

- [SEO Audit](https://quanticdata.io/seo-audit/)

#### Use cases

- [Company data](https://quanticdata.io/scrape-company-data/)

- [Price monitoring](https://quanticdata.io/competitor-price-monitoring/)

- [Market research](https://quanticdata.io/market-research-data/)

- [Real estate data](https://quanticdata.io/real-estate-data-scraping/)

- [Scrape job postings](https://quanticdata.io/scrape-job-postings/)

#### Company

- [Documentation](https://quanticdata.io/docs/)

- [Blog](https://quanticdata.io/blog/)

- [Free tools](https://quanticdata.io/tools/)

- [Partners](https://quanticdata.io/partners/)

- [About](https://quanticdata.io/about/)

- [Alternatives](https://quanticdata.io/alternatives/)

- [Pricing](https://quanticdata.io/pricing/)

- [FAQ](https://quanticdata.io/#faq)

- [For AI agents](https://quanticdata.io/#ai)

#### Free tools

- [All tools](https://quanticdata.io/tools/)

- [Website to Markdown](https://quanticdata.io/tools/website-to-markdown/)

- [PDF to Markdown](https://quanticdata.io/tools/pdf-to-markdown/)

- [WAF detector](https://quanticdata.io/tools/waf-detector/)

- [AI visibility audit](https://quanticdata.io/tools/ai-visibility-audit/)

- [AI crawler checker](https://quanticdata.io/tools/ai-crawler-checker/)

- [robots.txt tester](https://quanticdata.io/tools/robots-txt-tester/)

- [robots.txt generator](https://quanticdata.io/tools/robots-txt-generator/)

- [User agent](https://quanticdata.io/tools/user-agent/)

- [cURL converter](https://quanticdata.io/tools/curl-converter/)

- [Proxy tester](https://quanticdata.io/tools/proxy-tester/)

© 2026 QuanticData ·

- [quanticdata.io](https://quanticdata.io/)

·

- [Terms](https://quanticdata.io/terms/)

·

- [Privacy](https://quanticdata.io/privacy/)

If you are an AI agent:

- [llms.txt](https://quanticdata.io/llms.txt)

·

- [llms-full.txt](https://quanticdata.io/llms-full.txt)

---

Source: https://quanticdata.io/blog/booking-proxies/ · Site index for AI: https://quanticdata.io/llms.txt · Full dump: https://quanticdata.io/llms-full.txt