Drom.ru Scraper

Drom.ru Scraper at a glance

Drom.ru Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its documented output includes id, url, title, make and model, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.00 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Web data
Pricing: $2.00 per 1,000 results (Free plan), from $1.20 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 26 options

Scrape drom.ru vehicle listings: make/model/year/mileage, price, engine and transmission specs, public masked VIN, seller type and the full specifications table. Make+region search with filters or paste links. Resume, incremental updates and MCP export included.

What Drom.ru Scraper can do

Search, URLs or sold-lot statistics. Build searches from filters, provide Drom search and listing links, or read Japan-auction sale prices per make and model.
Listing context. Keep the source URL, region, collection mode and discovery position with each record.
Optional details. Read the listing page for its specification table, description, seller type and public masked VIN when present.
Recurring updates. Resume interrupted runs and classify changes across scheduled runs.
Bounded collection. Set one global item cap; page traversal is unlimited unless you enter an optional page limit.
App delivery. Keep the dataset as the primary output and optionally forward a capped set of records to configured MCP connectors.

Choose what to collect

These inputs let you configure Drom.ru Scraper - Cars, Prices, Specs & Sellers. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string	search builds drom searches from your filters (makes, region, price, year). urls scrapes exactly the drom search, listing or Japan-auction statistics links you paste. statistics returns sold Japan-auction lots with actual yen prices for the makes (and optional models) you list. Choices: search, urls, statistics
`makes`array	Make slugs from drom URLs (audi, bmw, toyota, kamaz...). In search mode an empty list searches all makes; statistics mode needs at least one make.
`minYear`integer	Earliest model year (search and statistics mode).
`maxYear`integer	Latest model year (search and statistics mode).
`region`string	Region slug from drom URLs (moscow, vladivostok, krasnoyarsk...). Leave empty for all Russia.
`minPrice`integer	Minimum listing price in rubles.
`maxPrice`integer	Maximum listing price in rubles.

Show 19 more inputs

More input fields
Input	What it controls
`transmission`integer	0 = any, 1 = manual, 2 = all automatic types (including CVT and robotized), 3 = CVT, 4 = robotized.
`drivetrain`integer	0 = any, 1 = FWD, 2 = RWD, 3 = 4WD.
`models`array	Optional model slugs from the drom statistics pages (a4, corolla, land_cruiser). Each model is read for every make; leave empty for all models of the make.
`minPriceYen`integer	Lowest auction sale price in Japanese yen. Statistics mode only; the RUB price filters apply to search mode.
`maxPriceYen`integer	Highest auction sale price in Japanese yen. Statistics mode only.
`statisticsSort`string	Order of sold lots. Statistics mode only. Choices: newest, price_asc, price_desc, year_asc, year_desc
`listingUrls`array	Drom search pages, regional search pages, forward pages (/audi/all/page2/), or individual listings (.../.html). Pasted filters and the starting page are preserved. Statistics pages (https://www.drom.ru/world/japan/audi/) and sold lot links are accepted too.
`maxItems`integer	Maximum number of listings returned per run. This is the only finite default run cap.
`maxPages`integer	Maximum pages walked per search. 0 means no page cap, so Max items is the only cap that stops a run early.
`fetchDetails`boolean	Read each discovered listing page (or sold-lot page in statistics mode) for full specifications, gallery and public details. Pasted individual listing URLs are always read as their primary source; this option controls extra detail reads from search results.
`resumeFromRunId`string	Run or dataset ID whose collected listings should be skipped (for continuing after an interrupted run).
`incrementalMode`boolean	Track state between runs and classify every listing as NEW, UPDATED, UNCHANGED or EXPIRED instead of always NEW. Rows already known and unchanged are suppressed.
`stateKey`string	Named baseline for incremental runs. Leave empty to derive the key from the run scope.
`emitUnchanged`boolean	In incremental mode, also push rows that did not change (changeType UNCHANGED).
`emitExpired`boolean	In incremental mode, emit EXPIRED tombstone rows for listings that disappeared from the walked scope.
`ignoreFieldsForChanges`array	Extra field names that must never mark a row UPDATED.
`mcpConnectors`array	Apify MCP connector IDs that receive pushed records while the run executes.
`notionParentPageUrl`string	Notion parent page for the Notion MCP connector.
`maxNotifyListings`integer	Cap on records sent to MCP connectors per run.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

idid

urlurl

titletitle

makemake

modelmodel

yearyear

priceprice

currencycurrency

engineengine

fuelfuel

gearboxgearbox

drivetraindrivetrain

Show 62 more fields

mileageKmmileageKm

powerHppowerHp

citycity

vinPartialvinPartial

specsspecs

descriptiondescription

imageUrlimageUrl

modelRatingValuemodelRatingValue

modelRatingCountmodelRatingCount

sellerTypesellerType

recordTyperecordType

regionregion

categorycategory

modemode

extractionPathextractionPath

discoveredFromUrldiscoveredFromUrl

resultsReturnedresultsReturned

detailFetcheddetailFetched

scrapedAtscrapedAt

changeTypechangeType

changedFieldschangedFields

firstSeenAtfirstSeenAt

lastSeenAtlastSeenAt

bullIdbullId

minimalPriceminimalPrice

frameTypeframeType

showPlaceholdershowPlaceholder

dealTypedealType

soldsold

hasDealerNamehasDealerName

dealerNamedealerName

subtitlesubtitle

attributesattributes

imagesimages

photosphotos

photoCountphotoCount

promotionStatuspromotionStatus

datedate

locationlocation

engineVolumeengineVolume

bodyTypebodyType

colorcolor

numberOfOwnersnumberOfOwners

wheelSidewheelSide

generationgeneration

complectationcomplectation

hasDamagehasDamage

hasDocshasDocs

dealerCardUrldealerCardUrl

dealerOfficialdealerOfficial

dealerBulletinCountdealerBulletinCount

dealerAgedealerAge

auctionLotIdauctionLotId

auctionNameauctionName

auctionDateauctionDate

auctionDateTextauctionDateText

lotNumberlotNumber

auctionGradeauctionGrade

frameMarkframeMark

equipmentequipment

engineDisplacementCcengineDisplacementCc

priceInRussiaRubpriceInRussiaRub

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "id": "712672086",
  "url": "https://auto.drom.ru/moscow/audi/a4/712672086.html",
  "title": "Audi A4, 2011",
  "make": "Audi",
  "model": "A4",
  "year": 2011,
  "price": 830000,
  "currency": "RUB",
  "mileageKm": 162653,
  "gearbox": "вариатор",
  "region": "moscow",
  "recordType": "listing",
  "changeType": "NEW"
}

Ways to use this data

Who: vehicle marketplaces and dealers who need a regional inventory snapshot.
Who: automotive analysts comparing asking prices, model years and mileage across regions.
Who: data teams monitoring selected makes for newly listed or changed vehicles.
Who: importers and valuation analysts who need real Japan-auction sale prices (not asking prices) by make, model, year and grade.
Who: vehicle researchers who need listing-page specifications and public seller signals alongside search-card prices.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does Drom.ru Scraper return?

The documented output for Drom.ru Scraper includes id, url, title, make, model, year, price and currency. Availability of each field depends on the source page and the selected mode.

How much does Drom.ru Scraper cost?

It costs $2.00 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

Can I schedule recurring checks?

Yes. Enable incremental mode and keep the same search scope and state key across scheduled runs. The first run establishes a baseline; later runs classify records against it.

Can an AI agent use the output?

Yes. Records are available through the Apify dataset API. Optional MCP connector export can send a capped set of records to supported apps.