Booking.com Hotel Scraper

Use this Booking.com hotel scraper to export listings by destination or hotel URL for travel research, price snapshots and structured datasets. Get hotel identity, location, ratings and available stay context. Rooms, policies, facilities, photos and review-summary details are optional.

Start small and add dates only when you need availability or prices. This Actor does not sign in, reserve rooms, solve access challenges or collect private traveler data.

Quick start

{
  "destination": "Lisbon",
  "maxHotelsPerSearch": 5,
  "maxCandidatesPerSearch": 25,
  "maxHotelsPerRun": 5
}

This collects up to five lean hotel rows. Without dates, price and availability fields may be null or unavailable. Export the dataset as CSV, JSON or Excel, or retrieve it through the API.

Historical useful-output excerpt, not a current availability or price claim:

{
  "hotelName": "Chiado Arty Flats",
  "hotelId": 1814397,
  "canonicalUrl": "https://www.booking.com/hotel/pt/chiado-arty-flats.html"
}

Use the results to build accommodation inventories, compare dated price snapshots, or enrich a travel dataset with property ratings and location. Each run is a snapshot, not a built-in price-alert service.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Compare Lisbon and Porto hotels
• Find family hotels in Barcelona
• Collect complete details for one Lisbon hotel
• Track Paris hotel prices in euros
• Search Lisbon hotels and export prices

What you get

• Property details: hotel identifiers, names, canonical links, location, ratings and review counts when exposed.
• Stay and price context: the requested and returned dates, occupancy, currency and displayed prices, with excluded taxes and fees kept separate.
• Optional hotel details: room information, policies, facilities, photos and review-summary metadata, with a separate outcome for each requested detail.

Every hotel row includes collection time and available coverage warnings. The separate run summary helps you check whether searches finished, returned no matches or stopped early.

Who is it for?

• Travel researchers building a sample of accommodation in selected destinations.
• Hotel and revenue teams comparing public property details and dated price observations.
• Travel data teams enriching an existing inventory with hotel identifiers, location and available details.

Hotel research workflows

• Build a destination inventory. Collect a small Lisbon or Porto sample and keep hotelId, canonicalUrl, property name and location. Review the linked properties before combining them with your travel dataset. Search results are a sample, not a complete inventory of every hotel.
• Compare dated price observations. Supply dates, occupancy and currency, then retain priceContext and provenance with each row. Compare equivalent stays in your spreadsheet, checking returned currency and separately excluded taxes or fees. The per-night amount is derived from the displayed stay total, and the observation is not a reservation or guaranteed quote.
• Enrich known hotel records. Supply direct hotel URLs and enable only the optional details you need. Inspect each enrichment outcome before using room, policy, facility or photo fields. Review enrichment provides summary metadata rather than individual guest review text.

The target and stay settings below explain the supported date modes and detail choices. For repeated observations, schedule separate runs and compare saved exports in your own workflow.

Input settings

Setting	API key	Scope
Search targets	destination, destinations, hotelUrls	One phrase, multiple destinations, or direct hotel URLs.
Fixed dates	checkIn, checkOut	Both YYYY-MM-DD dates, or neither.
Relative dates	checkInOffsetDays, stayNights	Offset 0–365 days, stay 1–30 nights.
Occupancy	adults, children, childrenAges, rooms	Adults 1–30, children 0–10, ages 0–17, rooms 1–10.
Display context	currency, language	Requested currency and locale. Returned context can differ.
Property filters	propertyTypes, minReviewScore, starRatings	Types such as HOTEL/APARTMENT. Review thresholds 6/7/8/9. Stars 1–5.
Stay filters	freeCancellationOnly, minPricePerNight, maxPricePerNight	Per-night bounds require dates. Based on displayed stay total divided by nights.
Order	sortBy	Requested Booking.com order. Not an independently re-sorted complete inventory.
Candidates per search	maxCandidatesPerSearch	1–500 evaluated rows per destination. At least the per-search saved cap.
Hotels per search	maxHotelsPerSearch	1–100 saved rows per destination.
Hotels per run	maxHotelsPerRun	1–100 saved rows across all targets.
Optional details	enrichRooms, enrichPolicies, enrichFacilities, enrichPhotos, enrichReviews	Boolean switches. Default lean output.
Connection country	countryCode	Optional country for the residential route, not an access guarantee.
Advanced connection	proxyConfiguration	Optional managed settings, direct opt-out or customer pool. No alternate-route fallback.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Each dataset row represents one hotel. Summaries are stored separately as RUN_SUMMARY in the default key-value store.

