# 2GIS Reviews Scraper — Written Reviews by Source (`thenetaji/2gis-reviews-scraper`) Actor

Export a 2GIS business's written reviews with the stars, full text, both dates, the reviewer's name and review count, the photo count and the business's own reply. Each row names which source it came from, because 2GIS aggregates Flamp, Booking and others under one listing.

- **URL**: https://apify.com/thenetaji/2gis-reviews-scraper.md
- **Developed by:** [The Netaji](https://apify.com/thenetaji) (community)
- **Categories:** Business, Marketing, Automation
- **Stats:** 3 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.17 / 1,000 reviews

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

## 2GIS Reviews Scraper

Every written review of a 2GIS business, as a spreadsheet. Each row carries the stars, the
full text in the language it was written in, both dates, likes and comment counts, how many
photographs the reviewer attached, the reviewer's name, public id and own review count, the
business's reply where it has replied — and one field most review exports do not have.

**Which source the review came from.** 2GIS aggregates its own reviews with Flamp, Booking,
Avito and others under a single listing, and they are not the same corpus. A rating average
that mixes them is a different number from one that does not, so every row names its
`provider` and the row also carries the full list of sources that branch aggregates.

### Accepted input

`placeIds` is required and takes one 2GIS branch id per line — exactly the `id` every [2GIS
Search Scraper](https://apify.com/thenetaji/2gis-search-scraper) row publishes. A 2GIS place
link and the decorated id from a raw 2GIS search response both reduce to the same value and
can be mixed into the same list.

`sort` chooses the ordering. `date_created` is newest first and the default; `date_edited`
puts recently edited reviews first; `friends` and `trust` are 2GIS's social and
trust-weighted orderings. That is 2GIS's own allowed set, quoted from the refusal it returns
for anything else, so there is nothing outside it to offer.

`locale` is optional and takes one of the city's own locales, written as `ru_RU` or `en_AE`.
Leave it empty for the city's default.

`maxItems` defaults to `100` and caps **each business separately**, so twenty businesses with
a cap of 100 returns up to 2,000 rows rather than 100 shared between them. `0` means no limit
— and on this surface no limit genuinely means all of them.

```json
{
  "placeIds": ["70000001007179642"],
  "sort": "date_created",
  "maxItems": 200
}
```

### Response fields

```json
{
  "requested_id": "70000001007179642",
  "review_id": "271440829",
  "review_rating": 5,
  "review_text": "Отлично!)))",
  "date_created": "2026-08-23T03:46:23.263816+07:00",
  "date_edited": null,
  "likes_count": 0,
  "comments_count": 0,
  "photo_count": 2,
  "provider": "2gis",
  "author_id": "54832258",
  "author_name": "Марианна Винокурова",
  "author_public_id": "b5702370dd1141b080fb8693fe2991fc",
  "author_reviews_count": 2,
  "official_answer_text": "Спасибо за отзыв!",
  "official_answer_date": "2026-08-24T09:12:00+07:00",
  "branch_rating": 4.8,
  "branch_review_count": 1091,
  "total_reviews": 1039,
  "providers": ["flamp", "2gis"],
  "sort": "date_created"
}
```

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

**Two review counts are published and they disagree on purpose.** `branch_review_count` is
what the business's place card shows — 1,091 on the measured branch — and `total_reviews` is
how many this endpoint will actually serve — 1,039 on the same one. The difference is
star-only ratings: 2GIS counts them on the card and returns only written reviews here.
Publishing the larger alone makes a complete walk look truncated; publishing the smaller
alone misstates the business. The run log says both at the top of each business.

`provider` names the source of that individual review; `providers` lists every source the
branch aggregates. Filter on `provider` before averaging anything.

The review's own fields are namespaced away from the business's: `review_rating` is the stars
that review gave and `branch_rating` is the business's aggregate, on the same row. A dataset
that used `rating` for both would be unsortable.

`author_reviews_count` is how many reviews that person has written in total, which is the
cheapest signal available for weighting a reviewer's opinion.

### Behaviour on partial results

A branch that no longer resolves is skipped with a line in the run log and the rest of the
list still runs. An entry that is not a branch id is skipped before any request is made.

The walk goes to the end and nothing about it expires. It is an offset counter against the
stated total, not a cursor: a branch stating 1,039 written reviews served all 1,039 and
answered an empty list past that. So an interrupted run resumes exactly where it stopped, and
`maxItems: 0` really does mean every review.

A business with no written reviews is a successful run with no rows. Its `branch_review_count`
can still be non-zero — those are the star-only ratings, and there is no text to return.

### Frequently asked questions

**Why does the business say 1,091 reviews and this Actor returns 1,039?**
Because 2GIS counts star-only ratings on the place card and returns only written reviews
here. Both numbers are on every row, as `branch_review_count` and `total_reviews`, and the
run log states both before the walk starts. A walk that reaches `total_reviews` is complete.

**Some reviews came from Flamp or Booking. Why?**
Because 2GIS aggregates several review sources under one business listing. They are genuinely
attached to that business, but they are not the same corpus and they are not moderated the
same way. `provider` on every row lets you separate them; `providers` lists all of them for
the branch.

**Can I get reviews for a business I only have a name for?**
Not directly. [2GIS Search Scraper](https://apify.com/thenetaji/2gis-search-scraper) is the
lookup by name, and its rows carry the ids this takes.

**Which sort should I use?**
`date_created` for a chronological corpus, which is what most analysis wants. `trust` if you
are reading a handful of reviews and want 2GIS's own idea of the most credible first. The set
is 2GIS's, and nothing outside it is offered because 2GIS refuses anything else outright.

**Does an ordering change which reviews I get, or only their order?**
Only their order, on a complete walk. If you cap the run with `maxItems`, the ordering decides
which slice you keep — which is exactly when `trust` or `date_created` matters.

**Is a 2GIS account or API key required?**
No. No account, session cookie or key of any kind is supplied to the Actor or needed by it.

### Related Actors

[2GIS Search Scraper](https://apify.com/thenetaji/2gis-search-scraper) is where the ids come
from: business search across 206 cities, with a flag on every row saying whether 2GIS matched
the query at all.

[2GIS Business Scraper](https://apify.com/thenetaji/2gis-place-scraper) takes the same ids
and returns the phone numbers, websites and email addresses a search row never carries.

[2GIS Scraper](https://apify.com/thenetaji/2gis-scraper) puts this export and the business
search behind one mode picker, if you would rather run one Actor than two.

# Actor input Schema

## `placeIds` (type: `array`):

2GIS branch ids, one per line — exactly the `id` every search row publishes, which is how these Actors compose. A full 2GIS place link and the decorated id from a raw 2GIS search response are both accepted and reduce to the same value.

## `sort` (type: `string`):

How 2GIS should order the reviews. This is 2GIS's own allowed set, quoted from the refusal it returns for anything else — `friends` and `trust` are its social and trust-weighted orderings.

## `locale` (type: `string`):

One of the city's own locales, written as `ru_RU` or `en_AE`. Leave it empty for the city's default. This is not a translation layer: a locale a city does not offer is refused by 2GIS outright — Dubai serves `en_AE` and refuses `en_US` — and the Covered Cities Actor lists each city's set.

## `maxItems` (type: `integer`):

Maximum reviews to save for each business in the list. Set 0 for no limit. Reviews come 50 to a request and the walk reaches the end — a branch stating 1,039 written reviews served all of them.

## Actor input object example

```json
{
  "placeIds": [
    "70000001007179642"
  ],
  "sort": "date_created",
  "locale": "ru_RU",
  "maxItems": 20
}
```

# Actor output Schema

## `dataset` (type: `string`):

All records scraped by this run

# 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 = {
    "placeIds": [
        "70000001007179642"
    ],
    "sort": "date_created",
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("thenetaji/2gis-reviews-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 = {
    "placeIds": ["70000001007179642"],
    "sort": "date_created",
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("thenetaji/2gis-reviews-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 '{
  "placeIds": [
    "70000001007179642"
  ],
  "sort": "date_created",
  "maxItems": 20
}' |
apify call thenetaji/2gis-reviews-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thenetaji/2gis-reviews-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/aRMBseuey9Je2N3lC/builds/hgfaXbIs5PsvHqO8K/openapi.json