OSM POI Scraper — Leads by Category & Area

What this Actor scrapes

Point this Actor at a place name or a bounding box, pick a business category, and get a flat lead list pulled straight from OpenStreetMap's Overpass API — name, street address, phone, website, email, opening hours and coordinates for every matching dentist, restaurant, gym, hotel, car repair shop, pharmacy, EV charging station, supermarket or café in the area. No API key, no map-tile scraping — just the business records local lead-gen agencies, franchise-siting analysts and field-sales teams actually need.

What we handle for you

• 🌐 Two verified public endpoints — Overpass API for the POI query, Nominatim for place-name-to-bbox resolution — both keyless, no account or API key to manage.
• 🔁 Retries with exponential backoff on 429 (rate-limited) and 504 (query timeout) — up to 5 attempts, Retry-After honoured, other 4xx failures reported immediately instead of retried blind.
• 🧱 Self-throttled pacing — at least 1 second between outbound requests, so we stay inside Overpass's shared fair-use budget instead of getting rate-limited in the first place.
• 🏷️ Category-aware tag mapping — plain-English categories (dentist, gym, car_repair, ...) translate to the right OSM tag combinations, including the ones a naive query would miss.
• 🧊 Node, way and relation coverage — building-outline POIs (not just point nodes) are included via out center, so results aren't silently missing half the map.
• 💰 Pay-Per-Event pricing — you only pay for results that land in your dataset. No data, no charge beyond the small warm-up fee.

Use cases

• Local lead generation — pull every business of a category in a city or neighborhood as a ready-to-dial list.
• Franchise siting — map competitor and complementary-business density before picking a new location.
• Field-sales territory planning — export addresses and coordinates for route mapping.
• Market research — count and profile businesses by category across regions without a maps API key.

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

{
  "placeName": "Helsinki, Finland",
  "bbox": [
    60.15,
    24.9,
    60.2,
    24.98
  ],
  "category": "dentist",
  "maxResults": 3,
  "timeoutSeconds": 25,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

namecategorystreetcityphonewebsitelatitudelongitudeosm_link

{
  "name": "Hammaslaakariasema Esplanadi",
  "category": "dentist",
  "street": "Pohjoisesplanadi",
  "housenumber": "31",
  "city": "Helsinki",
  "postcode": "00100",
  "country": null,
  "phone": "+358 9 1234567",
  "website": "https://example-dental.fi",
  "email": null,
  "opening_hours": "Mo-Fr 08:00-18:00",
  "latitude": 60.1682,
  "longitude": 24.9457,
  "osm_id": 123456789,
  "osm_type": "node",
  "osm_link": "https://www.openstreetmap.org/node/123456789"
}

Pricing

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.

Limitations

• Coverage depends entirely on OpenStreetMap's own tagging density in the target area — well-mapped cities return rich results, sparsely-mapped regions return fewer than a proprietary maps API would.
• No reverse-geocoding or address enrichment when addr:* tags are missing on the source OSM element — the field comes back null rather than guessed.
• The category list is a fixed 9-item enum in v1 (dentist, restaurant, gym, hotel, car_repair, pharmacy, ev_charging, supermarket, cafe). The advanced rawOverpassQuery field is available for anything outside that list.
• Only bounding-box and place-name area input is supported — no custom polygon shapes.