Hotel & Host Leads Scraper — build a hotel owner contact list by city, enriched with booking tech stack

Get a hotel owner contact list for any city in minutes: hotels, guest houses, B&Bs and vacation rental host leads, each enriched with a contact email crawled from the property's own website and its hospitality tech stack — channel manager / PMS and OTA presence. No API key, no residential proxies, and you pay only per lead actually returned.

What does it do?

This actor finds accommodations by city using OpenStreetMap (Nominatim geocoding + the Overpass API), then crawls each property's own website (home, contact, about, booking and rooms pages) to extract contact emails, Facebook and Instagram profiles, and two premium signals no plain directory scraper gives you:

• Channel manager / PMS detection — SiteMinder, Cloudbeds, Mews, Guesty, Lodgify, Little Hotelier, Hostfully, Sirvoy, Beds24, eviivo, RoomRaccoon
• OTA presence detection — Booking.com, Expedia, Airbnb, Vrbo, Hotels.com, Tripadvisor, Hostelworld, Agoda

On top of that, every lead carries the listing basics: name, accommodation type (hotel / guest house / B&B / motel — optionally hostels, serviced apartments and chalets), star rating and room count where OpenStreetMap has them, full parsed address, phone, website, and coordinates. Results are deduped by name + address + website, and has_email / has_phone / has_website flags make filtering in a spreadsheet trivial.

Use cases

• Channel-manager and PMS sales teams (SiteMinder, Cloudbeds, Mews competitors) prospecting independent properties not yet showing a channel-manager signal — the classic greenfield pitch — or already on a rival's platform for a "switch" campaign.
• STR and vacation-rental software vendors building city-by-city lists of guest houses and B&Bs — small hosts who book direct today and are the ideal upgrade target.
• OTA and metasearch BD teams finding properties with a website but no Booking.com / Expedia / Airbnb footprint, i.e. inventory a competitor hasn't signed yet.
• Hospitality marketing agencies cold-emailing hotels with weak digital setups (no booking engine, no OTA links) with a "we'll fix your direct bookings" angle.
• CRM enrichment — re-run monthly per market and merge on osm_id to keep owner emails and tech-stack fields fresh in your pipeline.

Input

Field	Type	Default	Description
location	string	(required)	City and region/country to search, e.g. 'Marrakesh, Morocco', 'Lisbon, Portugal', 'Austin, Texas'.
includeHostels	boolean	false	Also include hostels.
includeApartments	boolean	false	Also include tourism apartments / aparthotels.
includeChalets	boolean	false	Also include chalets.
maxItems	integer	100	Maximum number of accommodations to return (1–1000).
crawlEmails	boolean	true	Visit each property's own website to extract contact emails and detect its channel manager / PMS and OTA presence. Turn off for a faster, listing-only run.
onlyWithWebsite	boolean	false	Drop accommodations with no website (required for email + tech-stack enrichment).
onlyWithEmail	boolean	false	Keep only properties where an email was found (best for cold email).
maxPagesPerSite	integer	3	How many pages (home, contact, about, booking...) to crawl per website while looking for an email (1–8).
concurrency	integer	8	How many websites to crawl in parallel (1–20).

Example input:

{
  "location": "Marrakesh, Morocco",
  "maxItems": 100,
  "crawlEmails": true,
  "onlyWithWebsite": false,
  "onlyWithEmail": false,
  "maxPagesPerSite": 3,
  "concurrency": 8
}

Only location is required — everything else has a sensible default.

Output

Each dataset row is one accommodation lead. Export to CSV, JSON, or Excel, or pull it via the Apify API.