Fields	Meaning
hotelId, bookingId, canonicalUrl, url	Stable identity and canonical hotel URL, when exposed.
hotelName, location, coordinates, stars, rating, review count	Base property information.
provenance	Requested/applied destination, dates, occupancy, currency, language, filters and sorting.
availabilityContext	Returned availability status and stay context.
priceContext	Displayed stay total, currency, nights, derived per-night amount and separately excluded taxes/fees.
rooms, policies, facilities, photos, reviews	Requested optional details. Unavailable values remain null or empty.
enrichment, warnings, rank, scrapedAt	Coverage, diagnostic reasons, result order and collection time.

priceContext.total is the displayed total stay price. pricePerNight divides that amount by nights. It is not a separately quoted rate. Excluded taxes and fees stay separate. Always compare requested and returned currency rather than assuming conversion.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is a one-time run fee when budget permits. A started run can incur this fee even if no hotels are returned.

The hotel-scraped event charges for each saved hotel row. Optional enrichments have no separate event, and empty outcomes or diagnostic summaries are not hotel rows. Candidates have no result fee, but processing them uses resources.

Use the candidate, per-search and per-run caps to bound work. When the hotel-event budget is exhausted, extraction stops and the run can finish with fewer rows. Inspect RUN_SUMMARY for saved counts and budget reasons.

See the live Pricing tab for current rates and subscription discounts.

Tips for best results

• Start with lean output. Collect a few hotels first, then enable only the optional details your dataset needs.
• Choose one date mode. Supply both fixed dates or use the relative offset and stay length. Relative dates resolve from the UTC date when the run starts, so keep the returned provenance with your export.
• Include every child's age. Provide one childrenAges value per child so the requested occupancy is consistent.
• Check the returned stay context. Review dates, occupancy, currency and excluded fees before comparing prices. A requested setting is not proof Booking.com returned it unchanged.
• Read enrichment outcomes. A missing room or photo detail does not necessarily invalidate the base hotel record. Check each row's warnings and the run summary.

Limits and caveats

Summary status	Meaning and next step
SUCCEEDED	Completed without warnings. Check row counts and budgetExhausted for budget-limited work.
NO_MATCHES	A valid search found no matching listings or could not resolve a match. Empty dataset, successful run. Check spelling or target.
SOLD_OUT	No returned availability for the stay, or only sold-out rows. Completed zero-row searches succeed. This does not prove every property is sold out.
PARTIAL	Useful rows remain, but a target/enrichment failed or the safe deadline was reached. Inspect row and summary reasons.
TARGET_CHALLENGE	Access challenge. Not proof the target is private, deleted or empty. Try later with a smaller scope.
INPUT_CONFIGURATION_LIMIT_REACHED	Invalid input or exhausted candidate allowance before a filtered match. Check date mode, child ages and limits.
FAILED	Unexpected transport/response, essential storage, billing or system failure. Keep the run ID when reporting it.

Large or heavily filtered searches can stop before reaching the requested count. Booking.com can challenge access with any connection setting. Storage or billing failure still fails the run even when useful rows were saved.

A restarted or resurrected run does not resume collection. Start a new run if needed.

