# Expedia Hotel Data Scraper (`fetchfinch/expedia-hotel-data-scraper`) Actor

Collect hotel names, descriptions, overall ratings, and review counts from Expedia property pages.

- **URL**: https://apify.com/fetchfinch/expedia-hotel-data-scraper.md
- **Developed by:** [Fetch Finch](https://apify.com/fetchfinch) (community)
- **Categories:** Travel, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 72.4% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 hotels

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Expedia Hotel Data Scraper

![No customer API key](https://img.shields.io/badge/No%20customer%20API%20key-required-43A047)
![Pricing](https://img.shields.io/badge/Pricing-pay%20per%20hotel-5C6BC0)
![Output](https://img.shields.io/badge/Output-hotel%20profile-00A98F)
![Browserless](https://img.shields.io/badge/Browserless-no%20browser-3178C6)
![Run limit](https://img.shields.io/badge/Run%20limit-1%20hotel-F39C12)

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](https://apify.com/fetchfinch/expedia-hotel-data-scraper/examples/expedia-hotel-profile-quick-test)
- [London hotel profile by URL](https://apify.com/fetchfinch/expedia-hotel-data-scraper/examples/london-expedia-hotel-profile)
- [Look up a property by Expedia ID](https://apify.com/fetchfinch/expedia-hotel-data-scraper/examples/hotel-profile-by-expedia-id)
- [Check a hotel's rating and review count](https://apify.com/fetchfinch/expedia-hotel-data-scraper/examples/hotel-rating-review-count-check)

### Try the sample

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

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

[Open Expedia Hotel Data Scraper](https://apify.com/fetchfinch/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.

# Actor input Schema

## `mode` (type: `string`):

Hotel details is the reliable default. Reviews mode uses Expedia's GraphQL endpoint and may be rate limited.

## `startUrl` (type: `string`):

One Expedia Hotel-Information page URL.

## `startUrls` (type: `array`):

A single URL is accepted per run. The code enforces this limit to control run time and proxy costs.

## `hotelId` (type: `string`):

Numeric Expedia hotel ID. If provided, this takes precedence over the ID in the URL.

## `hotelName` (type: `string`):

Optional name override when using hotelId-only input.

## `requestTimeoutSecs` (type: `integer`):

The hotel page can take over a minute to return through the Unlocker.

## `maxRetries` (type: `integer`):

At most one retry is allowed per hotel, even if a larger value is supplied.

## `proxyConfiguration` (type: `object`):

Used only when the actor's Bright Data Web Unlocker credentials are not configured.

## `proxyUrl` (type: `string`):

Optional proxy URL for a run. When provided, it overrides the actor's Web Unlocker configuration.

## `proxyUrls` (type: `array`):

Optional secret list of proxy URLs; one is selected per retry.

## `results_wanted` (type: `integer`):

Only used in experimental reviews mode.

## `max_pages` (type: `integer`):

Only used in experimental reviews mode.

## `review_sort` (type: `string`):

Sort order for the one experimental review page.

## `pageSize` (type: `integer`):

Maximum of 20 reviews per request in experimental reviews mode.

## Actor input object example

```json
{
  "mode": "hotel",
  "startUrl": "https://www.expedia.com/Vienna-Hotels-Holiday-Inn-Vienna-City.h2530.Hotel-Information",
  "requestTimeoutSecs": 120,
  "maxRetries": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "results_wanted": 20,
  "max_pages": 1,
  "review_sort": "most_recent",
  "pageSize": 20
}
```

# Actor output Schema

## `hotelData` (type: `string`):

Hotel profile or review records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("fetchfinch/expedia-hotel-data-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("fetchfinch/expedia-hotel-data-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call fetchfinch/expedia-hotel-data-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fetchfinch/expedia-hotel-data-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/yrEFCOAxVLBrl1msI/builds/kBqA7B1TKyflF4gCE/openapi.json