Booking Scraper for Hotel Rate Data
A hosted scraping API lets you hand over a Booking.com property URL and receive the rendered page or structured fields back, without running your own headless browsers or proxy pool.
This page explains what the API returns, how the request options map to credit costs, and how to choose between HTML, JSON and Markdown output for rate monitoring, review analysis or listing enrichment.
What a Booking property request returns
A single call against a Booking.com property or listing page can return nightly rates, availability windows, star rating, review score and count, amenity list, room types and the full photo gallery. The response arrives as either rendered HTML ready for your own parser or as structured JSON when extraction rules are supplied. Markdown output is also available for feeding property descriptions into an LLM for rewriting, amenity classification or competitive analysis.
Three common jobs map onto the same endpoint:
- Rate monitoring. Track nightly prices across a set of properties to support pricing and competitive analysis.
- Review analysis. Collect guest review text, ratings, traveler-type tags and posting dates to power sentiment tracking or reputation monitoring.
- Reservation detail retrieval. Pull Booking.com reservation details for analysis of market trends, customer preferences and competitor positioning.
Because the API renders JavaScript and rotates residential proxies on your behalf, the response reflects what a real browser would see rather than a stripped static page.
Choosing between HTML, JSON and Markdown
The output format should follow what happens next in your pipeline, not the other way around.
| Downstream task | Recommended output | Why |
|---|---|---|
| You already have a parser tuned to Booking's markup | Rendered HTML | Keeps your existing selectors working |
| You want named fields without writing a parser | JSON via extract_rules or ai_extract_rules | Fields arrive already mapped |
| You are feeding an LLM for rewriting or classification | Markdown | Clean text without markup noise |
| You need a visual record of the page | Screenshot | Captures how a real browser rendered it |
If you are unsure, start with JSON using extract_rules for the specific fields you need. Add ai_extract_rules with a natural-language spec when the fields are easier to describe than to select.
How a request is assembled
The workflow is four steps:
- Create an account. You get an API key and free starting credits immediately.
- Install an SDK or use cURL. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java; plain cURL works too. Each scrape becomes a single function call, with no proxy rotation or headless Chrome to manage yourself.
- Send a GET request with your API key and a Booking.com URL. JavaScript renders, residential proxies rotate, and rendered HTML comes back ready to parse.
- Add advanced parameters when needed.
render_jsturns on JavaScript rendering,stealth_proxyhandles CAPTCHA-heavy pages,country_coderoutes through a residential IP in a specific country, andai_extract_rulesextracts data from a natural-language description.
Setup is documented with copy-paste examples in Python, Node.js, cURL and a request builder. Swap in your API key and send.
Request option and credit map
The options you enable determine the credit cost per successful request. The table below summarizes the relationship between the main options and their credit implications.
| Option | What it does | Credit cost per successful request |
|---|---|---|
| Base request | Standard fetch | Starts at 1 credit |
render_js | JavaScript rendering | 5 credits |
| Premium proxy without JS | Premium proxy, no JS rendering | 10 credits |
| Premium proxy with JS | Premium proxy plus JS rendering | 25 credits |
stealth_proxy | Stealth proxy for CAPTCHA-heavy pages | 75 credits |
country_code | Route through a residential IP in a chosen country | Included with proxy options |
extract_rules / ai_extract_rules | Return parsed JSON | Included with request |
Credits are valid for one month and do not roll over. Concurrency limits are set per plan, not per target site.
Worked example: one property to JSON
Suppose you want nightly rates and the review score for a single hotel. You would:
- Take the property URL from Booking.com.
- Send a GET request to the API with your key, the URL,
render_jsenabled, and anextract_rulesmap such as{"nightly_rate": ".hprt-price-price", "review_score": ".bui-review-score__badge"}. - Receive a JSON object with those fields populated from the rendered page.
If the selectors are hard to pin down, replace extract_rules with ai_extract_rules and describe the fields in plain language. The response still comes back as parsed JSON. For a batch of properties, loop the same call over your URL list while respecting your plan's concurrency limit.
Concurrency limits versus target-side throttling
Two different limits can slow a Booking scraping job, and they need different responses.
- Your plan's concurrency limit caps how many requests can be in flight at once. If you hit it, requests queue or fail until a slot frees up. The fix is to reduce parallelism or move to a plan with higher concurrency.
- Target-side throttling happens when Booking.com itself responds slowly or blocks aggressive patterns. The fix is to space out requests or use multiple sessions rather than raising your concurrency.
If requests are failing, check which limit you are hitting before changing your plan. Raising concurrency will not help if the target is the bottleneck.
Plans and what they include
Plans are billed monthly and priced exclusive of VAT. Every plan includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules. Higher tiers add priority email support, a dedicated account manager and team management with per-user credit and concurrency quotas. Before committing to a tier, check the current pricing, included usage, trial conditions, billing schedule and cancellation terms, since these can change and should be confirmed against the latest published details. If you need to know how to stop or change a subscription, review the applicable cancellation terms before signing up.
Why teams use a hosted scraper instead of building one
Running your own scraping stack means maintaining a fleet of headless browsers, sourcing and rotating proxies, and keeping up with anti-bot changes on the target site. A hosted API absorbs that work: proxy rotation avoids IP-based blocking, headless browser rendering mimics real user behavior to reduce blocking risk, and the platform scales across thousands of browsers during traffic spikes.
For Booking specifically, the value is that property pages are JavaScript-heavy and change layout periodically. A hosted service that already renders and parses those pages removes the maintenance burden from your team.
| Downstream task | Recommended output | Why |
|---|---|---|
| Existing parser tuned to Booking markup | Rendered HTML | Keeps existing selectors working |
| Named fields without writing a parser | JSON via extract_rules or ai_extract_rules | Fields arrive already mapped |
| Feeding an LLM for rewriting or classification | Markdown | Clean text without markup noise |
| Visual record of the page | Screenshot | Captures how a real browser rendered it |
Recommendations reflect the output formats the API supports; they are not a benchmark of accuracy across formats.
| Option | What it does | Credit cost per successful request |
|---|---|---|
| Base request | Standard fetch | Starts at 1 credit |
| render_js | JavaScript rendering | 5 credits |
| Premium proxy without JS | Premium proxy, no JS rendering | 10 credits |
| Premium proxy with JS | Premium proxy plus JS rendering | 25 credits |
| stealth_proxy | Stealth proxy for CAPTCHA-heavy pages | 75 credits |
| country_code | Route through a residential IP in a chosen country | Included with proxy options |
| extract_rules / ai_extract_rules | Return parsed JSON | Included with request |
Credit costs are per successful request and depend on which options are enabled. Credits are valid for one month and do not roll over.
Frequently asked questions
Do I need an account to scrape Booking?
No external Booking account is required. You sign up for an API key, which comes with free starting credits and no card, then send the URL and the service handles the fetch.
Can I scrape Booking from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when page content varies by geography.
What's the rate limit for scraping Booking?
The API enforces concurrency limits per plan rather than per-target rate limits. If Booking.com throttles aggressive patterns, space out requests or use multiple sessions.
How do I get structured JSON from Booking?
There are two ways to get parsed JSON back. extract_rules lets you attach CSS selectors to the output field names you define. ai_extract_rules instead takes a plain-language description of the fields, so no selectors are needed. In both cases the response body is already parsed JSON, not raw markup.
Which programming languages can I use to scrape Booking?
Any language. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.
How much does it cost to scrape Booking?
Free starting credits are available on signup with no card required. Paid plans start at $19/month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JS rendering, 25 for premium proxy with JS, 75 for stealth proxy.