Skip to content

Free tool · live search, rate-limited

Hotel Price Check

A destination, two dates, and what Booking.com is quoting right now. Cheapest first, with the review score next to every price so a cheap room and a bad room are told apart.

2 nights, 2 adults. One REAL Booking.com search on our key, capped per visitor per day.

Lisbon

nothing searched yet

Pick your dates and press Search hotels. What comes back is one live Booking.com search: property names, the total for the stay, review scores and a link that opens the same room with your dates already filled in. Rates go stale in minutes, so this page keeps none.

Know before the response shape changes

One email when something ships that changes what you can build: a new endpoint, a changed field, a deprecation, a price move. Nothing else goes to this list.

The address is stored to send that list and nothing else. It is not sold, not shared with the marketplaces, and not used to build a profile. Unsubscribe from any email, or from the unsubscribe page. More in privacy.

What this is not

One search is a search, not a market

The honest limits of what a single live lookup can tell you, stated up front.

Not an average

The spread we print is the range inside one result set on your dates. It is not a city average, a nightly rate index or a seasonal figure, and calling it one would be making a number up.

Not a parity check

Comparing what different countries are quoted needs the same question asked of each market several times. A single reading per market produces phantom gaps, so we do not build that here.

Not cached

Hotel rates go stale within minutes. Nothing on this page is stored between runs, and there is no captured example sitting in the results panel pretending to be current.

On your own key

One search here. A comp set, a budget filter and a schedule on your key

Same endpoint, more arguments: a per-night budget, the 24 Booking.com filters, your own occupancy, and proxy_country when you are ready to sample markets properly.

Questions, answered plainly

Is this the average hotel price for a city?
No, and nothing on this page computes one. What you get is the properties one live Booking.com search returned for the dates you asked for, cheapest first, with the spread between the cheapest and the dearest of them. An average across a city would need a defined sample and repeat measurement, and we would rather show you the search than invent a statistic.
Why does the price change if I run it again?
Because it is live. Rates move, availability moves, and the set of properties a search returns moves with them. Anything printed as a fixed number would be wrong within minutes, so this tool keeps nothing.
What is in each row?
The property name, the total price for the whole stay in the currency you asked for, the review score and count where Booking has them, the room type, and a deep link that opens that property with your dates and occupancy already filled in.
Does this show prices as seen from different countries?
Not here. Booking.com does quote different markets differently, and the API exposes that through proxy_country, but a single reading per country is not a comparison: one market moves between identical requests by more than the gap you are trying to measure. That work needs repeat sampling, so it lives in its own tool.
Do I need an account?
No. No account, no email, nothing gated. The search runs on our key, which is why it is capped per visitor per day.
What can I add on my own key?
A per-night budget, the 24 Booking.com filters (free cancellation, breakfast, review score, star rating and the rest), a different occupancy, and proxy_country for market-specific pricing. Same endpoint, more arguments.