# Expedia Hotel Scraper (`mrdoe/expedia-hotel-scraper`) Actor Expedia hotel scraper for prices, ratings, photos, and room-by-room pricing breakdowns. Search by destination, hotel name, or URL - no API needed. Get per-room pricing, discounts, and amenities most Expedia scrapers miss, for any property worldwide. - **URL**: https://apify.com/mrdoe/expedia-hotel-scraper.md - **Developed by:** [MrDoe](https://apify.com/mrdoe) (community) - **Categories:** Travel, News, Lead generation - **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.50 / 1,000 results 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 Scraper Extract hotel listings from **Expedia.com**, the world's largest online travel marketplace with millions of properties across 200+ countries. Get comprehensive data including prices, ratings, photos, and location details for any destination — delivered as clean, structured data ready for analysis, monitoring, or your own product. Looking for guest reviews instead? See the companion [Expedia Review Scraper](https://apify.com/mrdoe/expedia-review-scraper). Run it on the Apify platform for on-demand or scheduled runs, API access, and integrations with the tools you already use. ### What does Expedia Hotel Scraper do? This Actor collects hotel data from Expedia in three ways: - **Search by destination.** Type a city name, get back a list of hotels with a headline price, rating, and photos for your selected dates — one row per hotel, for comparing across a city. - **Fetch by URL.** Paste a specific Expedia hotel URL and get back **every room type that hotel offers**, each with its own price, strikeout discount, and facility list (bed configuration, size, view, WiFi, etc.) — one row per room, for a complete picture of a single property. - **Find by hotel name.** Don't have a URL? Type the hotel's name (e.g. "Hilton Garden Inn Dubai Mall Of The Emirates") and the Actor finds that exact property and returns its full room breakdown, same as fetch-by-URL. If the name doesn't match anything closely enough, nothing is scraped and the run tells you why instead of returning the wrong hotel; if it matches closely but not perfectly (a typo, a shortened name), it still scrapes the best match and flags that assumption on every output row. Paste a search URL instead of a hotel URL and you get the destination-search behavior (one row per matching hotel) at that URL's filters. ### Key features | Feature | Description | | ------------------------ | ------------------------------------------------------------------------------------------------------------ | | Destination search | Type any city; the Actor resolves it to the correct Expedia region | | URL mode | Accepts hotel URLs and Expedia search URLs | | Deeplink support | Expedia share links (`expe.onelink.me` and similar) are auto-resolved to the canonical hotel URL | | Date and guest filters | Check-in/out dates, adults, rooms, children with ages | | Price and rating filters | Min/max price, star ratings, sort order | | Photos and pricing | Up to 4 images per hotel, nightly price, strikeout discounts | | Full room breakdown | Fetching a specific hotel returns every room type it sells, each with its own price and facilities | | Find by hotel name | Type a hotel's name instead of hunting for its URL; low-confidence matches are flagged, not silently guessed | ### What data can you extract? #### Hotel cards (destination search or search URL) - **Identity and location** — property ID and URL, name, star rating, destination context - **Pricing** — headline nightly price (numeric and formatted), strikeout price when discounted, currency - **Reviews (aggregate)** — overall rating (0–10), rating label (Good, Excellent, etc.), total review count - **Media and dates** — gallery image URLs, check-in/check-out dates, adult count used for search #### Room records (specific hotel URL) - Everything in a hotel card, repeated on every room row for context (name, rating, review count) - **Room name** — e.g. "Twin Room, 2 Twin Beds", "Suite, 1 Bedroom", "Family Suite, 2 Bedrooms" - **Room price** — nightly price and strikeout discount for that specific room type - **Facilities** — bed configuration, room size, view, WiFi, cancellation terms, and other amenities Expedia lists for that room ### How to use Expedia Hotel Scraper #### Search by destination ```json { "mode": "search", "destination": "Paris", "adults": 2, "currency": "USD", "maxItems": 50 } ``` #### Filter by price and star rating ```json { "mode": "search", "destination": "Tokyo", "checkIn": "2026-09-10", "checkOut": "2026-09-13", "adults": 2, "starRatings": ["4", "5"], "minPrice": 150, "maxPrice": 400, "sortBy": "REVIEW" } ``` #### Get every room type for a specific hotel ```json { "mode": "url", "startUrls": [{ "url": "https://www.expedia.com/Example-City-Hotels-Sample-Hotel.h11111.Hotel-Information" }], "checkIn": "2026-09-10", "checkOut": "2026-09-13" } ``` Returns one record per room type the hotel sells for those dates (Standard, Deluxe, Suite, etc.), each with its own price and facility list. Pass several hotel URLs in `startUrls` to do this for more than one property in a single run. #### Find a hotel by name (no URL needed) ```json { "mode": "hotelName", "hotelName": "Hilton Garden Inn Dubai Mall Of The Emirates", "destination": "Dubai", "checkIn": "2026-09-10", "checkOut": "2026-09-13" } ``` Returns the same room-by-room breakdown as fetch-by-URL, but starting from just a name. `destination` is optional here — add it when the hotel name alone could match more than one property (e.g. a hotel chain with several locations). If nothing matches closely enough, the run finishes with zero records and a message explaining why, rather than returning an unrelated hotel; a close-but-imperfect match is still used, with the assumption noted in `extra.hotelNameMatch` on every returned row. #### Paste a deeplink (expe.onelink.me share link) Share links generated by the Expedia mobile app's "Share" button, as well as marketing and social deeplinks, are accepted as-is. The Actor follows the redirect, identifies the hotel, and extracts it like any other URL. ```json { "mode": "url", "startUrls": [{ "url": "https://expe.onelink.me/hnLd/9o2lnq8o" }] } ``` Supported deeplink hosts: `expe.onelink.me` (primary), `expe.app.link`, `trip.expedia.com`. Only Expedia hotel deeplinks are handled. Hotels.com and Vrbo short links are out of scope for this release. #### Use a search URL Paste an Expedia search URL with your filters already applied. The Actor returns matching records up to `maxItems`. ```json { "mode": "url", "startUrls": [ { "url": "https://www.expedia.com/Hotel-Search?destination=Barcelona&d1=2026-07-01&d2=2026-07-05&adults=2" } ], "maxItems": 200 } ``` #### Family travel with children ```json { "mode": "search", "destination": "Orlando", "adults": 2, "children": ["5", "10"], "rooms": 1 } ``` ### Input parameters | Parameter | Type | Default | Description | | -------------------- | -------- | ------------------ | ----------------------------------------------------------------------------------------------- | | `mode` | string | `search` | `search`, `url`, or `hotelName` | | `destination` | string | `Paris` | City name (search mode); optional narrowing hint (hotelName mode) | | `hotelName` | string | | Hotel name to look up (hotelName mode) | | `startUrls` | object\[] | | Expedia URLs (URL mode) | | `destinationId` | string | | Optional numeric region ID. Skips auto-resolution | | `checkIn` | string | tomorrow | `YYYY-MM-DD` or a relative offset like `1 day` | | `checkOut` | string | day after tomorrow | `YYYY-MM-DD` or a relative offset like `2 days` | | `adults` | integer | `2` | Adult guests, 1 to 14 | | `children` | string\[] | `[]` | Ages of children, 0 to 17 (one entry per child) | | `rooms` | integer | `1` | Rooms to book, 1 to 8 | | `minPrice` | integer | | Minimum nightly price | | `maxPrice` | integer | | Maximum nightly price | | `starRatings` | string\[] | `[]` | One or more of `1`, `2`, `3`, `4`, `5` | | `sortBy` | string | `RECOMMENDED` | `RECOMMENDED`, `PRICE_LOW_TO_HIGH`, `PRICE_HIGH_TO_LOW`, `DISTANCE`, `PROPERTY_CLASS`, `REVIEW` | | `currency` | string | `USD` | 3-letter ISO code | | `maxItems` | integer | `5` | Hard cap on total records | | `proxyConfiguration` | object | Apify Residential | Proxy configuration | ### Output example #### Hotel card (destination search or search URL) ```json { "mode": "search", "placeName": "Example Hotel Paris", "hotelId": "11111", "hotelUrl": "https://www.expedia.com/Example-City-Hotels-Sample-Hotel.h11111.Hotel-Information", "hotelOverallRating": 9.2, "hotelRatingLabel": "Wonderful", "hotelTotalReviews": 1843, "provider": "expedia", "scrapedAt": "2026-04-18T07:30:00.000Z", "extra": { "searchDestination": "Paris", "starRating": 5, "priceFrom": 420, "priceFormatted": "$420 nightly", "priceStrikeout": "$600", "currency": "USD", "images": [ "https://images.example.com/lodging/sample-1.jpg", "https://images.example.com/lodging/sample-2.jpg" ], "checkIn": "2026-07-01", "checkOut": "2026-07-03", "adults": 2 } } ``` #### Room record (specific hotel URL) ```json { "mode": "rooms", "placeName": "Example Hotel Paris", "hotelId": "11111", "hotelUrl": "https://www.expedia.com/Example-City-Hotels-Sample-Hotel.h11111.Hotel-Information", "hotelOverallRating": 9.2, "hotelRatingLabel": "Wonderful", "hotelTotalReviews": 1843, "provider": "expedia", "scrapedAt": "2026-04-18T07:30:00.000Z", "extra": { "roomName": "Deluxe Room, City View", "facilities": ["City view", "355 sq ft", "Sleeps 3", "1 King Bed", "Free WiFi"], "priceFrom": 420, "priceFormatted": "$420 nightly", "priceStrikeout": "$600", "currency": "USD", "checkIn": "2026-07-01", "checkOut": "2026-07-03", "adults": 2, "starRating": 5, "hotelCategoryRatings": { "Cleanliness": 9.4, "Service": 9.3 }, "hotelNameMatch": null } } ``` `hotelNameMatch` is only set (non-null) when the run used `mode: "hotelName"`. It records what you typed, which hotel name it was matched to, a confidence score, and — when the match wasn't exact — a plain-language note explaining the assumption: ```json "hotelNameMatch": { "query": "Hilton Garden Inn Dubai Mal", "matchedName": "Hilton Garden Inn Dubai Mall Of The Emirates", "score": 0.9, "confident": false, "note": "Hotel name \"Hilton Garden Inn Dubai Mal\" didn't match any hotel exactly (best match 90% confidence). Assumed you meant \"Hilton Garden Inn Dubai Mall Of The Emirates\" and scraped that hotel. If this is wrong, use a more exact name, add a destination to narrow the search, or use a direct hotel URL instead." } ``` You can download the dataset in various formats such as JSON, HTML, CSV, or Excel from the Apify Console or API. ### Tips - Use `maxItems` to control run size. The Actor saves matching records until that limit is reached or there are no more results. - A specific hotel URL returns one row per room type, so a hotel with 7 room types uses up to 7 of your `maxItems` on its own — size `maxItems` accordingly when passing several `startUrls`. - `destinationId` speeds up search. Pass the numeric ID from any Expedia URL (the segment after `.d`) to skip name resolution. - Need reviews for a hotel? Use the companion [Expedia Review Scraper](https://apify.com/mrdoe/expedia-review-scraper) — it accepts the same hotel URLs. - In `hotelName` mode, add `destination` whenever the hotel name alone could match a chain's multiple locations (e.g. "Hilton Downtown" exists in many cities) - it narrows the lookup instead of relying on the name alone. - Some fields (star rating) are only populated when Expedia itself publishes that data for a given property — they're left blank rather than guessed. ### Pricing This Actor is priced per result (per hotel card or per room record). There's no artificial ceiling on `maxItems` — raise it as high as you need for your use case. Runs use Apify's proxy network, which is included in your Apify plan's usage. ### FAQ & support **Is this legal?** This Actor extracts publicly available information from Expedia.com pages that anyone can view in a browser. You are responsible for using the collected data in compliance with applicable laws and Expedia's terms of service. **Some fields are empty for a hotel — why?** Not every property on Expedia carries every field (e.g. an official star rating). The Actor never fabricates data — a missing field means Expedia itself doesn't expose it for that listing. **I typed a hotel name and got zero results — why?** The name didn't match any hotel closely enough for the Actor to be confident it's the right one, so it scraped nothing rather than guessing. Check the run log for the exact warning, try a more complete/exact name, add `destination` to narrow the search, or switch to a direct hotel URL if you have one. **Found a bug or have a feature request?** Open an issue on the Actor's Issues tab, or reach out for a custom data extraction solution tailored to your needs. # Actor input Schema ## `mode` (type: `string`): "search" resolves a destination name to matching hotels. "url" fetches specific Expedia hotel or search page URLs. "hotelName" looks up one specific hotel by name and returns its room-level pricing. ## `hotelName` (type: `string`): Exact-ish name of one hotel to look up, e.g. "Hilton Garden Inn Dubai Mall Of The Emirates". Used only in hotelName mode. If the name doesn't match any result closely enough, nothing is scraped and a warning explains why - it's never guessed against an unrelated hotel. A close-but-imperfect match is still used, with a note on every output row saying which hotel name was assumed. ## `destination` (type: `string`): City or region name to search, e.g. "Paris". Used in search mode. In hotelName mode, an optional hint (e.g. the city) to narrow the name lookup when the hotel name alone is ambiguous. ## `destinationId` (type: `string`): Optional numeric Expedia region ID (the segment after ".d" in an Expedia URL). Skips destination-name resolution. ## `startUrls` (type: `array`): Expedia hotel URLs, search URLs, or share/deeplinks (expe.onelink.me, expe.app.link, trip.expedia.com). Used only in url mode. ## `checkIn` (type: `string`): YYYY-MM-DD. Defaults to tomorrow. ## `checkOut` (type: `string`): YYYY-MM-DD. Defaults to the day after tomorrow. ## `adults` (type: `integer`): Adult guests per booking, 1 to 14. ## `children` (type: `array`): Ages of children, 0 to 17 (one entry per child). ## `rooms` (type: `integer`): Rooms to book, 1 to 8. ## `minPrice` (type: `integer`): Minimum nightly price. ## `maxPrice` (type: `integer`): Maximum nightly price. ## `starRatings` (type: `array`): One or more of 1, 2, 3, 4, 5. ## `sortBy` (type: `string`): Result ordering. ## `currency` (type: `string`): 3-letter ISO currency code. ## `maxItems` (type: `integer`): Hard cap on total records saved, across all destinations/URLs combined. ## `proxyConfiguration` (type: `object`): Required - Apify Proxy must be enabled for this Actor to run. ## Actor input object example ```json { "mode": "search", "destination": "Paris", "startUrls": [ { "url": "https://www.expedia.com/Dubai-Hotels-Hilton-Garden-Inn-Dubai-Mall-Of-The-Emirates.h12949919.Hotel-Information" } ], "adults": 2, "children": [], "rooms": 1, "starRatings": [], "sortBy": "RECOMMENDED", "currency": "USD", "maxItems": 5, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `results` (type: `string`): No description # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://www.expedia.com/Dubai-Hotels-Hilton-Garden-Inn-Dubai-Mall-Of-The-Emirates.h12949919.Hotel-Information" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("mrdoe/expedia-hotel-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [{ "url": "https://www.expedia.com/Dubai-Hotels-Hilton-Garden-Inn-Dubai-Mall-Of-The-Emirates.h12949919.Hotel-Information" }] } # Run the Actor and wait for it to finish run = client.actor("mrdoe/expedia-hotel-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 '{ "startUrls": [ { "url": "https://www.expedia.com/Dubai-Hotels-Hilton-Garden-Inn-Dubai-Mall-Of-The-Emirates.h12949919.Hotel-Information" } ] }' | apify call mrdoe/expedia-hotel-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,mrdoe/expedia-hotel-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 ` 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/GVsZ7pfF48AyawdkX/builds/a5wdWw3tcBjICTXew/openapi.json