# Expedia Hotel Reviews Scraper (`fetchfinch/expedia-hotel-reviews`) Actor

\[💰 $1.39-$1.99 / 1K] Extract structured Expedia hotel reviews, ratings, dates, traveler details, sentiments, photos, and management responses without a browser.

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

## Pricing

from $1.39 / 1,000 expedia review extracteds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Expedia Hotel Reviews Scraper

Extract structured Expedia hotel reviews, ratings, traveler details, dates,
sentiment labels, photos, and management responses with a browserless Apify
Actor. Give it one Expedia Hotel-Information URL, several hotel URLs, or a
hotel ID and receive clean records in an Apify dataset.

### Public example tasks

Try the ready-to-run examples:

- [Test Expedia hotel reviews](https://apify.com/fetchfinch/expedia-hotel-reviews/examples/expedia-review-quick-test) — a quick sanity check with a small result set.
- [Compare recent Expedia hotel reviews](https://apify.com/fetchfinch/expedia-hotel-reviews/examples/compare-expedia-hotel-reviews) — collect reviews from multiple hotels for comparison.
- [Reviews for a specific Expedia hotel](https://apify.com/fetchfinch/expedia-hotel-reviews/examples/expedia-specific-hotel-reviews) — collect reviews for one property.
- [Analyze Expedia hotel ratings](https://apify.com/fetchfinch/expedia-hotel-reviews/examples/expedia-rating-analysis) — inspect ratings, sentiments, and traveler details.

### Highlights

- Browserless GraphQL requests; no browser session is required.
- One hotel, multiple hotels, or hotel-ID input.
- Pagination, review ordering, retries, proxy support, and optional raw diagnostics.
- Dataset records are normalized for exports, dashboards, and downstream analysis.

### How to use

The smallest useful input is an Expedia hotel URL:

```json
{
  "startUrl": "https://www.expedia.com/London-Hotels-London-Heathrow-Marriott-Hotel.h438504.Hotel-Information",
  "results_wanted": 20,
  "review_sort": "most_recent"
}
```

For several properties, use `startUrls`. You can also provide `hotelId`
directly; it takes precedence over the ID in a URL.

### Input

| Field | Description |
| --- | --- |
| `startUrl` | One Expedia Hotel-Information URL. |
| `startUrls` | One or more Expedia hotel URLs. |
| `hotelId` | Numeric Expedia hotel ID. |
| `results_wanted` | Maximum review records to save; default `20`. |
| `max_pages` | Maximum GraphQL pages per hotel; default `8`. |
| `review_sort` | `none`, `most_relevant`, `most_recent`, `highest_rating`, or `lowest_rating`. Expedia may not expose every order for every property. |
| `proxyConfiguration` | Apify proxy configuration. Residential proxies are recommended for Expedia. |
| `proxyUrl` | Optional custom HTTP proxy URL for a single run. |
| `requestHeaders` | Optional current browser headers, including an updated `client-info` value if needed. |
| `cookie` | Optional current browser Cookie header. Cookies expire and should be supplied at runtime. |
| `graphqlRequest` | Optional GraphQL request body copied from DevTools if Expedia changes its query schema. |
| `pageSize` | Reviews requested per GraphQL page; default `20`, maximum `100`. |
| `maxRetries` | Retries per page; default `3`. |
| `saveRawResponses` | Save successful GraphQL pages to the key-value store. |
| `includeRawReview` | Include Expedia's raw review object in each item. |
| `includeDebugFields` | Include diagnostic fields in each item. |
| `includeMetaRecords` | Add one summary record per hotel. |

The actor also accepts the original MVP names `maxReviews`, `maxPages`,
`sortBy`, `useApifyProxy`, `proxyGroups`, and `proxyCountryCode` for backward
compatibility.

### Output

By default, one dataset item is emitted per review. Depending on Expedia's
response, a record can include:

`hotel_id`, `hotel_name`, `review_id`, `rating`, `title`, `review_text`,
`published_date`, `stay_date`, traveler fields, language, helpful votes,
sentiment and theme labels, guest photos, management response fields, source
URLs, and `scraped_at`. Missing values are omitted.

Summary records and raw response diagnostics are optional and do not create
additional review charges. Raw pages are saved as
`RAW-{hotelId}-{page}` in the key-value store.

### Proxy and reliability

The default input uses Apify's residential proxy configuration. You can set
your own rotating gateway in the Actor's environment variables:

```text
RESIDENTIAL_PROXY_URL=http://username:password@proxy.example.com:1234
```

The environment variable is used when the `proxyUrl` input is empty. A
per-run `proxyUrl` takes precedence over the environment variable, and both
take precedence over Apify's built-in proxy configuration. Keep this value
secret; it is never logged by the actor.

HTTP 429 responses, server errors, timeouts, and transient GraphQL errors are
retried with exponential backoff and a new proxy session. Expedia can still
throttle or challenge requests, so availability depends on the property,
traffic, and proxy quality. If Expedia changes the request schema, provide a
fresh DevTools request body in `graphqlRequest`.

### Pricing

This Actor uses pay-per-event pricing. The current rate is **$1.99 per 1,000
reviews** on the free tier, with lower rates for higher Apify subscription
tiers. A small actor-start charge and the Apify minimum charge also apply.
Only saved review records are billed as review events.

# Actor input Schema

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

One Expedia Hotel-Information URL. Use startUrls for multiple hotels.

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

One or more Expedia hotel URLs. The numeric hotel ID is read from the h12345 part of the URL.

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

Numeric Expedia hotel ID. This takes precedence over the ID embedded in a URL.

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

Optional name override when using hotelId-only input.

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

Maximum review records to save.

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

Maximum GraphQL review pages per hotel.

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

Friendly sort order. Expedia may not expose every order for every property.

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

Apify proxy configuration. Residential proxies are recommended for Expedia.

## `requestHeaders` (type: `object`):

Optional browser headers. Provide a current client-info value if Expedia rejects the default.

## `cookie` (type: `string`):

Optional current browser Cookie request header. Cookies expire and should be supplied at runtime.

## `graphqlRequest` (type: `object`):

Optional exact GraphQL request body copied from DevTools when Expedia changes its query schema.

## `graphqlEndpoint` (type: `string`):

Expedia GraphQL endpoint used for review requests.

## `useApifyProxy` (type: `boolean`):

Legacy alias. Prefer proxyConfiguration.

## `proxyGroups` (type: `array`):

Legacy alias for proxyConfiguration.apifyProxyGroups.

## `proxyCountryCode` (type: `string`):

Legacy alias for proxyConfiguration.apifyProxyCountry.

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

Optional custom HTTP proxy URL. Takes precedence over RESIDENTIAL\_PROXY\_URL and Apify proxy settings.

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

GraphQL page size, capped at Expedia's practical limit of 100.

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

Number of retries for transient failures such as 429, timeouts, and server errors.

## `saveRawResponses` (type: `boolean`):

Save each successful GraphQL page in the key-value store.

## `includeRawReview` (type: `boolean`):

Include Expedia's raw review object in every dataset item.

## `includeDebugFields` (type: `boolean`):

Include pagination metadata in each review record.

## `includeMetaRecords` (type: `boolean`):

Add one summary record per hotel to the dataset.

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

Maximum time to wait for one Expedia request.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.expedia.com/Vienna-Hotels-Holiday-Inn-Vienna-City.h2530.Hotel-Information?regionId=3704&pwaDialog=product-reviews"
    }
  ],
  "results_wanted": 20,
  "max_pages": 8,
  "review_sort": "none",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "graphqlEndpoint": "https://www.expedia.com/graphql",
  "useApifyProxy": true,
  "pageSize": 20,
  "maxRetries": 3,
  "saveRawResponses": false,
  "includeRawReview": false,
  "includeDebugFields": false,
  "includeMetaRecords": false,
  "requestTimeoutSecs": 45
}
```

# Actor output Schema

## `reviews` (type: `string`):

Normalized Expedia review records.

## `rawResponses` (type: `string`):

Present when saveRawResponses is enabled.

# 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-reviews").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-reviews").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-reviews --silent --output-dataset

```

## MCP server setup

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

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/wGwmehgdtpNVwDpKZ/openapi.json