# Yandex Maps Scraper / Парсер Яндекс Карт - Businesses & Places (`abotapi/yandex-maps-scraper`) Actor

Scrape businesses and places from Yandex Maps by search term or URL for research, leads and market analysis. Парсер Яндекс Карт: собирайте данные о компаниях и местах по запросу или ссылке для поиска клиентов, исследований и анализа рынка.

- **URL**: https://apify.com/abotapi/yandex-maps-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.80 / 1,000 business records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Yandex Maps Scraper

Apify Actor for scraping Yandex Maps business search results.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `searchStringsArray` | string\[] | Search queries to run on Yandex Maps. |
| `startUrls` | string\[] | Direct Yandex Maps targets (business, category, or search pages) to scrape alongside the keyword search. Both feeds merge into one dataset. |
| `location` | string | Free-text region for keyword searches, resolved to map coordinates via the open OpenStreetMap geocoder. Ignored by `startUrls`. |
| `maxResultsPerSearch` | integer | Maximum businesses to save per search. Default `20`. |
| `maxPagesPerSearch` | integer | SERP pages walked per search (25 businesses each). `0` (default) = no page cap. |
| `includeRaw` | boolean | Include the matched raw Yandex response object per row, for debugging. Default `false`. |
| `fetchDetails` | boolean | Open each business page for reviews, opening hours, and photo totals. Off = faster, search-card-only rows. Default `true`. |
| `maxReviews` | integer | Per-business review count when `fetchDetails` is on. Default `3`. Billing scales with volume (1 extra unit per started block of 10 reviews). |
| `language` | string | Browser locale. Default `en-US`. |
| `resumeFromRunId` | string | Paste a previous run ID or dataset ID to continue a full-catalogue walk; businesses already collected there are skipped. |
| `incrementalMode` | boolean | Recurring monitoring: reruns the same search and classifies each business as NEW / UPDATED / UNCHANGED / REAPPEARED / EXPIRED. Default `false`. |
| `stateKey` | string | Optional. Name the incremental baseline explicitly. Auto-derived from the search settings when left empty. |
| `emitUnchanged` | boolean | Incremental mode only. Also save UNCHANGED businesses. Default `false`. |
| `emitExpired` | boolean | Incremental mode only. Also save a row for businesses no longer found, once the walk reaches its natural end. Default `false`. |
| `proxyConfiguration` | object | Apify Proxy settings. Datacenter (no group) by default; pick `RESIDENTIAL` if the datacenter pool is refused. |
| `mcpConnectors` | array | Optionally send results into the apps you already use via Model Context Protocol (MCP) connectors (Notion, Linear, Airtable, Apify). Leave empty to skip; never changes the dataset output. |
| `notionParentPageUrl` | string | Notion connector only: URL or id of the Notion page under which item pages are created. |
| `maxNotifyListings` | integer | Cap on businesses written to each connector per run. Does not affect the dataset. |

#### Example input

```json
{
  "searchStringsArray": ["coffee"],
  "location": "Melbourne",
  "maxResultsPerSearch": 20,
  "maxPagesPerSearch": 5
}
```

### Output

Each dataset item contains the Yandex business ID, title, URL, address, categories, coordinates, search context, and scrape timestamp. Set `includeRaw` to `true` when debugging response parsing.

### Notes

- Keyword searches resolve `location` to map coordinates through the open OpenStreetMap geocoder; direct URLs skip that step.
- With `fetchDetails` on, each business page is read for reviews and extra info, and rows bill the `detail-enrichment` surcharge (1 unit per row plus 1 per started block of 10 reviews).

# Actor input Schema

## `searchStringsArray` (type: `array`):

Search queries to run on Yandex Maps.

## `startUrls` (type: `array`):

Direct Yandex Maps targets to scrape - one search, category, or business page per row. Example: https://yandex.com/maps/org/no\_plates\_coffee/124606085044/ (a real business page; rows carry its address, phones, hours, and reviews).

## `location` (type: `string`):

Free-text region for keyword searches (resolved to map coordinates via the open OpenStreetMap geocoder). Ignored by startUrls.

## `maxResultsPerSearch` (type: `integer`):

Maximum businesses to save per search.

