Expedia Hotels Scraper - Prices, Ratings & Reviews
Pricing
from $1.00 / 1,000 results
From $1/1K. Scrape Expedia.com hotel listings and reviews for any destination. Extract prices, ratings, review text, photos, location details, hotel information, and more in clean, structured data.
Search mode runs a destination query and paginates results. URL mode fetches hotels by property or search URL.
Search mode only. Type a place name the way you would on the site, for example Paris, New York or Tokyo; the Actor looks it up itself. A bare Expedia region id (for example 2734) or the older "2734|Paris" form also works.
Optional. You usually don't need this -- the Actor resolves the Destination text above on its own (Expedia's own lookup first, a geocoder fallback second). Set this only if you already know the numeric region ID from an Expedia URL (for example 2734 for Paris, 178293 for New York; it is the number after .d in any Expedia URL) and want to skip resolution entirely.
URL mode only. Paste any Expedia link: a hotel page (…h891081.Hotel-Information, also on a localized site such as expedia.co.uk or the mobile m.expedia.com host), a share link (expe.onelink.me / expe.app.link), a Hotel-Search results page (its dates, guests, sort and filters are used), or a destination guide page (…d612707.Travel-Guide-Hotels). A bare property id such as 891081 also works. Hotel cards are priced for the Check in / Check out inputs (a hotel link's own dates are reported in the log, not used); a Hotel-Search link's own dates are used unless they are in the past. See the README for the full URL-shape table.
![Expedia.com & Hotel.com [$2.5💰] Reviews/Ratings/Sentiment A. avatar](https://images.apifyusercontent.com/S3jQnQO1Qq7Evmm8G6HhWSwePurMx4mbNBaxjT2ShAg/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vbmduOHZSRVNUa3NleVdFNnAtYWN0b3ItNkkxaEJLTk1nQk5IZVl4dUwtOXNoSm5hbnd2Ni1leC5wbmc.webp){kind=avatar}
[ { "url": "https://www.expedia.com/Paris-Hotels-Hotel-Trianon-Rive-Gauche.h891081.Hotel-Information" }, { "url": "https://www.expedia.com/Hotel-Search?destination=Barcelona&d1=2027-08-01&d2=2027-08-03&adults=2" }, { "url": "https://www.expedia.com/Paris-Hotels.d612707.Travel-Guide-Hotels" }]Required. Pick a date, or type a relative value such as 1 day (tomorrow) or 7 days.
Required. Pick a date, or type a relative value such as 2 days (day after tomorrow).
Number of adult guests. Affects pricing and availability in the results.
Add one entry per child and type the age in years (0 to 17). Two kids age 5 and 10? Add 5 and 10. Two 5 year olds? Add 5 twice.
[]Number of rooms to book. Each room uses the same adult and children configuration.
Minimum nightly price (the nightly price each hotel card shows, in the selected currency). Hotels without a price for your dates are skipped while a price filter is set. Leave empty for no minimum.
Maximum nightly price (the nightly price each hotel card shows, in the selected currency). Hotels without a price for your dates are skipped while a price filter is set. Leave empty for no maximum.
Filter by star rating. Select one or more. Leave empty to include all star ratings.
[]Only return properties rated at least this well by guests. Leave empty for any rating.
Only return properties that have ALL of the selected amenities. Leave empty for no amenity filter.
Only return properties of ANY of these kinds (hotel, hostel, apartment and so on). Leave empty for all types.
Only return properties offering the selected booking terms.
Only return properties tagged for ALL of the selected kinds of trip.
Only return properties with the selected accessibility features.
Limit results to these neighborhoods. Use the number after neighborhood= in an Expedia search link after you pick a neighborhood filter on the site (for example 178676 is Montmartre in Paris). Pasting that whole search link into Start URLs applies it too.
Limit results to ANY of these hotel brands. Use the number after hotel_brand= in an Expedia search link after you pick a brand filter on the site (for example 2141 is ibis). Pasting that whole search link into Start URLs applies it too.
Only hotels whose name matches this text, e.g. Marriott or Ibis (the site's own Search by property name filter). Search mode, and pasted Hotel-Search links (their hotelName parameter).
Order in which hotels are returned.
Search mode only: also fetch each hotel's address, map coordinates, full amenity list, policies, fees and what's nearby (one extra request per hotel). URL mode always includes these for hotel links.
Also fetch every room type with its rate options: price for your dates, cancellation terms, meal plan, pay now or pay later. Works in both modes. Adds roughly 0.2 to 1 MB of proxy traffic per hotel.
Keep at most this many photo links per hotel. Leave empty to keep all.
When enabled, the output is individual review records (one row per review) instead of hotel cards. Works in both Search and URL input types.
When enabled, each hotel card gets up to Max Reviews per Hotel reviews embedded under extra.reviews. Ignored if Scrape reviews only is on.
Cap on reviews embedded in each hotel card (default 20). Only applies when Include reviews in hotel cards is on. Ignored in Scrape reviews only mode (Max Items caps the overall total there, and each review row is billed as a normal result).
YYYY-MM-DD. Only keep reviews on or after this date. Speeds up runs when you only need recent reviews.
Order in which reviews are collected. Leave empty for the site's default (most relevant). When a review date range is set, empty means newest first.
Only keep reviews rated at least this (1 to 10).
Only keep reviews rated at most this (1 to 10). Combine with Lowest rated first to collect complaints quickly.
Keep links to guest photos on each review.
Keep the hotel's reply to each review (reviews only mode).
Attach hotel level aggregate ratings (cleanliness, staff, location, and similar categories) to each review record.
Currency requested for prices. Expedia.com quotes its own prices in US dollars whatever is selected here, so check extra.priceCurrency on each hotel for the currency the prices are actually in.
Language and region for content on hotel cards and for review language.
Hard cap on the total number of records saved to the dataset across all pages and hotels.
Proxy settings. Residential proxies are recommended for reliable access.
Paste a previous run ID or dataset ID to continue a large crawl of hotels without returning or charging for hotels already collected there. Use this after an interrupted run, or when continuing a destination pull in another run. For recurring daily monitoring of the same search or URLs, use Incremental mode below instead.
Turn this on for daily or recurring monitoring of the same destination search or hotel/search URLs. The first run returns all matching hotels as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED hotels. Turn on "Emit unchanged" or "Emit expired" only when you also want those hotels returned (and billed). Hotels are compared on their listing content (name, ratings, review count, price and totals, rooms, amenities, policies, address, deals); the photo set (extra.images, extra.gallery) is never compared because the site rotates it, and by default these are also left out of change detection but still returned: extra.checkIn and extra.checkOut (they roll forward daily when Check-in/Check-out are left empty), availability scarcity messages, sponsored flag, search rank, price messages, map image and search URL. Add more in Ignore fields when detecting changes below. State is kept separately for each mode/destination/URL/filter setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.
Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the destination/URLs and filters. Different searches then never mix state with each other.
Off by default. Turn on to also return hotels that have not changed since the last run, marked UNCHANGED. This returns and bills extra rows you already have, so leave it off unless you specifically want the full snapshot every run.
Off by default. Turn on to also return hotels that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search/URLs, not when Max Items capped it or when Resume was used. This returns and bills extra synthetic rows, so leave it off unless you need expiry tracking.
Output field names (or extra.* nested paths) that should NOT make a hotel count as UPDATED. Always ignored by default: extra.checkIn and extra.checkOut (left empty, Check-in/Check-out default to "tomorrow"/"the day after", which rolls forward every day on a scheduled run), the site's scarcity text (extra.availabilityMessage), ad placement (extra.sponsored), the card's search rank (extra.searchRank), the price block's text lines that carry the dates (extra.priceMessages), the map link (extra.staticMapImage) and your own customData. Add fields such as hotelTotalReviews or extra.priceFormatted here if changes to them are not relevant to your monitoring. Ignored fields are still returned in the output, only change detection skips them.
Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify > Settings > Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON; the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.