Hotel rate monitoring and price comparison
Usa los endpoints de Hotels.com para convertir hotel rate monitoring and price comparison en solicitudes API repetibles con inputs documentados y respuestas JSON.
Turn Hotels.com into structured JSON — date-bound hotel search with per-night and per-stay prices, one property's live rates and room offers, the guest-review overview and paginated review archive, and static property metadata, all credential-free.
Search Hotels.com by destination and dates, then pull live per-night rates, room offers, guest reviews, and property detail as structured JSON.
Familias de endpoints
6
Parámetros documentados
14
Ejemplos
7
Snapshot en vivo del catálogo
Endpoints activos
7
Métodos
GET, POST
Parámetros obligatorios
14
Referencias de esquema
7
{
"platform": "Hotels.com",
"endpoint": "hotels-autocomplete",
"method": "GET",
"path": "/hotels/autocomplete",
"auth": "apiKey"
}Casos de uso
Search Hotels.com by destination and dates, then pull live per-night rates, room offers, guest reviews, and property detail as structured JSON.
Usa los endpoints de Hotels.com para convertir hotel rate monitoring and price comparison en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Hotels.com para convertir destination-level inventory and pricing research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Hotels.com para convertir guest-review analysis and reputation tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Hotels.com para convertir travel content aggregation en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Hotels.com — 7 endpoints, 14 parámetros de solicitud documentados y 7 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
7 documented Hotels.com endpoints, grouped into 6 request families — Reviews, Autocomplete and Offers, plus 3 more.
14 request parameters are documented across those Hotels.com endpoints, 14 of them required — the full input contract is public before you write any integration code.
7 of the 7 Hotels.com endpoints ship a recorded example response, and 7 carry a documented response schema — you can code against the real JSON before the first request.
Hotels.com endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
7 hosted MCP tools back the Hotels.com endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
/hotels/reviews
/hotels/autocomplete
/hotels/offers
/hotels/property
/hotels/rates
/hotels/search
Catálogo de endpoints
/hotels/autocompleteReturns Hotels.com search-box suggestions for a partial destination or property name in `q` (up to 120 characters). Each suggestion has its type, primary and secondary text, full location name, coordinates, and region or property id. A query with no match returns an empty `suggestions` list.
Notas de la respuesta
Returns anonymous destination and property suggestions from the Hotels.com search box. A valid no-match response has an empty `suggestions` array. Availability and prices are not included.
Herramienta MCP hotels_autocomplete
/hotels/offersReturns the public room/unit offer summaries shown for one Hotels.com property and date range, including room labels and non-transactional offer messages. Booking, checkout, payment, and reservation tokens are never returned. property_id is the numeric global property id from a Search response.
Herramienta MCP hotels_offers
/hotels/propertyReturns public static metadata from one canonical Hotels.com property page, including name, address, rating, images, and amenities. Date-bound availability, prices, booking, and review content are excluded.
Notas de la respuesta
Returns public static property metadata. Date-bound availability, prices, booking, and review content are excluded.
Herramienta MCP hotels_property
/hotels/ratesReturns one Hotels.com property's date-bound rates and availability: the same property card Search returns, with the live per-night and per-stay prices Hotels.com shows for the requested dates. property_id is the numeric global property id from a Search response's properties[].id; it is distinct from the legacy /ho<id>/ URL id.
Notas de la respuesta
Returns one property's date-bound rates and availability as the same property card `/hotels/search` returns, with the live `price` (per-stay total), `strikeout_price`, and `nightly_price` for the requested dates. `properties` normally has one entry. An unknown property id, or one with no rates for the requested dates, returns `404`.
Herramienta MCP hotels_rates
/hotels/reviewsReturns one Hotels.com property's review overview: the overall rating (0-10) with its descriptive label, the per-category sub-ratings (cleanliness, service, amenities, and so on), and a bounded set of highlighted guest reviews with reviewer, date, rating label, text, and verified-stay flag. property_id is the numeric global property id from a Search response's properties[].id. This mirrors the property page's Guest reviews section; the full paginated review archive is not exposed.
Notas de la respuesta
Returns the property's review overview: `overall_rating` on the 0-10 scale as displayed (e.g. `9.2/10`), a `superlative` label (e.g. `Wonderful`), per-category sub-ratings in `categories`, and a bounded set of highlighted guest reviews in `reviews` (reviewer, date, `8/10 Very good`-style rating label, message, and a `verified` flag). This mirrors the property page's Guest reviews section; the full paginated review archive is not exposed. An unknown property id returns `404`.
Herramienta MCP hotels_reviews
/hotels/reviews/archiveReturns one page of public guest reviews for a Hotels.com property, including reviewer, date, traveler type, rating label, title, and message. Use page and page_size to walk the archive; the response reports whether another page is available. property_id is the numeric global property id from a Search response's properties[].id. Booking, account, and private review data are not included.
Notas de la respuesta
Returns one page of public guest reviews and `has_more`, which indicates that Hotels.com advertises another page for the same property and stay criteria. Use a later `page` value to continue. The endpoint excludes booking, account, payment, and private review data.
Herramienta MCP hotels_reviews_archive
/hotels/searchReturns a page of date-bound Hotels.com hotel search results for either a free-text destination or a numeric Hotels.com region_id: property cards with per-night and per-stay prices, review score and count, location, thumbnail, amenities, and promotional badges. Provide exactly one of query or region_id; region_id skips destination typeahead resolution. Prices are the live rates Hotels.com shows for the requested check-in and check-out dates.
Notas de la respuesta
Returns a page of date-bound search results with the live per-night and per-stay prices Hotels.com shows for the requested dates. Price fields are display strings: `price` is the per-stay total (`LEAD`), `strikeout_price` the crossed-out reference price, and `nightly_price` the per-night qualifier (e.g. `$369 nightly`). Each property's `url` is the canonical `/ho<id>/<slug>/` page (usable with `/hotels/property`) and its `id` is the numeric global property id usable with `/hotels/rates` and `/hotels/reviews`. A destination with no matches returns an empty `properties` array.
Herramienta MCP hotels_search
APIs relacionadas
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 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.
Cobertura de la empresa
Expedia Group, Inc. · EXPE
Hotels.com es operado por Expedia Group, Inc. (EXPE). Los endpoints SEC de Crawlora usan el mismo CIK de esa empresa, así que los filings, datos financieros, transacciones de insiders y participaciones 13F provienen de la misma API key que los endpoints de Hotels.com de arriba.
Otras plataformas de Expedia Group, Inc. en el catálogo
Cómo hacer scraping de Hotels.com
Crawlora's seven Hotels.com endpoints cover the whole public funnel — destination suggestions, date-bound search, per-property rates and room offers, the review overview and archive, and static property detail — as normalized JSON with one API key and no account or signed session. Booking, checkout, payment and reservation tokens are never returned.
Send partial text to /hotels/autocomplete for Hotels.com's own search-box suggestions covering destinations (with region IDs) and property names. Prices are not included at this step; use the region ID or free-text destination in the next call.
POST /hotels/search with a free-text destination or a numeric Hotels.com region_id plus check-in and check-out dates for one page of normalized property cards: per-night and per-stay prices, review score and count, location, and the property_id you need for the per-property endpoints.
POST /hotels/rates with a property_id and dates for that property's date-bound rates and availability (the same card shape Search returns), and /hotels/offers for the public room and unit offer summaries shown for that stay, with room labels and non-transactional offer messages.
POST /hotels/reviews for the review overview — the 0–10 overall rating with its label and per-category sub-ratings (cleanliness, service, amenities and so on) plus a bounded set of highlighted reviews — and /hotels/reviews/archive to walk the full public review list with page and page_size (reviewer, date, traveler type, rating label, title, message).
POST /hotels/property with a canonical Hotels.com property page for name, address, rating, images and amenities. This endpoint is date-free static metadata; use /hotels/rates for prices and /hotels/reviews for review content.
Preguntas frecuentes
Resolve a destination with /hotels/autocomplete, call /hotels/search with that destination or region_id and your dates for priced property cards, then use the returned property_id with /hotels/rates, /hotels/offers, /hotels/reviews and /hotels/reviews/archive for one property's live rates, room offers and guest reviews. /hotels/property returns the static detail page. No account or signed session is required.
Yes. /hotels/search returns per-night and per-stay prices for the requested dates, and /hotels/rates returns one property's date-bound rates and availability. /hotels/offers adds the room and unit offer summaries. Only /hotels/property is static, date-free metadata.
Yes. /hotels/reviews returns the overall 0–10 rating with its descriptive label, per-category sub-ratings and a bounded set of highlighted reviews; /hotels/reviews/archive pages through the full public review list with reviewer, date, traveler type, rating label, title and message.
No. The endpoints return public search, rate, offer, review and property data only. Booking, checkout, payment and reservation tokens are never returned.
Collecting publicly accessible search results, rates, reviews and property metadata is generally permissible if you respect Hotels.com's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect, for research, monitoring and comparison rather than abusive collection.