Yandex Maps Place Scraper

One Yandex Maps organisation read in full from its id or its page address. The row carries the rating with its rating and review counts kept apart, the phone numbers, the websites, the social and booking links, the opening hours with the current open state, every category the organisation is filed under, its amenity features, the chain it belongs to, nearby metro stations, the coordinates and the photo count.

This is the lookup for a business you already know. If you are reading an area rather than a list, Yandex Maps Scraper returns twenty-five organisations per request with the same contact details already on each row, and a row there costs a twenty-fifth of a row here.

Accepted input

placeUrls is required and takes one organisation per line, as either the numeric id (1018907821) or the page address (https://yandex.com/maps/org/pushkin/1018907821/). Both are accepted in the same list and both reduce to the same value: the slug in front of the id on that address is decoration, and the id is the key.

Every Yandex Maps Scraper row publishes both, as id and as url, which is how the two Actors compose without an address ever being assembled.

language picks the language titles, addresses and opening hours come back in: English, Russian, Turkish or Ukrainian. That is a closed set — a locale outside it is refused upstream rather than falling back.

maxItems defaults to 100 and caps how many organisations the run reads. One organisation is one request and one row here, so it is a cap on the list rather than on a page of results.

{
  "placeUrls": [
    "1018907821",
    "https://yandex.com/maps/org/pushkin/1018907822/"
  ],
  "language": "en_US",
  "maxItems": 100
}

Response fields

{
  "requested_place": "1018907821",
  "id": "1018907821",
  "type": "business",
  "title": "Pushkin",
  "short_title": "Pushkin",
  "description": "Restaurant",
  "url": "https://yandex.com/maps/org/pushkin/1018907821/",
  "uri": "ymapsbm1://org?oid=1018907821",
  "seoname": "pushkin",
  "address": "Tverskoy Blvd, 26А",
  "full_address": "Moscow, Tverskoy Blvd, 26А",
  "postal_code": "125009",
  "country": "Russia",
  "latitude": 55.7649,
  "longitude": 37.6039,
  "geo_id": 213,
  "metro": [{ "name": "Пушкинская", "distance": 320 }],
  "categories": [{ "name": "Restaurant" }],
  "features": [{ "name": "Average bill", "value": "2500 ₽" }],
  "phones": [{ "type": "phone", "number": "+7 495 739-00-33" }],
  "websites": ["https://cafe-pushkin.ru"],
  "social_links": [{ "type": "instagram", "url": "…" }],
  "business_links": [{ "type": "booking", "url": "…" }],
  "working_time_text": "Daily, 12:00 AM – 12:00 AM",
  "working_status": { "open": true },
  "status": null,
  "rating_value": 4.6,
  "rating_count": 15219,
  "review_count": 6001,
  "photo_count": 4210,
  "chain": null
}

Fields absent from a record are returned as null rather than omitted, so every row has the same shape.

rating_count and review_count are two different numbers and both are published. Yandex counts people who rated separately from people who wrote, and the second is the one Yandex Maps Reviews Scraper pages through. A single column called "reviews" would silently be one of the two, and it is the wrong one to plan a review harvest against. The run log states both for every organisation it reads.

working_time_text is the opening hours as one line, in the requested language. working_status is Yandex's own structured open-or-closed state at the moment of the read, and status is where a permanently-closed marker appears.

categories, features, phones, websites, social_links, business_links, metro, chain and working_status are republished in Yandex's own shape. There is no measured field list to rename them into, and renaming fields nobody has seen populated publishes a permanently-null column and calls it a schema.

requested_place is echoed back after cleaning, so a run given a mix of ids and pasted links can be matched to what each resolved to.

Behaviour on partial results

An organisation that no longer resolves is skipped with a line in the run log and the rest of the list still runs — twenty ids taken from a search last week will not all still be listed, and losing nineteen good rows to one closed restaurant is the wrong trade.

An entry that is not an organisation is skipped before any request is made, with a message naming the shape.

An organisation with no rating and no reviews is a successful row. Coverage is deepest in Russia and the CIS: a Moscow restaurant carried 15,219 ratings and 6,001 written reviews while Manhattan coffee shops carried none. That is real sparsity in Yandex's data rather than a field this Actor failed to read.

Frequently asked questions

Why would I use this instead of the Maps search? When you already know which businesses you want. The search returns twenty-five organisations per request with the same contact details on each row, so reading an area through this Actor would cost twenty-five times as much for the same data. Use it for a watchlist, for refreshing a set of ids you already collected, or for the handful of businesses a search gave you.

Where do I get organisation ids? From Yandex Maps Scraper — every row publishes both an id and a url, and either works here. A link copied from a browser works too.

What is the slug in front of the id on the address? Decoration. /maps/org/pushkin/1018907821/ and /maps/org/1018907821/ are the same page, and the id is the key. That is why a link and a bare id reduce to the same value here.

Why are there two review numbers? Because Yandex counts ratings and written reviews separately. rating_count is everyone who gave stars; review_count is the subset who wrote something, and it is the one a reviews export can actually reach. Planning a harvest against the first number overstates it, often by a factor of two or more.

The row has no phone number. Is it missing? No — the organisation publishes none. This Actor reads the same card a visitor sees, and a business that does not list a phone number on Yandex Maps does not have one there to read.

Is a Yandex account or API key required? No. No account, session cookie or key of any kind is supplied to the Actor or needed by it. Open the url on any row and you see the same record.

Related Actors

Yandex Maps Scraper is where the ids come from: organisations by name, category or address, centred anywhere in the world, twenty-five to a request with the contact details already attached.

Yandex Maps Reviews Scraper takes the same ids and exports the written reviews, with the reviewer's contributor level and Yandex's own per-aspect summary.

Yandex Search Scraper is the other half of this site: web results with paid placements flagged on every row.