# Avito RU $1💰 URL | Keyword Filters | Enriched Output (`abotapi/avito-ru-scraper`) Actor

From $1/1k. Pull structured listing data from avito.ru by region, category, or direct URL. Supports filters and auto-pagination. Returns 25+ fields per listing, including price, full address, metro details, images, posting date, seller type, and verification badges.

- **URL**: https://apify.com/abotapi/avito-ru-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:** E-commerce, Real estate, Developer tools
- **Stats:** 287 total users, 53 monthly users, 99.7% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $1.00 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Avito.ru Scraper

Pull structured listing data from avito.ru, the largest classifieds portal in Russia, in seconds. Search by region and category with filter inputs, or paste any avito.ru URL and the scraper walks pagination forward. Returns 25+ fields per listing including price, full address, metro station and walking distance, photo gallery URLs, posting date, seller type and verification badges.

### Why this scraper

- 25+ fields per listing (most competitors expose 10-12)
- Supports both modes: build a search from filters, or paste URLs verbatim
- All categories covered: apartments, houses, cars, motorcycles, jobs, services, electronics, home, hobbies, animals, and more
- All regions: moskva, sankt-peterburg, novosibirsk, rossiya (all of Russia), 80+ regional slugs
- Forward-paging from any URL (start at page 5, walk to page 20)
- Rich SERP output by default: title, price, full description, photo gallery, address, metro, seller name, badges — no detail fetch needed
- Optional detail-page enrichment (`fetchDetails`) adds the structured attribute table (rooms, area, floor, etc.), view counts, and seller stats
- **Resume and recurring updates.** Turn on Incremental mode to get only NEW, UPDATED, and REAPPEARED listings on every scheduled run, or resume one specific interrupted crawl with `resumeFromRunId`
- HTTP-only architecture, ~50 listings/second on Apify Residential proxy
- Around $1.50 per 1000 listings on the cheapest plan

### Data you get

> Sample shape, values are illustrative placeholders, not from a live listing.

| Field | Example |
|---|---|
| id | `0000000000` |
| url | `https://www.avito.ru/moskva/kvartiry/listing-title-slug_0000000000` |
| title | `Sample listing title in Russian` |
| price | `12345678` |
| currency | `RUB` |
| priceText | `12 345 678 ₽` |
| category | `kvartiry` |
| subcategory | `prodam` |
| region | `moskva` |
| city | `moskva` |
| address | `ЖК «Образцовый», ул. Примерная, 4` |
| street | `ул. Примерная` |
| metro | `Образцовая` |
| metroId | `0` |
| metroDistanceMin | `10` |
| postedDate | `1 января` |
| description | `Full listing description text (returned in every run, no detail fetch needed).` |
| photoUrls | `["https://90.img.avito.st/image/1/1.example", "..."]` |
| photoCount | `5` |
| badges | `["Sample badge text"]` |
| isVerified | `true` |
| sellerName | `Agent Name` |
| sellerType | `agency` |
| sellerRating | `0.0` |
| sellerReviewsCount | `0` |
| sellerSince | `На Авито с YYYY года` |
| viewsCount | `0` |
| attributes | `{"Sample attribute key": "Sample value"}` |

### How to use

#### Search by filters (recommended)

