Aleksandr Kobtsev

Over a hundred travel-operator price and availability integrations taught me one rule: a number off by one is a booking that does not exist. I build scrapers the same way: the source is lying until it proves otherwise.

My Actors:

• verify before they bill: currency, language and dates are checked on every response.
• never charge for a page they could not read.
• fail loudly: a run that collected nothing fails, it does not end green.
• are watched: a scheduled job re-parses live pages, so a markup change shows in hours.

• Booking.com Scraper : hotels of a city or airport with prices for your dates.
• Booking.com Reviews Scraper : guest reviews of any hotel, by score, language, trip type or word.
• Booking.com Hotel Price Monitor : one hotel's price and availability for every date.
• Booking.com Hotel Price Calendar Scraper : room rates with cancellation terms.

• Google Hotels Scraper : a hotel's price on every booking site Google lists.
• Google Hotels Price Tracker : a hotel's price by date: low or high, sold out, alerts.
• Hotel Rate Parity Monitor : which booking sites undercut a hotel's own site, and by how much.
• Hotel Leads Scraper : hotels with e-mail, phones and booking engine.
• Hotel Review Insights : what guests praise and criticise, and ratings elsewhere.

Found something broken? Open an issue on the Actor. I read them.