{
  "name": "Riad Dar Anika",
  "type": "guest_house",
  "stars": "4",
  "rooms": "8",
  "address": "23 Derb El Ferrane, Medina",
  "city": "Marrakesh",
  "state": null,
  "postal_code": "40000",
  "country": "MA",
  "phone": "+212 5 24 38 00 00",
  "website": "https://www.riaddaranika.com",
  "email": "contact@riaddaranika.com",
  "emails": ["contact@riaddaranika.com", "booking@riaddaranika.com"],
  "facebook": "https://www.facebook.com/riaddaranika",
  "instagram": "https://www.instagram.com/riaddaranika",
  "channel_manager": ["Cloudbeds"],
  "ota_presence": ["Booking.com", "Tripadvisor"],
  "tech_signals": ["Cloudbeds", "Booking.com", "Tripadvisor"],
  "latitude": 31.6295,
  "longitude": -7.9811,
  "osm_type": "node",
  "osm_id": 123456789,
  "source": "openstreetmap",
  "has_email": true,
  "has_phone": true,
  "has_website": true
}

email is the primary contact address (listing email, or the first one found on the site); emails holds every address discovered while crawling. tech_signals is channel_manager + ota_presence flattened for one-column filtering.

Example output

A real sample from a live run:

Name	City	Type	Phone	Email	Website	Tech signals
Hotel Almas	Marrakech	hotel	+212 524 425540	reservation@hotelalmasmarrakech.com	http://www.hotelalmasmarrakech.com/	Booking.com, Tripadvisor
Riad Christina		guest_house	+212 5 24 38 43 84	contact@riadchristina.com	https://www.riadchristina.com/	eviivo, Booking.com, Expedia
Riad Papillon		guest_house	+44 20 7193 7357	contact@marrakech-riad.co.uk	https://www.marrakech-riad.co.uk/marrak…	Beds24
Imouzzer		hotel		contact@hotel-imouzzer.com	https://www.hotel-imouzzer.com/	Tripadvisor

Pricing

This actor uses Apify pay-per-event pricing: you're charged per lead returned, via a result event fired once per accommodation in the dataset. No subscription, no charge for empty runs — if a city yields nothing, you pay nothing. A free Apify plan is enough to try it: run a mid-size city and inspect the emails and tech signals before spending anything. See the actor's Pricing tab for the current per-result rate.

Tips & FAQ

Where does the data come from?

Discovery uses OpenStreetMap (Nominatim + Overpass) queried live at run time; enrichment crawls each property's own public website live during the run. Nothing comes from a cached database, so emails and tech signals reflect what's online today.

Why OpenStreetMap and not Booking.com?

Booking.com is heavily bot-protected and scraping it requires expensive residential proxies. OpenStreetMap gives the same sellable core — accommodation owner contacts by city — reliably and cheaply, and the website crawl adds the emails and tech signals Booking.com wouldn't expose anyway. The trade-off: coverage depends on how well-mapped a city is. Major tourist destinations are mapped very thoroughly; a rural area may return fewer properties than actually exist.

How accurate is the tech-stack detection?

Detection is signal-based: the crawler looks for platform-specific domains and script references (e.g. cloudbeds, siteminder, booking.com) in each site's HTML. It's reliable when the platform has a public-facing widget or link on the site. A property using a PMS purely in the back office, with no embed on its website, won't show a signal — treat an empty channel_manager as "no public signal", not proof of no system.

Why do some properties have no email?

Not every property lists an email on its website, and some have no website at all. Set onlyWithEmail: true to keep the output cold-email-ready, and raise maxPagesPerSite to dig deeper into larger sites. Verify the addresses with the Bulk Email Verifier before sending a campaign.

Do I need an API key or proxies?

No. Both OpenStreetMap and the property websites are queried directly — no API keys, no anti-bot bypass, and it runs fine on datacenter IPs.

Is it legal?

The actor only reads publicly available data: OpenStreetMap listings and each property's own public web pages. It doesn't log in or bypass any access controls. Follow applicable outreach laws (CAN-SPAM, GDPR, etc.) when you contact the leads.

Related actors

• Bulk Email Verifier — verify and score every scraped email before you send a campaign
• Restaurant Leads Scraper — the same enrichment approach for restaurants, with POS / reservation / delivery stack detection
• Local Business Leads — any local business category by city, with website platform detection

Found a bug or need a feature? Open an issue on the actor's Issues tab — typical response within 1 business day.