Deadline-limited work can write PENDING_WORK. This is diagnostic context, not an automatic resume mechanism. The Actor does not bypass challenges. Price and availability fields may be absent without dates or when not exposed.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~booking-com-hotels-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "destination": "Lisbon",
  "maxHotelsPerSearch": 5,
  "maxCandidatesPerSearch": 25,
  "maxHotelsPerRun": 5
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/booking-com-hotels-scraper').call({
  "destination": "Lisbon",
  "maxHotelsPerSearch": 5,
  "maxCandidatesPerSearch": 25,
  "maxHotelsPerRun": 5
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/booking-com-hotels-scraper').call(run_input={'destination': 'Lisbon', 'maxHotelsPerSearch': 5, 'maxCandidatesPerSearch': 25, 'maxHotelsPerRun': 5})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Booking.com Hotel Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Booking.com Hotel Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/booking-com-hotels-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Booking.com Hotel Scraper by Fetch Cat, or give it the identifier fetch_cat/booking-com-hotels-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

Give your assistant the inputs it needs along with a request like one of these:

• “Collect up to five hotels each in Lisbon and Porto with Fetch Cat's Booking.com Hotel Scraper, with a maximum of ten hotels overall and twenty-five candidates per city. Show hotel IDs, names, ratings and source links for an accommodation research sheet.”
• “Search Paris hotels for a two-night stay starting fourteen days from today, for two adults in one room and prices requested in euros. Collect at most five hotels, inspect up to twenty-five candidates, and show displayed totals, excluded fees and returned dates and currency.”
• “Collect details for the Booking.com hotel URL I provide, with at most one saved hotel. Include facilities and photos, keep the hotel's source link, and flag missing details or access warnings.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

Choose targets and stay context

Provide destination, destinations, or hotelUrls. Direct URLs must use a Booking.com /hotel/{country}/{slug}.html path and return at most one stable-ID match each. Up to 25 targets and 100 saved hotels are supported per run. Duplicate hotel IDs are saved once.

For prices and availability, supply both fixed checkIn and checkOut dates, or the relative pair below. Do not combine date modes. Relative dates resolve once during input initialization using the current UTC date and appear in row provenance.

{
  "destination": "Paris",
  "checkInOffsetDays": 14,
  "stayNights": 2,
  "adults": 2,
  "rooms": 1,
  "currency": "EUR",
  "maxHotelsPerSearch": 5,
  "maxHotelsPerRun": 5
}

Supply one childrenAges value for every child. Listings, displayed prices, currency and availability depend on Booking.com's response. They are not reservations or guaranteed quotes.

Optional hotel details

Enable only the surfaces you need. Each enrichment has an independent outcome: a rooms failure need not discard successful photos or the base hotel. Inspect enrichment and warnings on each row.

• enrichRooms: exposed room configurations and matched offer details.
• enrichPolicies: cancellation, prepayment, pet and meal-plan signals.
• enrichFacilities: facility and property highlights.
• enrichPhotos: available hotel photo URLs.
• enrichReviews: listing-level scores, labels, counts and available summary metadata, not individual guest review text.

FAQ

Does this return guest review text?

No. Review enrichment is listing-level metadata and available summaries.

Can I reuse the same input later?

Yes. Relative dates resolve when each run initializes its input. Fixed dates remain fixed.

Can I use this as a Booking.com API alternative?

You can collect supported public listing fields through Apify's API or MCP, but this is not an official Booking.com API and cannot reserve rooms. Export results as CSV, Excel or JSON.

Is a direct hotel URL guaranteed to work?

No. Both direct URLs and destination searches can be challenged, blocked or affected by Booking.com changes.

Why are prices missing or currencies different?

Check the requested dates and returned priceContext. The Actor preserves what Booking.com exposes rather than inventing prices or conversion.

Related Actors

• Booking.com Reviews Scraper — Collect available Booking.com guest-review text, ratings and visible stay details from the loaded review page, not complete history.
• Agoda Hotels Scraper — Collect public Agoda hotel search listings with displayed prices, ratings, locations and property links.
• Airbnb Listings Scraper — Collect public Airbnb accommodation listings with displayed search prices and available property metadata.
• Google Flights Scraper — Collect public Google Flights fare options for a route and travel date, with available prices and flight schedules.
• Google Hotels Scraper — Collect public Google Hotels search listings with displayed stay prices and available property details.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