## `maxPagesPerSearch` (type: `integer`):

SERP pages walked per search (25 businesses each). 0 = no page cap - Max results per search is the only cap that stops a walk early.

## `includeRaw` (type: `boolean`):

Include the matched raw Yandex response object in each dataset row for debugging.

## `fetchDetails` (type: `boolean`):

Open each business page and read its reviews, opening hours and photo totals. Turn OFF for fast, search-card-only rows

## `maxReviews` (type: `integer`):

Per-business review count when details mode is on. Billing scales with volume: the detail-enrichment surcharge bills 1 unit per enriched row plus 1 unit per started block of 10 reviews (10 reviews = 1 extra unit, 25 = 3, 1000 = 101) - heavy review pulls bill their transfer.

## `language` (type: `string`):

Browser locale.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue a full-catalogue walk across separate runs. Businesses already collected there (matched by business id) are skipped, so this run only saves the new ones. Leave empty for a normal fresh run. Distinct from Incremental mode below — this continues one specific interrupted run, not recurring monitoring.

## `incrementalMode` (type: `boolean`):

When ON, this actor remembers the previous run of the SAME search (see State key) and classifies each business as NEW / UPDATED / UNCHANGED / REAPPEARED / EXPIRED. UNCHANGED and EXPIRED rows are not saved to the dataset unless enabled below — this is what keeps a scheduled recurring run cheap. Default OFF (every run returns every business, as today). Combining with Resume from a previous run above is only safe on the very first incremental run (no baseline yet) — once a baseline exists, remove Resume from a previous run or set a different State key.

## `stateKey` (type: `string`):

Manually name the incremental baseline for this search, e.g. "nyc-coffee". Leave empty to auto-derive one from the search settings — two runs with the exact same search settings then share a baseline automatically. Set this explicitly if you want to run several DIFFERENT search configs against the SAME named baseline, or keep configs that happen to match fully separate.

## `emitUnchanged` (type: `boolean`):

When ON, incremental mode also saves businesses with no detected change (changeType="UNCHANGED") to the dataset, instead of only NEW/UPDATED/REAPPEARED. This returns — and bills for — every business every run, defeating the point of incremental mode for most use cases. Default OFF.

## `emitExpired` (type: `boolean`):

When ON, incremental mode also saves a row (changeType="EXPIRED") for each previously-tracked business that no longer appears, once this run reaches the natural end of the search results (skipped on a capped, resumed, or otherwise incomplete run — those cannot tell "gone" apart from "not reached yet"). This returns — and bills for — an extra row per disappeared business. Default OFF.

## `proxyConfiguration` (type: `object`):

Apify Proxy settings used for all requests. Datacenter (no group) by default; pick RESIDENTIAL when the datacenter pool is refused.

## `mcpConnectors` (type: `array`):

Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per business (title + key fields), not the full JSON — the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on businesses written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "searchStringsArray": [
    "restaurants"
  ],
  "startUrls": [
    {
      "url": "https://yandex.com/maps/org/no_plates_coffee/124606085044/"
    }
  ],
  "location": "New York, NY",
  "maxResultsPerSearch": 20,
  "maxPagesPerSearch": 0,
  "includeRaw": false,
  "fetchDetails": true,
  "maxReviews": 3,
  "language": "en-US",
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchStringsArray": [
        "restaurants"
    ],
    "startUrls": [
        {
            "url": "https://yandex.com/maps/org/no_plates_coffee/124606085044/"
        }
    ],
    "location": "New York, NY",
    "maxResultsPerSearch": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/yandex-maps-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchStringsArray": ["restaurants"],
    "startUrls": [{ "url": "https://yandex.com/maps/org/no_plates_coffee/124606085044/" }],
    "location": "New York, NY",
    "maxResultsPerSearch": 20,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/yandex-maps-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchStringsArray": [
    "restaurants"
  ],
  "startUrls": [
    {
      "url": "https://yandex.com/maps/org/no_plates_coffee/124606085044/"
    }
  ],
  "location": "New York, NY",
  "maxResultsPerSearch": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call abotapi/yandex-maps-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/yandex-maps-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/SN6AdkrVpugyTz56F/builds/SaABqyBCY3zOKRm4I/openapi.json