Pricing

Rating

Developer

Actor stats

Categories

Share

Bing Maps Business Scraper

Scrapes business listings from Bing Maps and outputs clean, structured data — no HTML in the output.

How it works

The core scraping logic is based on the original Bing Maps Scraper script, which discovered that Bing's /maps/overlaybfpr overlay endpoint returns listing anchors (a.listings-item) with rich data-entity JSON blobs embedded as attributes. This actor parses those blobs into flat, structured records.

What this Apify actor adds on top of the original script:

• Apify proxy integration — residential, datacenter, or custom proxy support to avoid IP blocking at scale.
• Multi-query batching — run many searches in a single actor run.
• Automatic deduplication — removes duplicate name + address pairs across queries.
• Retry with backoff — failed requests are retried up to N times with increasing delays.
• Structured dataset output — results pushed to Apify dataset, exportable as JSON, CSV, or Excel.

Output fields

Input example

{
"queries":[
"restaurants San Francisco",
"coffee shops Portland OR"
],
"maxResultsPerQuery":100,
"market":"en-US",
"includeRawJson":false,
"deduplicateByName":true,
"delayBetweenRequests":2000,
"maxRetries":3,
"proxyConfiguration":{
"useApifyProxy":true,
"apifyProxyGroups":["RESIDENTIAL"]
}
}

Input reference

Proxy configuration

Using a proxy is strongly recommended. Without one, Bing may block or throttle requests after a handful of queries.

Apify Proxy (recommended)

Select a proxy group in the Apify console, or pass it in the input:

{
"proxyConfiguration":{
"useApifyProxy":true,
"apifyProxyGroups":["RESIDENTIAL"]
}
}

Available groups:

Apify Proxy with country targeting

To get results localized to a specific country:

{
"proxyConfiguration":{
"useApifyProxy":true,
"apifyProxyGroups":["RESIDENTIAL"],
"apifyProxyCountry":"US"
}
}

Custom / external proxy

If you have your own proxy provider:

{
"proxyConfiguration":{
"useApifyProxy":false,
"proxyUrls":[
"http://user:pass@proxy-host:8080"
]
}
}

No proxy (not recommended)

Omit the proxyConfiguration field entirely. The actor will connect directly. Suitable only for small, one-off runs.

Running locally

# Install the Apify CLI
npminstall-g apify-cli
# Run with a local input file
apify run --input-file input.json

Output

Results are pushed to the default Apify dataset. You can export them from the Apify console as JSON, CSV, or Excel. All fields are flat except hours (day → time object) and the optional rawEntity.