Avito RU $1💰 URL | Keyword Filters | Enriched Output avatar

Avito RU $1💰 URL | Keyword Filters | Enriched Output

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Avito RU $1💰 URL | Keyword Filters | Enriched Output

Avito RU $1💰 URL | Keyword Filters | Enriched Output

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.

Pricing

from $1.00 / 1,000 results

Rating

5.0

(1)

Developer

Abot API

Abot API

Maintained by Community

Actor stats

0

Bookmarked

208

Total users

44

Monthly active users

5 days ago

Last modified

Share

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.

FieldExample
id0000000000
urlhttps://www.avito.ru/moskva/kvartiry/listing-title-slug_0000000000
titleSample listing title in Russian
price12345678
currencyRUB
priceText12 345 678 ₽
categorykvartiry
subcategoryprodam
regionmoskva
citymoskva
addressЖК «Образцовый», ул. Примерная, 4
streetул. Примерная
metroОбразцовая
metroId0
metroDistanceMin10
postedDate1 января
descriptionFull listing description text (returned in every run, no detail fetch needed).
photoUrls["https://90.img.avito.st/image/1/1.example", "..."]
photoCount5
badges["Sample badge text"]
isVerifiedtrue
sellerNameAgent Name
sellerTypeagency
sellerRating0.0
sellerReviewsCount0
sellerSinceНа Авито с YYYY года
viewsCount0
attributes{"Sample attribute key": "Sample value"}

How to use

{
"mode": "search",
"regions": ["moskva"],
"category": "kvartiry",
"dealType": "prodam",
"minPrice": 1000000,
"maxPrice": 9000000,
"sortBy": "price_asc",
"maxPages": 5,
"maxListings": 250,
"proxy": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"]
}
}
{
"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

{
"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)

{
"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

ParameterTypeDefaultDescription
modestringsearchEither search (use filters) or url (use direct URLs)
regionsstring[]["moskva"]Region slugs. Use rossiya for all of Russia
categorystringkvartiryTop-level category slug (apartments, cars, jobs, services, etc.)
dealTypestringprodamprodam (sale), snyat (rent), kupit (wanted), sdam (lease). Property categories only
querystringemptyFree-text query, matches title and description
minPriceintemptyMinimum price in rubles
maxPriceintemptyMaximum price in rubles
sortBystringdefaultdefault, date_desc, price_asc, price_desc
ownerOnlyboolfalseRestrict to private (non-pro) sellers
urlsstring[]emptyDirect avito URLs. URL mode only
maxPagesintempty (unlimited)Optional bound on pages walked per region/URL (about 50 listings/page). Leave empty to walk every result page; defers to maxListings
maxListingsint20Total cap across all searches. 0 = unlimited
fetchDetailsboolfalseVisit each listing for full description, all photos, seller stats
proxyobjectApify ResidentialProxy configuration
resumeFromRunIdstringemptyPrevious 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
incrementalModeboolfalseRecurring monitoring of the same search/URL set: returns only NEW/UPDATED/REAPPEARED listings against a remembered baseline. See "Resume and recurring updates" below
stateKeystringemptyIncremental mode only. Name a monitoring campaign, or deliberately share state across differently-configured runs. Leave empty to derive one automatically
emitUnchangedboolfalseIncremental mode only. Also return UNCHANGED listings. Off by default — returns and bills rows you already have
emitExpiredboolfalseIncremental 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.

{
"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.