Auto.ru Scraper - Car Listings, Prices, Checks & Dealers
Pricing
from $1.80 / 1,000 listing results
Scrape Auto.ru car listings: search by make, model, year, price, mileage, body, engine, gearbox, drive, seller and region, or paste result, dealer and listing links. Get price history, vehicle checks, owners, valuation, dealer details and photos, plus price-change tracking.
Choose 'search' to find listings with the filters below, 'url' to scrape pasted links, or 'listing' to read listings by their key.
Write the make, and optionally the model, the way they appear in auto.ru web addresses: bmw, bmw x5, vaz vesta, land_rover discovery. A generation number from the address may follow the model. One search per entry. Leave empty for every make. Read only in search mode.
[ "bmw x5"]Cities or regions to search, one search each, for example Moscow, Saint Petersburg, Kazan or Sverdlovsk oblast. Latin names work for the biggest places; any other place can be written in Russian, for example Тверь. Leave empty for all of Russia (the site would otherwise pick the region of the connecting address).
How far around each city in Regions to look, from 0 (the city itself) to 1000. Leave empty for the site's own default (200 km for most cities). Ignored for regions that are whole oblasts or republics.
Return the stock of these dealers (the numeric dealer id is a field of every dealer row, and a dealer page link works in URL mode). A dealer search ignores the region, radius and make settings.
Smallest engine displacement in cubic centimetres, for example 2000. The site compares it rounded to a tenth of a litre, so 1995 counts as 2000.
Largest engine displacement in cubic centimetres. The site compares it rounded to a tenth of a litre.
Only these fuel types. 'Gas equipment' returns cars fitted with a gas system (LPG). Leave empty for all.
Left-hand or right-hand drive.
Only cars with at most this many owners in the vehicle title (1, 2 or 3). Leave empty for any number.
Off by default, like the site: cars the seller marks as damaged or not running are left out. Turn on to include them.
Off by default, like the site. Turn on to include cars whose customs clearance is missing.
Order of the results. A sort order written into a pasted result link wins over this setting.
auto.ru links to scrape directly. A result link carries its own make, model, region and filters, and they win over the settings above. A dealer link returns that dealer's stock. A listing link reads that listing. Read only in url mode.
[ "https://auto.ru/moskva/cars/bmw/x5/used/?year_from=2018&sort=price-asc", "https://auto.ru/diler/cars/all/avilon_tenet_moskva/", "https://auto.ru/cars/used/sale/honda/vezel/1160165890-6216410f/"]Listing keys as they appear at the end of a listing link (the number, a dash and eight characters, for example 1160165890-6216410f), or whole listing links. Read only in listing mode.
[ "1160165890-6216410f"]Search and url scopes: also read every listing's own page for the seller's description, the view and favourite counters and the site's condition grade. This is one extra request per listing and carries a per-listing surcharge. Listing mode always reads the page.
Maximum number of listings to return across the whole run, EXPIRED rows from Incremental mode included. This is the run's cap. Use 0 for the maximum of 100000 listings per run. The site shows at most 99 result pages (3663 listings) per search, so use several makes, models or regions to go beyond that.
Maximum number of result pages to read per make, region or link. Each page carries up to 37 listings. 0 means as many as the search has, up to the site's limit of 99.
Connection used for every request. Leave the default (residential, any country). Apify free plans do not include proxies, so a free-plan run falls back to a backup connection and may return less.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ]}Paste a previous run ID or dataset ID to continue a large pull without returning or charging for listings already collected there. Use this after an interrupted run. For recurring monitoring of the same scope, use Incremental mode below instead.
Turn this on for daily or recurring monitoring. The first run returns every matching listing as NEW. Later runs normally return only NEW, UPDATED and REAPPEARED listings, which makes it a cheap way to watch price drops. What is compared: price, discount, availability, status, specification, ownership and vehicle-check fields, seller, description, equipment and price history. What is excluded by default (still returned in the row, never a change): scrape timestamps, the listing's rank and page, where it was found, view and favourite counters, days on sale and the last-edited time, exchange-rate conversions (price in dollars and euros), the site's own market-price estimates, dealer rating and condition grade, the rotating labels and badges, and photo links. Equipment and phone lists are compared regardless of order. 'Changes to watch' narrows this to price and availability only. Turn on 'Emit unchanged' or 'Emit expired' only when you also want those rows returned (and billed). State is kept separately for each scope and filter setup; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.
Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently configured runs. Leave empty to derive a key automatically from the scope and filter settings, so two different scopes never mix state.
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 want a full snapshot every run.
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 the tracked scope without a page that could not be read, never when Max listings or the site's 99-page limit capped it, and never when Resume was used. A sold or removed listing counts as missing; consider 'Expire after missed scans' above 1 so a brief gap does not expire a listing. EXPIRED rows count against Max listings: a run returns at most the room left under it, and the rest are returned on a later complete run. This returns, and bills, extra rows, so leave it off unless you need expiry tracking.
All fields (default): any change to the compared listing data marks a listing UPDATED. Price and availability only: just the asking price, the dealer discount, the availability, the status and the price history, so description, equipment or ownership edits never produce a billable UPDATED row. Changing this never starts a new baseline: the existing saved state is kept (under an automatic or a named State key) and each stored listing is simply compared under the new setting.
Off by default. When on, UPDATED and EXPIRED rows are slim: ids, link, title, current price and availability, plus priceChanges (old and new value of each field that moved) and variantChanges (price-history entries ADDED, REMOVED or CHANGED). NEW rows stay full. A compact row does not carry listing-page detail fields, so no detail charge applies to it.
Used with 'Emit expired'. A listing is marked EXPIRED only after it was missing from this many CONSECUTIVE complete scans (default 1). Listings come and go as sellers publish and sell, so a value of 2 or more avoids false expiries.
Field names that must not count as a change, for example description or equipment. Use a dotted path to ignore a key inside every element of a list, for example priceHistory.price. Ignored fields are still returned in the row. Rank, where the listing was found, counters, exchange-rate conversions, the site's estimates and photo links are already ignored by default. Changing this list never starts a new baseline: the saved state is kept and each stored listing is re-compared under the new list, so no listing comes back as NEW.
Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API & Integrations, then select it here. Notion gets a page per listing; other connectors get a best-effort write or digest. Each connector receives a condensed summary per listing, not the full record; the complete record always stays in the dataset. Leave empty to skip; this never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
URL or id of the Notion page under which listing pages are created. Required to enable the Notion export; ignored by other connectors.