```json
{
  "mode": "search",
  "regions": ["moskva"],
  "category": "kvartiry",
  "dealType": "prodam",
  "minPrice": 1000000,
  "maxPrice": 9000000,
  "sortBy": "price_asc",
  "maxPages": 5,
  "maxListings": 250,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

#### Cars in all of Russia, free-text search

```json
{
  "mode": "search",
  "regions": ["rossiya"],
  "category": "avtomobili",
  "query": "tesla model 3",
  "sortBy": "date_desc",
  "maxPages": 3,
  "maxListings": 150,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

#### Multi-region rentals with private sellers only

```json
{
  "mode": "search",
  "regions": ["moskva", "sankt-peterburg"],
  "category": "kvartiry",
  "dealType": "snyat",
  "ownerOnly": true,
  "maxPrice": 80000,
  "maxPages": 5,
  "maxListings": 200,
  "fetchDetails": true,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

#### Direct URLs (multi)

```json
{
  "mode": "url",
  "urls": [
    "https://www.avito.ru/moskva/kvartiry/prodam?p=2",
    "https://www.avito.ru/sankt-peterburg/avtomobili?q=BMW"
  ],
  "maxPages": 3,
  "maxListings": 200,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

### Input parameters

| Parameter | Type | Default | Description |
|---|---|---|---|
| `mode` | string | `search` | Either `search` (use filters) or `url` (use direct URLs) |
| `regions` | string\[] | `["moskva"]` | Region slugs. Use `rossiya` for all of Russia |
| `category` | string | `kvartiry` | Top-level category slug (apartments, cars, jobs, services, etc.) |
| `dealType` | string | `prodam` | `prodam` (sale), `snyat` (rent), `kupit` (wanted), `sdam` (lease). Property categories only |
| `query` | string | empty | Free-text query, matches title and description |
| `minPrice` | int | empty | Minimum price in rubles |
| `maxPrice` | int | empty | Maximum price in rubles |
| `sortBy` | string | `default` | `default`, `date_desc`, `price_asc`, `price_desc` |
| `ownerOnly` | bool | false | Restrict to private (non-pro) sellers |
| `urls` | string\[] | empty | Direct avito URLs. URL mode only |
| `maxPages` | int | empty (unlimited) | Optional bound on pages walked per region/URL (about 50 listings/page). Leave empty to walk every result page; defers to `maxListings` |
| `maxListings` | int | 20 | Total cap across all searches. 0 = unlimited |
| `fetchDetails` | bool | false | Visit each listing for full description, all photos, seller stats |
| `proxy` | object | Apify Residential | Proxy configuration |
| `resumeFromRunId` | string | empty | Previous run ID or dataset ID to continue ONE interrupted crawl without re-returning/re-charging listings it already collected. See "Resume and recurring updates" below |
| `incrementalMode` | bool | false | Recurring monitoring of the same search/URL set: returns only `NEW`/`UPDATED`/`REAPPEARED` listings against a remembered baseline. See "Resume and recurring updates" below |
| `stateKey` | string | empty | Incremental mode only. Name a monitoring campaign, or deliberately share state across differently-configured runs. Leave empty to derive one automatically |
| `emitUnchanged` | bool | false | Incremental mode only. Also return `UNCHANGED` listings. Off by default — returns and bills rows you already have |
| `emitExpired` | bool | false | Incremental mode only. Also return `EXPIRED` listings once a run fully scans every tracked region/URL. Off by default — returns and bills extra synthetic rows |

### Resume and recurring updates

Two distinct workflows share the same "🔁 Resume and recurring updates" input section:

- **`resumeFromRunId`** continues ONE specific interrupted run. Paste a previous run ID or dataset ID and this run skips every listing that run already collected, picking up where it left off — useful after a run was stopped early or hit an error partway through a large pull.
- **`incrementalMode`** is for running the SAME search or URL set again and again (daily, weekly, on a schedule) and getting only what changed. It remembers the previous run's listings in a dedicated key-value store, keyed automatically from the mode, regions/URLs, category, and filter settings (or your own `stateKey` if you want to name or deliberately share a campaign) — so two differently-configured runs never mix their baselines. `regions` is a list, hashed order-independently, so `["moskva","spb"]` and `["spb","moskva"]` resolve to the same state. Every listing is classified as `changeType`: `NEW` (first time seen), `UPDATED` (a comparable field changed — see `changedFields`), `REAPPEARED` (was gone, is back), or, with `emitExpired` on and only once a run has fully scanned every tracked region/URL to a confirmed end of results, `EXPIRED` (was tracked, no longer found). `UNCHANGED` listings are tracked but not returned unless `emitUnchanged` is on — both extra-emission toggles are off by default because they return, and bill, rows you already have.
- `incrementalMode` defaults to `false` — a normal run's behavior and output shape are unchanged until you opt in. Combining it with `resumeFromRunId` bootstraps a brand-new monitoring campaign from that resumed crawl's results; if a baseline already exists for the derived (or given) state key, the run fails fast rather than silently mixing the two.

### Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step **after** the scrape — the Apify dataset is never changed.

**What gets written to the connector:** a condensed, human-readable **summary** of each record — not the full JSON. Each item becomes one entry with a **title** and its key fields flattened to plain text. The **complete record always stays in the Apify dataset**.

1. Authorize a connector once under **Apify → Settings → Integrations** (Notion, Linear, Airtable, or Apify).
2. Select it in the **"Pipe results into your apps"** input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For **Notion**, also set `notionParentPageUrl` to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

### Output example

> Sample shape, values are illustrative placeholders, not from a live listing.

```json
{
  "id": "0000000000",
  "url": "https://www.avito.ru/moskva/kvartiry/listing-title-slug_0000000000",
  "title": "Sample listing title in Russian",
  "price": 12345678,
  "currency": "RUB",
  "priceText": "12 345 678 ₽",
  "category": "kvartiry",
  "subcategory": "prodam",
  "region": "moskva",
  "city": "moskva",
  "address": "ЖК «Образцовый», ул. Примерная, 4",
  "street": "ул. Примерная",
  "metro": "Образцовая",
  "metroId": 0,
  "metroDistanceMin": 10,
  "postedDate": "1 января",
  "description": "Full listing description text (returned in every run, no detail fetch needed).",
  "photoUrls": [
    "https://90.img.avito.st/image/1/1.example",
    "https://70.img.avito.st/image/1/1.example"
  ],
  "photoCount": 2,
  "badges": ["Sample badge text"],
  "isVerified": true,
  "sellerName": "Agent Name",
  "sellerType": "agency",
  "sellerRating": 0.0,
  "sellerReviewsCount": 0,
  "sellerSince": "На Авито с YYYY года",
  "viewsCount": 0,
  "attributes": {
    "Sample attribute key": "Sample value",
    "Another attribute key": "Another value"
  }
}
```

### Plan requirement

Avito accepts traffic from residential connections only. The free Apify plan does not include the Residential proxy add-on.

- **Apify Starter, Scale, or higher**: Residential proxy is included. Use the prefilled `proxy.useApifyProxy = true, apifyProxyGroups = ["RESIDENTIAL"]`.
- **Apify Free**: bring your own residential proxy via `proxy.proxyUrls`. Datacenter proxies will be rejected by the upstream edge.

For best results, leave the country code empty so the actor picks the cleanest available exit on each rotation. Per-page bandwidth averages 1.2 MB; a 100-listing run typically uses 30-50 MB of residential traffic.

### Verification

URL mode (shell and tokenized links) and the price filter re-verified against the live site on 2026-08-30: an unfiltered Moscow apartments page serves listings above 1.7 billion rubles, while the same search with a 15 million ruble ceiling returns only listings at or under 14.8 million.

# Actor input Schema

## `mode` (type: `string`):

Pick how you want to find listings. 'Search by filters' resolves a region + category + filters into a search URL automatically. 'Direct URLs' takes one or more avito.ru URLs you have already copy-pasted from your browser.

## `regions` (type: `array`):

Region slugs (Search mode only). Examples: 'moskva', 'sankt-peterburg', 'rossiya' (all of Russia). Multiple regions are scraped sequentially. Default: moskva.

## `category` (type: `string`):

Top-level category. Pick the kind of listings you want.

## `dealType` (type: `string`):

Sale or Rent. Only applies to property categories (apartments, houses, rooms, garages, commercial, land). Ignored for other categories. Avito only exposes two top-level deal types per category; the slugs are 'prodam' (sale) and 'sdam' (rent, long-term).

## `query` (type: `string`):

Optional text query (matches titles and descriptions). E.g. 'tesla', 'iPhone 15', 'студия у метро'.

## `minPrice` (type: `integer`):

Minimum price in rubles. Leave empty for no minimum.

## `maxPrice` (type: `integer`):

Maximum price in rubles. Leave empty for no maximum.

## `sortBy` (type: `string`):

How to order results.

## `ownerOnly` (type: `boolean`):

If true, exclude agency / professional sellers, return only private (С/Собственник) postings.

## `urls` (type: `array`):

Avito.ru search/category URLs to scrape (URL mode only). Multi-URL supported. Filter-mode fields are ignored. Pagination starts at the page in the URL and walks forward.

## `maxPages` (type: `integer`):

Optional bound on result pages walked per region/URL. Avito returns ~50-60 listings per page. Leave empty to walk every result page (the run size is controlled by Max listings, which this field defers to).

## `maxListings` (type: `integer`):

Hard global cap on total listings written to the dataset across ALL searches (every region in search mode, every URL in URL mode). The actor stops as soon as this number is reached. Set 0 for unlimited (subject to maxPages).

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

Lean mode is the default (false): the SERP card alone already returns 27 of 38 fields — full description, address, metro, photos, badges, rooms, area, floor — and runs ~8x faster and far cheaper. Enable (true) to additionally fetch each listing's detail page for the 21-key attributes dict (floor, ceilings, balcony type, parking, etc.), full photo gallery, view counts, and seller stats — the remaining 11 fields, for 38 total. Enrichment fetches one extra page per listing, so it is much slower and more expensive on high-volume scrapes.

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

Optional. ID of a previous run of this actor (or a dataset ID). Listings already in that dataset are skipped, so this run returns only NEW listings (a delta). Combine both runs' datasets for the full set. Max listings then counts only the new listings. For recurring monitoring of the same search, use Incremental mode below instead.

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

Turn this on for daily or recurring monitoring. The first run returns all matching listings as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED listings. Turn on "Emit unchanged" or "Emit expired" only when you also want those listings returned (and billed). State is kept separately for each mode/region/category/filter setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.

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

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the mode, regions/URLs, category, and filter settings -- different searches then never mix state with each other.

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

Off by default. Turn on to also return listings that have not changed since the last run, marked UNCHANGED. This returns -- and bills -- extra rows you already have, so leave it off unless you specifically want the full snapshot every run.

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

Off by default. Turn on to also return listings that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned every tracked region/URL to a confirmed end of results -- not when Max listings capped it or when Resume was used. This returns -- and bills -- extra synthetic rows, so leave it off unless you need expiry tracking.

## `proxy` (type: `object`):

Default: Apify Proxy with the RESIDENTIAL pool — the most reliable option for this site, which rejects datacenter and unknown source IPs. When RESIDENTIAL is on and no country is pinned, the actor rotates the exit country per session across a Russia + EU pool for the best success rate. To pin a single country, set Country in this section. Datacenter or no-proxy runs are allowed but warn at start and return fewer items.

## `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 item (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 items written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "regions": [
    "moskva"
  ],
  "category": "kvartiry",
  "dealType": "prodam",
  "sortBy": "default",
  "ownerOnly": false,
  "urls": [
    "https://www.avito.ru/moskva/kvartiry/prodam"
  ],
  "maxListings": 20,
  "fetchDetails": false,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "maxNotifyListings": 50
}
```

# 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 = {
    "mode": "search",
    "regions": [
        "moskva"
    ],
    "urls": [
        "https://www.avito.ru/moskva/kvartiry/prodam"
    ],
    "fetchDetails": false,
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false,
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/avito-ru-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 = {
    "mode": "search",
    "regions": ["moskva"],
    "urls": ["https://www.avito.ru/moskva/kvartiry/prodam"],
    "fetchDetails": False,
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/avito-ru-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 '{
  "mode": "search",
  "regions": [
    "moskva"
  ],
  "urls": [
    "https://www.avito.ru/moskva/kvartiry/prodam"
  ],
  "fetchDetails": false,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call abotapi/avito-ru-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/avito-ru-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/km2oo0mCahDBKPOa6/builds/11nvECfRSGr4ANIla/openapi.json