Hotel price and availability monitoring
Expediaエンドポイントを使えば、「Hotel price and availability monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Expedia's Stays, Flights, and Things To Do results into structured JSON — destination search, hotel listings with pricing and reviews, flight offers, and activity search, sourced from the same API the official mobile app uses. Credential-free.
Extract Expedia hotel search, hotel detail and reviews, flight search, and Things To Do activity search as structured JSON.
エンドポイントファミリー
4
ドキュメント化されたパラメータ
14
サンプル数
7
ライブカタログスナップショット
稼働エンドポイント
7
メソッド
POST
必須パラメータ
14
スキーマ参照
7
{
"platform": "Expedia",
"endpoint": "expedia-properties-search",
"method": "POST",
"path": "/expedia/properties/search",
"auth": "apiKey"
}ユースケース
Extract Expedia hotel search, hotel detail and reviews, flight search, and Things To Do activity search as structured JSON.
Expediaエンドポイントを使えば、「Hotel price and availability monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Expediaエンドポイントを使えば、「Flight fare research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Expediaエンドポイントを使えば、「Travel activity discovery」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のExpediaエンドポイントカタログから取得しています（エンドポイント7件、ドキュメント化されたリクエストパラメータ14個、公開レスポンススキーマ7件）。DocsとPlaygroundが参照しているカタログと同じものです。
Expediaのエンドポイントは7件、4つのリクエストファミリーに分類されています（Properties、Activities、Flightsほか1件）。
これらのExpediaエンドポイントには14個のリクエストパラメータがドキュメント化されており、うち14個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
7件のExpediaエンドポイントのうち7件が実際のサンプルレスポンスを、7件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Expediaのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、500、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Expediaのエンドポイントは7個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/expedia/properties/search
/expedia/activities/search
/expedia/flights/search
/expedia/locations/search
エンドポイントカタログ
/expedia/locations/searchReturns normalized destination/property typeahead suggestions (cities, airports, neighborhoods, hotels) for a free-text term.
レスポンスに関する注記
Each `data.items[]` entry's `region_id` (when present) can be passed as the `destination` context to `expedia-properties-search`/`expedia-properties-filters`/`expedia-activities-search`, which resolve free-text destinations through this same typeahead internally. Example response: ```json { "code": 200, "msg": "OK", "data": { "term": "Miami", "items": [ { "type": "SearchLocationBasicItem", "geo_type": "CITY", "primary_text": "Miami", "secondary_text": "Florida, United States", "location_full_name": "Miami, FL, United States", "region_id": "178289", "latitude": 25.77427, "longitude": -80.19366 } ] } } ```
MCPツール expedia_locations_search
/expedia/properties/searchReturns normalized Expedia Stays (hotel) search results for a free-text destination and date range. Promotional banners and sponsored ad slots are dropped, so every returned property has an id and name.
レスポンスに関する注記
`data.region_id` identifies the resolved destination and can be reused directly by `expedia-properties-filters`. Each `data.properties[]` entry's `id` is the property id for `expedia-properties-detail`/`expedia-properties-reviews`. Every returned property has a non-empty `id` and `name`: promotional banners and sponsored ad slots that Expedia mixes into its result list are dropped. They come on top of the requested `page_size`, so a full page still holds `page_size` properties. Price fields are kept as upstream-formatted display strings (e.g. `"$72 total"`) rather than parsed into a currency amount, since the upstream schema only exposes display-formatted price text on the search-results card. Example response: ```json { "code": 200, "msg": "OK", "data": { "destination": "Miami, Florida, United States of America", "region_id": "2297", "check_in": "2026-08-04", "check_out": "2026-08-05", "page": 1, "results_label": "300+ properties", "properties": [ { "id": "111893452", "name": "Kompose Boutique Hotel Miami Airport", "url": "https://www.expedia.com/Miami-Hotels-Kompose-Boutique-Hotel-Miami-Airport.h111893452.Hotel-Information", "review_score": 9.2, "review_count": 4460, "review_title": "Wonderful", "price": "$72 total", "strikeout_price": "$94", "nightly_price": "$53 nightly", "thumbnail_url": "https://images.trvl-media.com/lodging/112000000/111900000/111893500/111893452/5069ea21.jpg", "amenities": ["Pool"], "badges": ["VIP Access", "Member Price $22 off"] } ] } } ```
MCPツール expedia_properties_search
/expedia/properties/filtersReturns the sort and filter facets (amenities, star rating, neighborhood, nightly price range, sort options) available for a Stays search.
レスポンスに関する注記
Each `data.sections[].fields[]` entry's `type` is one of: `multi_select`, `single_select`, `dropdown`, `range`. For the selection types, `options[]` lists the selectable values; for `range`, `range_min`/`range_max` bound the field instead. Each option's `filter_id` (e.g. `amenities`, `star_rating`, `regionId`) and `value` are the upstream selection keys these facets represent -- exposed for reference; `expedia-properties-search` does not yet accept a filter-selection input. Example response: ```json { "code": 200, "msg": "OK", "data": { "destination": "Miami, Florida, United States of America", "region_id": "2297", "sections": [ { "title": "Filter by", "fields": [ { "type": "range", "label": "Nightly price", "range_min": 0, "range_max": 1000 }, { "type": "multi_select", "label": "Popular filters", "options": [ {"filter_id": "amenities", "value": "92", "label": "Airport shuttle included (92)"} ] } ] } ], "sort_options": [ {"filter_id": "sort", "value": "RECOMMENDED", "label": "Recommended for you", "selected": true} ] } } ```
MCPツール expedia_properties_filters
/expedia/properties/detailReturns a hotel's detail summary (name, star rating, address/coordinates, top amenities) for a known property id.
MCPツール expedia_properties_detail
/expedia/properties/reviewsReturns a hotel's overall rating and highlighted/recent guest reviews (reviewer, date, rating, message) for a known property id.
MCPツール expedia_properties_reviews
/expedia/flights/searchReturns normalized Expedia Flights search results (departing-leg offers) for an origin/destination IATA pair and date range.
レスポンスに関する注記
`data.offers[]` lists the *departing*-leg offers only, matching the app's own multi-step round-trip selection flow -- return-leg selection is not implemented. Example response: ```json { "code": 200, "msg": "OK", "data": { "origin": "JFK", "destination": "LAX", "departure_date": "2026-08-17", "return_date": "2026-08-18", "offers": [ { "airline": "JetBlue Airways", "route": "New York (JFK) - Los Angeles (LAX)", "departure_time": "7:30am", "arrival_time": "10:26am", "stops": 0, "duration_summary": "5h 56m • Nonstop", "price": "$551", "price_note": "Roundtrip per traveler" } ] } } ```
MCPツール expedia_flights_search
/expedia/activities/searchReturns normalized Expedia Things To Do (activities/tours) search results for a free-text destination and date range.
MCPツール expedia_activities_search
関連API
Travel & Hospitality
Build travel and lodging research workflows from structured Airbnb stay, room, availability, and review data.
Travel & Hospitality
Research hotels, restaurants, attractions, and destination pages from TripAdvisor with normalized listing and review endpoints.
Travel & Hospitality
Turn Booking.com's hotel, flight, and attractions surfaces into structured JSON — search results, hotel detail with rooms and photos, guest reviews, flight offers, and things-to-do listings, replayed directly against Booking.com's own persisted-query GraphQL and REST endpoints. Credential-free.
対象企業
Expedia Group, Inc. · EXPE
Expediaを運営するのはExpedia Group, Inc.（EXPE）です。CrawloraのSECエンドポイントは同じ企業のCIKを受け取るため、提出書類・財務・インサイダー取引・13F保有を上記のExpediaエンドポイントと同じAPIキーで取得できます。
カタログ内の他のExpedia Group, Inc.プラットフォーム
Expediaのスクレイピング方法
Crawlora's Expedia endpoints cover Stays, Flights, and Things To Do. Unlike most endpoint families, every Expedia call is a POST with a JSON body, such as {"destination": "Miami", "check_in": …, "adults": 2}. Responses mirror what Expedia's app shows a shopper: prices as display strings like $351 total or $120 nightly, strikeout prices, sale badges, and review labels.
POST /expedia/properties/search with destination, check_in, check_out, adults, and rooms. It returns region_id, a results_label (300+ properties for Miami Beach), and a page of property cards. Expedia mixes promo banners and sponsored slots into its result list (4 extra entries in one Miami search). The API drops them, so every card has an id and name and a full page still holds page_size cards (20 by default). Cards carry review_score, price, strikeout_price, nightly_price, and badges such as Sale $285 off.
/expedia/properties/filters returns the search-page facets for a destination: star rating (1 to 5 stars), guest rating (Good 7+, Very good 8+, and so on), and six sort options, each with its filter_id and value. The search endpoint does not accept filter selections yet, so treat the facets as reference data.
/expedia/properties/detail returns star_rating (half stars occur, for example 3.5), address, coordinates, and an amenities list such as Pool, Breakfast included, and Free WiFi. /expedia/properties/reviews returns overall_rating as text (8.4/10) plus reviews with a rating label and a verified flag.
/expedia/flights/search returns departing-leg offers only (the return leg is chosen in a second step on Expedia). Each offer carries airline, route, stops, a duration summary such as 2h 59m • Nonstop, and a per-traveler round-trip price. /expedia/activities/search returns activities with duration, review score and label, price, and a free_cancellation flag.
FAQ
Expedia's search cards only expose display-formatted prices, such as $351 total, $120 nightly, or $636 as a strikeout, so the API keeps them verbatim. Parse the number yourself if you need arithmetic.
No. Expedia's own result list mixes promo banners and sponsored ad slots in with real hotels. The API drops them, so every returned property has an id and a name, and a full page still holds page_size properties.
No. /expedia/flights/search returns departing-leg offers only, which matches Expedia's own multi-step round-trip flow. Each offer's price is the round-trip price per traveler.
Not a self-serve one. Expedia Group's Rapid API requires becoming an approved Expedia partner before you can even request an API key, and that key stays restricted to a development mode until your integration passes a site review — there's no instant, unaffiliated developer signup. Crawlora's Expedia endpoints return hotel, flight, and activity search and detail data as structured JSON with a single API key, no partner approval or site review required.