Paste a Hotels.com Hotel-Search URL and get the results back as rows: the hotel name, the price, the rating, the review count, the location, any deal label, the link and the image. The destination, the dates and the occupancy ride in the URL you submit, so the list you get is the one that search returned.
The input is the search, not the hotel - you build the query on Hotels.com the way you would to book, then hand the resulting URL to the job.
One row per hotel, each tagged with the search it came from - so a run across a dozen destinations still reconciles back to your input list.
There is no date picker and no guest count on this form. The destination, the check-in and check-out dates, the number of adults and the number of rooms are all part of the Hotel-Search URL you paste - so a row's price belongs to the search that produced it, and asking about different dates means submitting a different URL.
One search URL is every property the site listed for it, and the limit per query decides how much of that you take. Name, price, rating and review count arrive side by side, which is the shape you need to compare a market rather than look up a hotel.
Results sometimes carry a promotional label, and it arrives as its own deal column. It is optional on the result rather than guaranteed on the row, so treat it as a column that can be blank - which is also what makes it worth watching over time.
Each row is one search result as Hotels.com listed it: what it is called, what it costs for that search, how it is rated, where it is, and where to go next.
The link and the image come back alongside the numbers, so a shortlist can be rendered or checked by hand without a second pass. The column list below is the platform's own, and both download paths - JSON and Excel - project through it in the same order, so the file you get carries these nine names whichever button you press. Read the note under the table before you write a parser: the names are verified and the value formats are not.
The platform's own column list, in export order, confirmed identical across the JSON and Excel download paths. Descriptions say what each field is for; they claim nothing about its format - see the note underneath.
Read this dictionary as a list of names, not a promise about contents. The nine names and their order are solid: they come from the platform's published column list, and the JSON and Excel downloads both project through that same list in that same order. What is not settled is the shape of the values, because we hold no archived Hotels Search export at all - not an empty one, not a full one. So this page states no price format, no currency, no rating scale and no fill rate for any column. query is the exception the mechanism guarantees: the scraper writes it rather than reading it off the page, so it is on every row. Pull a free run and read the first rows before you assume anything else.
A limit per query is the only thing this form asks for beyond the list of searches. There is no sort order and no date picker - the trip is already in the URL you paste.
A few examples of how teams use hotel search data to answer a question they actually have.
Build the search you would build as a guest - your city, the weekend in question, two adults, one room - and export what the site listed. You get the set you are actually being compared against, at the prices a guest sees, rather than a rate sheet.
Export a destination, keep the url column, and feed those links to the reviews scraper. One run gives you the market; the second gives you what guests said about it, and the URL is what joins the two tables.
The dates are part of the URL, so a set of searches is a set of scenarios: the same city over several weekends, or one weekend as it approaches. What moves is visible as a diff between exports rather than as something somebody had to check by hand.
No subscription, no minimum, no recurring bill. Your first 500 rows are on us - after that, pay-as-you-go at the same flat rate as every other scraper here.
Every new account, one-time. No credit card required. Per-query limits, file upload and every export format included.
Roughly $2 per 1,000 hotels. The pre-flight estimator shows the row count and credit cost before a run starts - no surprise bills, no compute units to translate.
Volume pricing, dedicated workers and an SLA for continuous monitoring or very large historical pulls. Tell us your numbers and we will quote.
LIVESCRAPER10 at checkout.The same site, one level deeper. Take the url column from a search export, feed it in, and the shortlist becomes what guests actually wrote about each property.
The other half of where people sleep. Running both across the same destination and dates shows what a guest is really choosing between.
Short answer: yes for the public listings - and this export contains no account, no guest and no booking data.
A Hotels.com search page is published to be read. The hotel name, the price for the dates you asked about, the rating, the review count and the location are shown to anyone who runs that search, signed in or not. Collecting publicly listed prices is long-established practice, and nothing here touches a login, a booking or a payment.
There is no personal data in this output at all - it is a list of properties. No guest names, no reviews, no account rates, because none of that is in a search result. Nothing is booked, held or reserved either: reading a results page is not making a reservation, and the export carries no confirmation of any kind.
Hotels.com's own terms restrict automated access, so this is a terms question as well as a legal one - if you have a contractual relationship with the platform, check it. We run no third-party trackers on the data layer, and your exports auto-delete after 30 days.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
500 one-time free rows on every new account - no expiry. After that it is $0.002 per row, pay-as-you-go - no card on file until you say so.
Livescraper's Hotels Search Scraper turns a list of searches into hotel data. You submit Hotels.com Hotel-Search URLs - typed one per line, or uploaded as a CSV, XLSX, TXT or Parquet file - cap the rows per query or leave the limit empty to fetch all, and download the results as a clean CSV, Excel or JSON file.
Each row is one search result: the hotel name, the price that search returned, the rating and the review count, the location line, any promotional deal label, the link to the hotel page and the image. The link is the useful one for pipelines - it is what turns a shortlist from here into the input for a review pull, joined on the hotel URL.
The trip lives in the URL rather than on the form. Destination, check-in, check-out, adults and rooms are query parameters on the address you paste, which means a set of searches is a set of scenarios: one city over several weekends, or one weekend as it approaches. Revenue teams price their competitive set at the rates a guest actually sees; data teams export a destination and hand the links onward; strategy teams read what moved between two exports instead of checking by hand.
One practical note up front: this page describes the nine columns and their order, which the platform's published list and both of its download paths agree on exactly, but it claims no price format, no currency, no rating scale and no fill rates, because no archived Hotels Search export exists to base them on. Pull a free run and read the first rows before you build against it. Your first 500 rows cost nothing and need no credit card, and after that it is $0.002 per row, flat.