Do hotel prices change by country?

Published September 5, 2026

Short answer: Yes, sometimes, but the gap is real, modest, and property-dependent, not a fixed percentage. FlightPowers' Booking.com endpoints take a proxy_country field (a two-letter code) that routes the request through a residential proxy in that market. A controlled 2026-08-28 run found Japan about 4% under Germany on three Rome properties across repeat samples, while us itself varied by more than that between identical calls seconds apart.

Sometimes. Less than the internet says, and not reliably enough to measure with one call.

Booking.com can quote a different rate depending on where the visitor appears to be browsing from. Every endpoint here takes proxy_country, a two-letter lowercase code that routes the request through a residential proxy in that country, so you can price the same room as a resident of another market. Leave it out and the request goes through the global pool.

How do you make the request?

Same call as any other search, one extra field.

curl -X POST "https://booking-live-api.p.rapidapi.com/hotel_by_name" \
  -H "Content-Type: application/json" \
  -H "x-rapidapi-host: booking-live-api.p.rapidapi.com" \
  -H "x-rapidapi-key: $RAPIDAPI_KEY" \
  -d '{
    "hotel_name": "Duplo Charme Boutique Hotel",
    "checkin_date": "2026-11-18",
    "checkout_date": "2026-11-21",
    "adults": 2,
    "currency": "EUR",
    "proxy_country": "de"
  }'

A key with proxy_country included on the free plan comes from the RapidAPI listing. Nothing is held back for the paid tiers.

What did a controlled run show?

Three Rome properties, three markets, three identical requests per market. Only proxy_country changed. Captured 2026-08-28, totals for the stay in the same currency.

Read the rows before the columns.

Japan came back about 4% under Germany on all three properties, and it held across three repeat runs. That is a real gap, and it is modest.

Now look at us. Three identical requests, seconds apart, returned 486, 523 and 482 on one property. That spread inside one market is larger than the gap between markets. If you had sampled us once and compared it to a single de call, you would have "found" a 7.6% difference that is mostly noise.

How to measure it honestly

Repeat every market. One call per country is not a measurement, it is a draw from a distribution you have not looked at. Sample each market several times and record the spread next to the median.

Hold the property fixed. Compare one named property to itself across markets. Comparing "the first result" between markets compares different hotels, because result ordering is not stable between identical runs.

Do not anchor on us. It was the least stable market in this run. Pick a market that repeats cleanly as your baseline.

Say what you measured. "Japan ran about 4% under Germany on these three properties, on this date, over three samples" is a claim you can defend. "Prices vary by up to 8% across countries" is not.

price_as_seen_from is an input parameter on the keyed hotels MCP server, not a field in the REST response. Do not go looking for it in the JSON.

Related

• Geo-Pricing API: the product page, with the captured runs
• How to monitor hotel rate parity: the scheduled version, for brand and channel monitoring
• Hotel prices by hotel name: the lookup this builds on
• Hotel Price by Country: the three-market check in the browser, on our key