Expedia Hotel Data Scraper

Expedia Hotel Data Scraper

Collect a compact profile from an Expedia hotel page: the hotel name, page description, overall guest rating, and total review count. The Actor uses Expedia's hotel page and returns one structured dataset record per run.

Ready-to-run examples

• Quick Vienna hotel profile
• London hotel profile by URL
• Look up a property by Expedia ID
• Check a hotel's rating and review count

Try the sample

The default input is ready to run against Holiday Inn Vienna City:

{
  "mode": "hotel",
  "startUrl": "https://www.expedia.com/Vienna-Hotels-Holiday-Inn-Vienna-City.h2530.Hotel-Information"
}

Open Expedia Hotel Data Scraper and start with the prefilled sample hotel.

What you get

The default hotel profile can include:

• Expedia hotel ID and hotel name
• Expedia's page description
• Overall guest rating and rating label, when Expedia displays them
• Total review count, when Expedia displays it
• Property URL and scrape timestamp

Fields unavailable on a property page are omitted. Rating and review count are not present for every hotel.

Input

Input	Description
mode	hotel (default) returns one hotel profile. reviews enables the experimental GraphQL review collector.
startUrl	Expedia Hotel-Information page URL. A Vienna sample is prefilled.
hotelId	Numeric Expedia property ID. If supplied, it takes precedence over the URL.
hotelName	Optional hotel name override.
requestTimeoutSecs	Maximum wait for a hotel-page request; default 120 seconds.
maxRetries	Temporary-failure retries; capped in code at one.
proxyUrl / proxyUrls	Optional customer proxy override. Provider charges are billed to you by that provider.

The code enforces a limit of one hotel per run, even if a caller sends multiple URLs or overrides the input schema. Start separate runs for multiple properties.

The experimental reviews mode accepts results_wanted, max_pages, review_sort, and pageSize. It uses Expedia's GraphQL endpoint, which may return rate limits; review collection is not the default product path.

Proxy and billing

The Actor owner manages Bright Data Web Unlocker credentials. Customers do not need to provide an API key or configure a proxy for the standard run. If you supply your own proxy URL, that proxy replaces the owner-managed route and any charges are billed by your proxy provider.

Apify plan tier	Hotel profile (default)	Review (experimental)
Free	$0.01 per hotel	$0.00199 per review
Bronze	$0.01 per hotel	$0.00179 per review
Silver	$0.01 per hotel	$0.00159 per review
Gold, Platinum, Diamond	$0.01 per hotel	$0.00139 per review

Apify platform usage is included in the event price. Third-party proxy or Unlocker costs are not Apify platform usage and are paid by the account that owns those credentials.

Runtime

In a small six-request Bright Data test across three hotels, all page requests returned HTTP 200. Request time ranged from about 11 to 70 seconds, and the HTML response size varied substantially. This is an early sample, not a guarantee of future availability or response time.

Troubleshooting

• A run times out: Expedia pages can take over a minute through the Unlocker. Increase requestTimeoutSecs up to its allowed maximum.
• A run returns HTTP 429: Wait before retrying. Expedia may limit access; changing DNS does not remove a server-side rate limit.
• Hotel fields are missing: Ratings and review counts are property-page dependent. The Actor omits fields it cannot find rather than inventing values.
• Use your own proxy: Enter one full proxy URL in proxyUrl, or provide a short list in proxyUrls. These are treated as secrets. Your proxy provider may charge for requests and failed attempts.
• Reviews mode fails: It is experimental and uses Expedia's consumer GraphQL endpoint. Browser DevTools request bodies, cookies, and custom headers are troubleshooting inputs only; cookies expire, and these values should not be placed in public tasks or shared examples.

Export

Export the default dataset as JSON, CSV, Excel, and other formats supported by Apify.