Expedia Hotels + Reviews
Pricing
from $1.00 / 1,000 results
From $1/1K. Extract hotel listings and reviews from Expedia.com. Get comprehensive data, including prices, ratings, review text, photos, and location details for any destination.
Search mode runs a destination query and paginates results. URL mode fetches hotels by property or search URL.
Search mode only. Type a city (for example Paris, New York, Tokyo).
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. If left empty, the Actor resolves it from the Destination text above.
URL mode only. Paste Expedia property URLs (Hotel-Information pages) or Expedia Hotel-Search URLs.
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 filter in the selected currency. Leave empty for no minimum.
Maximum nightly price filter in the selected currency. Leave empty for no maximum.
Filter by star rating. Select one or more. Leave empty to include all star ratings.
[]Order in which hotels are returned.
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. Only applies when Include reviews in hotel cards is on. Ignored in Scrape reviews only mode (Max Items caps the overall total).
YYYY-MM-DD. Only keep reviews on or after this date. Speeds up runs when you only need recent reviews.
Attach hotel level aggregate ratings (cleanliness, staff, location, and similar categories) to each review record.
Currency for prices shown on hotel cards.
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.
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). 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.
Proxy settings. Residential proxies are recommended for reliable access.
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.