# Avito (Авито) Scraper - Russian Classifieds Listings + Prices (`lanternlab318/avito`) Actor

Collect public Avito listings from any category, filter or keyword page: title, price in RUB, place, category, specs, photos, publish time and the listing URL. No login, no cookies. Rows are deduplicated; empty and partial inputs are reported separately and never charged.

- **URL**: https://apify.com/lanternlab318/avito.md
- **Developed by:** [Lantern Lab](https://apify.com/lanternlab318) (community)
- **Categories:** E-commerce, Real estate, Lead generation
- **Security:** Limited permissions
- **Stats:** 2 total users, 2 monthly users, 89.5% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.49 / 1,000 listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Avito (Авито) Scraper — Listings, Prices & Sellers from Any Category

A Lantern Lab Actor. Give it Avito keywords or any result-list URL you can open in a browser — flats, cars, jobs, electronics, a shop's filter page — and get back every listing on it: **title, price in roubles, place, category, specs, photos, publish time and the listing URL**, plus whether the seller is a shop or a private person. No Avito login, no cookies of your own, no account.

**Price:** you pay per listing row. Inputs that find nothing, pages Avito refused, status rows and the run summary are free, and there is no run-start fee.

### What you get

- **Listings** from a keyword (`searchQueries` + a region) or from any Avito result-list URL (`searchUrls`) — the URL's own filters, sorting and category are kept, and a URL copied from page 3 starts at page 3.
- **price** in RUB out of the card's own microdata, `priceText` as the page prints it (`"от 2 530 000 ₽"`), `null` — never 0 — when the ad names no price.
- **title**, **category**, **params** (`"1.5 AMT (181 л.с.), лифтбек, передний, бензин"`), **description**, **location**, and **street** / **metro** where the card links them.
- **publishedAt** computed from the wording Avito shows, with **publishedAtPrecision** (`minute`, `hour`, `day`, `month`) and the original **publishedAtText**, so an estimate is never passed off as an exact time. Cards Avito shows no date on come back `null`.
- **sellerType**: `company` when the card carries Avito's shop block (then `shopUrl`, `sellerRating` and `sellerReviewsText` come with it), `unknown` otherwise — Avito labels a business seller and says nothing about the rest, and this Actor does not guess. No seller name and no phone number is collected.
- **imageUrls** — every photo the card carries, full size, in card order.
- **Clear status for every input.** An empty result list, a page Avito would not render, a refused request and an input cut short by a limit are four different, labelled records — never confused, never reported as "0 results".
- **No duplicates.** A listing that shows up under several inputs or on two pages is written and charged once — Avito does repeat promoted listings across pages, and those repeats are free.
- **A budget per input, if you want one.** `maxListings` is the run's total; `maxListingsPerInput` shares it out so input one does not spend what input two needed.
- **A hard request ceiling.** `maxUpstreamRequests` caps the whole run; leave it empty and the Actor derives one from your input.

### Input example

```json
{
  "searchQueries": ["iphone 13"],
  "searchUrls": [
    "https://www.avito.ru/sankt-peterburg/avtomobili",
    "https://www.avito.ru/moskva/kvartiry/prodam-ASgBAgICAUSSA8YQ"
  ],
  "city": "moskva",
  "maxListings": 200,
  "maxListingsPerInput": 50
}
```

| Field | Default | Meaning |
| --- | --- | --- |
| `searchQueries` | — | One keyword per line, in Russian. Searched in `city`, or across Russia when it is empty. |
| `searchUrls` | — | Avito result-list URLs copied from the browser. Use this, `searchQueries`, or both. |
| `city` | all of Russia | Avito region slug (`moskva`, `sankt-peterburg`, `ekaterinburg`). It also replaces the region of every URL above, so one URL can be run across several cities. |
| `maxListings` | `100` | Listing rows for the whole run. One Avito page carries up to 50, so this also decides how deep the Actor pages. |
| `maxListingsPerInput` | whole budget | Share of the budget one keyword or URL may spend. Set it when you give several inputs and want each of them collected. |
| `maxUpstreamRequests` | derived | Hard ceiling on requests to Avito, counting pages, retries and firewall exchanges (derived as four per page the run may need, at least 8). |
| `proxyConfiguration` | Apify Proxy | Datacenter is the default and what the Actor is measured on. |

### Output example

A listing row (`recordType: "listing"`):

```json
{
  "recordType": "listing",
  "listingId": "7926941211",
  "title": "Changan UNI-V 1.5 AMT, 2026",
  "price": 3445101,
  "currency": "RUB",
  "priceText": "от 2 530 000 ₽",
  "location": "Санкт-Петербург, Автово",
  "street": null,
  "metro": null,
  "category": "avtomobili",
  "categoryTitle": "Купить автомобиль в Санкт-Петербурге",
  "params": "1.5 AMT (181 л.с.), лифтбек, передний, бензин",
  "publishedAt": null,
  "publishedAtPrecision": null,
  "publishedAtText": null,
  "imageCount": 5,
  "imageUrls": ["https://b40.img.avito.st/image/1/..."],
  "url": "https://www.avito.ru/sankt-peterburg/avtomobili/changan_uni-v_1.5_amt_2026_7926941211",
  "sellerType": "company",
  "shopUrl": "https://www.avito.ru/brands/avtostyl_changan",
  "sellerRating": 4.8,
  "sellerReviewsText": "28 отзывов",
  "badges": ["В наличии", "Новый", "Официальный дилер"],
  "query": null,
  "sourceUrl": "https://www.avito.ru/sankt-peterburg/avtomobili",
  "page": 1,
  "rank": 2,
  "partial": false,
  "partialReason": null,
  "collectedAt": "2026-10-24T06:12:44.001Z"
}
```

One free `input_status` row per keyword or URL, with `listingsReturned`, `duplicatesSkipped`, `pagesFetched`, Avito's own result count (`totalText`), `partial`, `partialReason` and a plain-English `statusText`. The last row of the dataset — and the `RUN_SUMMARY` key in the run's store — totals the run: listings collected and charged, duplicates, pages read, inputs that were empty, inputs that are incomplete and why, requests sent to Avito and firewall challenges solved.

### Limits worth knowing

- **One Avito result page carries up to 50 listings, and the site stops offering pages at a depth of its own choosing** (commonly 30 pages ≈ 1 500 listings per URL). Narrow the filter — or run several cities — to go deeper than that, rather than asking for more pages than Avito offers.
- **Avito's firewall asks new IPs for a proof of work.** The Actor solves that public challenge in-process, with no browser and no login; a refused IP (HTTP 429/403) is retried from another proxy session. An input Avito refused from every session is written with `partialReason: "blocked"` — try `proxyConfiguration` with residential if that happens often.
- **Avito does not server-render every page it serves.** For the few it answers with the bare page shell, the Actor writes `partialReason: "page_not_rendered"` instead of pretending the result list was empty. A keyword page needs `cd=1` to render, which the Actor adds for you.
- **Dates are as coarse as the card.** Avito writes "7 часов назад" or "Вчера" on a result list, so `publishedAt` is derived from that wording; use `publishedAtPrecision` before treating it as a timestamp.
- **Public card data only.** This Actor reads what a logged-out visitor sees on the result list. It does not open a listing page, call a login-only API, or collect a private seller's name or phone number.

# Actor input Schema

## `searchQueries` (type: `array`):

One Avito search keyword per line, in Russian (iphone 13, диван, коляска детская). Each keyword is searched separately, in the region set below, and its listings are labelled with it. A listing that matches several keywords is returned once and charged once. Leave empty if you give listing page URLs instead.

## `searchUrls` (type: `array`):

Avito result-list URLs, one per line - open the category, the filter or the search you want on avito.ru and copy the address bar: https://www.avito.ru/moskva/noutbuki, https://www.avito.ru/sankt-peterburg/avtomobili, https://www.avito.ru/moskva/kvartiry/prodam-ASgBAgICAUSSA8YQ. Every filter in the URL is kept. A URL copied from page 3 starts collecting at page 3.

## `city` (type: `string`):

Avito region slug, as it appears in the site's own URL: moskva, sankt-peterburg, ekaterinburg, novosibirsk. It is the region your keywords are searched in, and it also replaces the region of any listing page URL above, so one URL can be run across several cities. Leave empty to search all of Russia.

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

Upper bound on the listing rows this run writes in total. One Avito result page carries up to 50 listings, so this also decides how many pages per input the run may walk. The input that hits the bound is marked partial with reason "listing_limit_reached".

## `maxListingsPerInput` (type: `integer`):

Optional share of the run budget for one keyword or URL. Leave it empty and the first input may spend the whole of maxListings, which is what a run with a single input wants; set it when you give several inputs and want each of them collected. An input that reaches its share is marked partial with reason "listing_limit_reached" and the next input still gets its own.

## `maxUpstreamRequests` (type: `integer`):

Hard ceiling on the HTTP requests this run sends to Avito, counting every result page, every retry and every firewall exchange. Left empty, the Actor works a ceiling out from your inputs and maxListings. At the ceiling collection stops - the inputs not reached are written with partialReason "upstream_request_cap" and the run then ends normally.

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

The proxy the requests to Avito go through. The default (Apify Proxy, datacenter) is the cheapest and is what this Actor is measured on: Avito answers it with a public proof-of-work challenge, which the Actor solves in-process without a login or a browser. Switch to residential only if your runs start reporting partialReason "blocked".

## Actor input object example

```json
{
  "searchQueries": [
    "iphone 13"
  ],
  "searchUrls": [
    "https://www.avito.ru/moskva/noutbuki"
  ],
  "maxListings": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `runSummary` (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 = {
    "searchQueries": [
        "iphone 13"
    ],
    "searchUrls": [
        "https://www.avito.ru/moskva/noutbuki"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lanternlab318/avito").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 = {
    "searchQueries": ["iphone 13"],
    "searchUrls": ["https://www.avito.ru/moskva/noutbuki"],
}

# Run the Actor and wait for it to finish
run = client.actor("lanternlab318/avito").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 '{
  "searchQueries": [
    "iphone 13"
  ],
  "searchUrls": [
    "https://www.avito.ru/moskva/noutbuki"
  ]
}' |
apify call lanternlab318/avito --silent --output-dataset

```

## MCP server setup

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

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/0qtm2zvBYWupkbuYV/builds/JeTCdTICON0vBVyLC/openapi.json