Hotels.com is the hotel-only brand of Expedia Group, and it shows two prices for most rooms: the public one, which depends on the country site you open, and the member one, which appears once you sign in to a loyalty program that has changed its name, its rules and, in Britain, its whole identity in the last three years. Proxies for Hotels.com are the tool for reading both layers the way guests in each market see them, on a schedule, without the Expedia Group platform behind the site deciding that one address is a machine.
We run a proxy network, and Hotels.com traffic reaches us from rate-shopping vendors, hotel revenue teams and price trackers, usually alongside its sibling Expedia. This page covers what is specific to Hotels.com: the country sites and the member layer, the loyalty changes that decide what a logged-in read means, the Rapid API as the sanctioned route, how the site blocks, which proxy type fits and how to size it. The hotel-side buyer's guide is proxies for hotel rate monitoring, and the sector background is in travel fare aggregation.
What proxies are best for Hotels.com?
Rotating residential proxies pinned to the country of the Hotels.com site you are reading, with a sticky residential or ISP exit for logged-in member prices. The Expedia Group platform behind the site localizes prices by point of sale and challenges datacenter ranges quickly, so a home connection in the right country is both the accuracy rule and the reputation rule. Datacenter suits a manual check; mobile is the rare tier for runs that keep drawing challenges.
The country site is the point of sale
Hotels.com runs separate country sites, and like the rest of Expedia Group it chooses currency and localizes pricing by the point of sale, the market a request appears to book from. The mechanism is the same one we describe for Expedia: the same room can show a different price and currency on the German site than on the American one, and a datacenter address wearing a country label usually collects a generic page in the wrong currency, because the site weighs where the network sits over the label attached to it.
For collection, that means the country site and the exit country have to agree. Reading a Paris hotel as a British guest means the UK site from a UK residential address, in pounds; reading it as an American guest means the US site from a US address, in dollars. One run with a currency switch reads neither.
The member layer, and why it keeps changing
The second price on Hotels.com is the member price, shown to signed-in members of the loyalty program. For a data team the problem is not that it exists; it is that the program underneath it has been rebuilt twice.
Expedia Group replaced Hotels.com's old rewards program with One Key, a single program across Expedia, Hotels.com and Vrbo. The global rollout was then scrapped in August 2024, after the United States and the United Kingdom had already switched (Head for Points). In March 2026 Hotels.com announced that its UK members would move back to a revived Hotels.com Rewards, in a phased migration between 8 April and 8 May 2026, with unspent OneKeyCash converted to Hotels.comCash (Head for Points). In the United States One Key continues, and from 28 July 2026 its earning on non-flight bookings becomes tiered by status, flights earn nothing, and the Hotel Price Guarantee on Expedia and Hotels.com ends (AwardWallet).
The practical consequence: a "member price" on Hotels.com now means different things in different markets, and a logged-in read has to be a logged-in read in that market, on an account enrolled in that market's program, held on one address for the whole session. A rate shopper that reports one member price for a hotel without saying which program and which market is reporting a number nobody is shown.
The Rapid API: the sanctioned route, if you can join
Expedia Group's lodging inventory is available to partners through the Rapid API, which the group describes as covering 800,000 properties across the globe, 310,000 destinations, 32 million property images in 40 languages and 76 million reviews, all directly sourced. Access is by becoming a partner: "You'll need to become a partner to integrate with Rapid API," with launch requirements to meet before going live (Expedia Group, Rapid API). That inventory is the supply behind Hotels.com and its sibling brands, so for a business that sells travel and can qualify, the API removes a whole site from the scraping problem.
The inventory behind Hotels.com, as Expedia Group describes its Rapid API
- 800K
- Properties
- 310K
- Destinations
- 76M+
- Reviews
directly sourced
Source: partner.expediagroup.com, Rapid API
What the API does not give you is a competitor's public price as a guest in Japan sees it, or the member layer as a signed-in member sees it, which is why residential exits per market remain the core of a rate-shopping job even for partners.
How Hotels.com blocks you
Hotels.com shares its platform and its defenses with Expedia, and the behaviour we describe in how Expedia blocks you applies here: datacenter ranges are rejected early, bulk searching that never books draws challenges, and the funnel to a bookable price sets a server-side session that has to stay on one address. A read that hops countries mid-session, arrives with no cookies, or sends a handshake that does not match its user agent fails before the IP is weighed. The address decides whether you are let in; the session decides whether you stay.
Which proxy type fits: residential, datacenter, ISP, or mobile
Datacenter proxies are challenged early on Expedia Group sites and fail the point-of-sale test regardless. Use them for parser work on saved pages.
Rotating residential proxies are home connections from a large pool, pinned to the country site's market, one per search page, rotated between. They pass the reputation check and read each market's public price as a guest there sees it (background in what is a residential proxy).
ISP proxies are static residential addresses, the right exit for a logged-in member read, which has to hold one address through the session, and for any walk through the funnel to a final price.
Mobile proxies are carrier addresses shared by many phones, the tier for runs that keep drawing challenges and for reading anything the app shows differently. Rarely needed.
| Hotels.com job | Proxy type | Why |
|---|---|---|
| Public prices across dates and cities | Rotating residential, country-pinned | Country site and exit agree; the pool spreads the schedule |
| Per-market reads (UK, DE, US sites) | Rotating residential in that country | Prices and currency follow the point of sale |
| Member prices | Sticky residential or ISP | Logged-in session on one address, per market's program |
| Funnel to a bookable price | ISP (static residential) | Server-side session persists |
| Parser development | Datacenter or free list | Saved pages, nothing at stake |
Free versus paid for Hotels.com
A free proxy is a shared datacenter address, the profile Expedia Group sites reject first, and it rarely lives long enough to finish a search page. For a single manual look at another country site, our free proxy list and proxy checker are free and enough. For a schedule, paid residential is the floor; ours starts at $0.44/GB pay-as-you-go with no KYC, so a first run across three markets costs cents.
Setting it up
Open the right country site from the right country. Pick the site by market, exit from a residential address in that country, and let the site choose its own currency; an override is a signal, and the default is what the guest sees.
Split public and member reads. Public pages rotate: one residential IP per search page, then a fresh one. Member reads hold a sticky ISP exit for the whole logged-in session, on an account enrolled in that market's program, and record which program the price came from. The split is explained in rotating vs static residential proxies.
Carry the session, trim the page. Keep the cookies the site sets for the length of a session and drop them with the address. Request the HTML you parse and block images, fonts and analytics; Expedia Group pages are heavy, and the bandwidth is the bill.
Use a browser only where the page demands it. Many Hotels.com pages carry prices in server-rendered HTML; when a page refuses to render without JavaScript, Playwright or Puppeteer behind a residential exit is the setup.
How many IPs, and how fast
The unit is a search page, and the grid multiplies across markets.
Sizing (rotating residential, one refresh cycle):
search pages = cities x check-in dates x lengths of stay x country sites
= 10 x 60 x 2 x 3 = 3,600 pages
hotel pages = search pages x hotels opened
member reads = hotels x markets, each on a sticky ISP session
Rotate per public page; hold per member session; trim every page.
Refresh near-term dates daily and far dates weekly, and the count halves. Our pricing is per gigabyte with no monthly minimum, so a seasonal shop pays only for the weeks it runs.
Staying unblocked on Hotels.com
- Country site, exit country and currency agree. A consistent visitor on a consistent market.
- Rotate public reads, hold member sessions. Mixing the two on one pool logs you out on the second page.
- Carry cookies within a session, drop them with the address. A fresh visitor every request is a bot tell.
- Keep the handshake honest. Real browser where you use one; a realistic client where you do not. The TLS fingerprint is read before the IP.
- Pace like a guest. Jitter the gaps and spread markets across the day; the checklist is in avoiding IP bans while scraping.
- Label every price by market and program. A member price without both is not a data point.
The limits worth knowing
Proxies put a Hotels.com read on the right country site from the right country and spread a schedule so that the platform sees guests rather than a monitor. They do not give you a member price without a member account in that market, they do not stand in for the Rapid API if you qualify, and they do not change Expedia Group's terms of use. Where the API or your own channel data covers a need, use it first.
For a manual look, our free proxy list and proxy checker are free. For a schedule, rotating residential at $0.44/GB pay-as-you-go per market, with a static ISP exit for the member layer, is what reads Hotels.com.
Sources
- Expedia Group, Rapid API, on inventory figures and partner access.
- Head for Points, Hotels.com Rewards is back, 5 March 2026, on the UK migration and the scrapped global rollout.
- AwardWallet, One Key to change Expedia earnings, scrap price guarantee, on the 28 July 2026 changes.
- HProxy, proxies for Expedia, on point-of-sale pricing and the shared platform's defenses.