/drom/cars/search

POST /api/drom/cars/search

Price: 10 credits

Search Drom.ru car listings by brand, model and filters: fuel, body type, condition, transmission, drive, steering wheel side, damage, price/year/mileage/power ranges, color and sort order. Returns listing cards with id, url, title, subtitle, price, location, date, dealer info and images.

How to use it

Search Drom.ru car listings. All filters optional except count. brand/model are slugs ('toyota'/'camry'); omit both to search all brands. Filters: fuel (petrol/diesel/hybrid/gas/electro), body_type (sedan/hatchback/liftback/coupe/suv/wagon/van/pickup), condition (all/used/new), transmission (manual/automatic/variator), drive (front/rear/full), wheel (left/right), damage (any/damaged/not_damaged), price_min/price_max (RUB), year_min/year_max, mileage_min/mileage_max (km), power_min/power_max (hp), color_id, available_only; sort by relevance/price_asc/price_desc/year_asc/year_desc. Each result has id, url, title, subtitle (complectation), price, location, date, is_dealer, dealer_name, attributes and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• brand string nullable — Brand slug, e.g. 'toyota', 'lada', 'bmw' (examples: "toyota")
• model string nullable — Model slug, e.g. 'camry' (requires brand) (examples: "camry")
• fuel string nullable — Fuel type (one of: "petrol", "diesel", "hybrid", "gas", "electro")
• body_type string nullable — Body type (one of: "sedan", "hatchback", "liftback", "coupe", "suv", "wagon", "van", "pickup")
• condition string — Listing condition (default: "all"; one of: "all", "used", "new")
• transmission string nullable — Transmission type (one of: "manual", "automatic", "variator")
• drive string nullable — Drive type (one of: "front", "rear", "full")
• wheel string nullable — Steering wheel side (one of: "left", "right")
• damage string — Damage filter (default: "any"; one of: "any", "damaged", "not_damaged")
• price_min integer nullable — Minimum price (RUB) (min: 0)
• price_max integer nullable — Maximum price (RUB) (min: 0)
• year_min integer nullable — Minimum production year (min: 1900)
• year_max integer nullable — Maximum production year (min: 1900)
• mileage_min integer nullable — Minimum mileage (km) (min: 0)
• mileage_max integer nullable — Maximum mileage (km) (min: 0)
• power_min integer nullable — Minimum engine power (hp) (min: 0)
• power_max integer nullable — Maximum engine power (hp) (min: 0)
• color_id integer nullable — Color id (source-specific numeric code) (min: 1)
• available_only boolean — Exclude already sold listings (default: false)
• sort string — Sort order (default: "relevance"; one of: "relevance", "price_asc", "price_desc", "year_asc", "year_desc")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "DromCarCard")
• id string required
• url string required
• subtitle string nullable
• price integer nullable
• location string nullable
• date string nullable
• is_dealer boolean nullable
• dealer_name string nullable
• is_sold boolean nullable
• attributes array (default: [])
• image string nullable
• images array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.