Hotel Price Monitor — Booking.com Rates, Scores and Review Volume

Track hotel rates in any city on chosen dates — price, guest score and review count — with firstSeenAt so new properties and moves are visible between runs.

What you get

Default dataset — one row per hotel

Field	Description
id	booking:<country>/<slug> — stable across query-string churn
name, city	Property and market
checkIn, checkOut	The dates the price was quoted for
priceAmount, currency, priceRaw	Total price for those dates, and the raw text
score, reviewCount	Guest score and how many reviews it is built on
isNew, firstSeenAt, scrapedAt	Change tracking
url	Direct link

Dataset market — one row per city, with priceLow/priceMedian/priceHigh, avgScore, currency and the date range.

Sample output

London 2026-11-01→2026-11-06 — 25 hotels (25 priced)

{ "name": "Radisson Blu Hotel, London Bloomsbury", "priceAmount": 761522,
  "currency": "PKR", "score": 8.1, "reviewCount": 4306 }

{ "city": "London", "checkIn": "2026-11-01", "checkOut": "2026-11-06",
  "hotels": 25, "withPrice": 25, "currency": "PKR",
  "priceLow": 148785, "priceMedian": 459091, "priceHigh": 1193951, "avgScore": 8.28 }

Limitations — read before buying

• A browser is required. Booking.com answers a plain request with HTTP 202 — a challenge page, and renders its cards only in a browser. So this runs on the Playwright image.
• A price is only meaningful with its dates. Every row and every market row carries checkIn and checkOut. Never compare two runs with different dates — they are different questions. The default is a fortnight out for 5 nights so the prefill runs with no editing.
• The currency follows the session locale, so a Pakistan-locale run returns PKR and a US one USD. currency is reported per row and per market and is never assumed — comparing PKR to USD silently would be worse than reporting neither.
• priceAmount is the total for the stay, as Booking displays it, not a nightly rate. Divide by the nights if you need one.
• Booking.com only. Google Travel is client-side; Expedia and Agoda are not attempted.
• priceMedian is the true median (the two middle values are averaged on an even count) — taking one of them biases the figure upward precisely on the small samples this actor usually has.

Pricing

Pay per result.

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Hotel Price Monitor — Booking.com Rates and Scores declares all 10 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Hotel Price Monitor include city, checkIn, checkOut, hotels, withPrice and currency.
• Hotel Price Monitor needs no API key, login or account of any kind before its first run.
• Every one of Hotel Price Monitor's 9 inputs is optional, so it runs with no configuration at all.
• Hotel Price Monitor documents checkIn as: Check-in date the prices were quoted for. Hotel prices are not comparable across dates, so this travels with them.
• Every number published about Hotel Price Monitor is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Hotel Price Monitor is filed under travel and business so that it is found by the people looking for that job, not by its internal name.

FAQ

What does Hotel Price Monitor return?

It returns 10 documented output fields — city, checkIn, checkOut, hotels, withPrice, currency, priceLow and priceMedian — each with a declared type and a written description. The full schema is below.

What does Hotel Price Monitor require to run?

Nothing. All 9 inputs are optional and ship with working defaults.

Does Hotel Price Monitor need an API key?

No. It reads only public data and asks for no account.

How is Hotel Price Monitor billed?

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.