Scraping API PricesHome / Cost to scrape / Booking.com
Cost to scrape Booking.com at 10K, 100K, and 1M
Published Booking.com scraping rates, plan costs at three billable volumes, access facts, protections, and the official API option.
Access
Protections in the way
Terms
What you scrape moves the bill more than who you buy from. A target that forces JavaScript rendering or a residential exit multiplies the meter before any plan is chosen.
No vendor publishes a rate specific to this target. That is the finding.
It means the general meter applies: whatever the vendor charges for a page of this kind, with the rendering and proxy multipliers its own pricing page states. The market table prices exactly that.
Access fact, checked 2026-07-26: Booking.com’s Terms prohibit automated systems from scraping, crawling, monitoring, or copying platform content without prior express written permission (Source).
Cost to scrape Booking.com at 10K, 100K, and 1M table
| Route | 10K | 100K | 1M | Billing rule and source | Checked |
|---|---|---|---|---|---|
| Crawlbase: Booking.com scrapers | Not published | Not published | Not published | Target endpoint is documented, but no target-specific public rate is in the record | 2026-07-26 |
| Bright Data Web Unlocker and Web Scraper API: Booking.com Scraper API | Not published | Not published | Not published | Target endpoint is documented, but no target-specific public rate is in the record | 2026-07-26 |
| Booking.com Demand API | Rate not in target record | Rate not in target record | Rate not in target record | No public per-call API price is published; commercial affiliate terms apply. | 2026-07-26 |
The comparison uses 10,000, 100,000, and 1,000,000 billable target calls or delivered results per month, calculated on 2026-07-26. It does not claim those calls all become useful rows. Credit, request, result, and search meters are passed through the dataset quote model, which selects the least expensive published self-service offer that covers each volume. A starting USD rate is shown as a lower bound because an unpublished minimum, tier, or contract can raise the invoice. Retries, pagination, duplicate outputs, taxes, and data licensing are outside these figures.
No public target price was found
The dataset contains no published surcharge or target-specific unit rate for Booking.com. A vendor may document a dedicated endpoint without publishing what that endpoint costs at these volumes. Those rows remain “Not published” rather than borrowing a generic request price, because a generic price does not prove target support, residential routing, rendering, parser coverage, or the target-specific contract. The unknown is the answer until a first-party rate is published.
Rendering and access change the job
This record classifies Booking.com as hard and records rate limiting, CAPTCHA, bot detection and fingerprinting, IP reputation checks, geographic variation or restriction, dynamic rendering. JavaScript rendering is required in the recorded profile, so a plain HTML request is not the same workload. Residential routing is recorded as needed, but no generic proxy multiplier is silently added: the table applies only a vendor’s explicit target meter.
Property pages, search results, rates, reviews, and availability are different outputs, so the endpoint name alone does not prove field coverage.
The official route is a separate product decision
Booking.com Demand API is recorded as available. Requires a managed Affiliate Partner account, contract, affiliate ID, and API token. No public per-call API price is published; commercial affiliate terms apply. Demand API is an affiliate inventory interface, not a field-for-field copy of every Booking.com page. Source and access status checked 2026-07-26.
Endpoint evidence and the remaining unknown
The dataset confirms 2 dedicated endpoints or templates. This proves named target support in the cited product documentation. It does not prove that each endpoint has a public target-specific price.
- Booking.com scrapers is documented, while its target-specific price remains unpublished in this record.
- Booking.com Scraper API is documented, while its target-specific price remains unpublished in this record.
What volume means for Booking.com
One useful unit is one accommodation observation for a fixed destination, stay dates, occupancy, booker market, and refresh. A catalogue job begins with accommodation search pages, then adds property details or availability calls only for the properties and fields the project needs. Booking.com’s Demand API documents separate search, details, and availability endpoints, while Crawlbase likewise separates Booking SERP and Booking Hotel scrapers. Count those operations separately instead of treating one visible hotel card as a complete property record. (Booking.com accommodation endpoints and Crawlbase scraper catalog, retrieved 2026-07-27.)
Demand API accommodation search uses rows and a next_page token, with 100 rows by default, and its current search guide caps one search at 10 pages and 1,000 properties. The token carries the original search criteria, so each returned page is another API call. For an eligible affiliate integration, Demand API can answer the same search, detail, and availability question within its response contract. Booking.com states that API coverage and availability are not intended to match its front end one for one, so the official route is not a substitute when the project specifically needs the rendered consumer result set. (Booking.com pagination guide and Booking.com accommodation search, retrieved 2026-07-27.)
Evidence to check before buying
- Crawlbase and Bright Data each maintain Booking.com-specific scrapers crawlbase.com.
- Booking.com provides a dedicated Demand API only to managed Affiliate Partners under contract developers.booking.com.
- Booking.com’s terms specifically enumerate automated scraping and crawling booking.com.
- Confirm the exact entity and output unit, whether a page, search, result, record, or API object. Then multiply by pagination and refresh frequency before selecting a plan.
- Fix the required country or market before pricing. The recorded geographic variation means one nominal URL can represent different jobs.