/drom/cars

POST /api/drom/cars

Price: 5 credits

Get full Drom.ru car listing details by listing URL: title, brand, model, year, price, city, engine, power, transmission, drive, body type, color, mileage, owners, steering wheel side, generation and complectation, VIN, condition, description and photos.

How to use it

Fetch a single Drom.ru car listing by its full listing URL (e.g. 'https://auto.drom.ru/{city}/{brand}/{model}/{id}.html'). Returns title, brand, model, year, price, currency, city, engine, power (hp), transmission, drive, body_type, color, mileage (km), owners, wheel (left/right), special_marks, generation, complectation, vin (masked by source), condition (used/new), pts_mismatch, description and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• car string required — Car listing as a full Drom.ru listing URL (examples: "https://auto.drom.ru/vladivostok/toyota/camry/125790180.html"; minLength: 1)

Response

• @type string (default: "DromCar")
• id string required
• url string required
• brand string nullable
• model string nullable
• year integer nullable
• price integer nullable
• currency string nullable
• city string nullable
• engine string nullable
• power integer nullable
• transmission string nullable
• drive string nullable
• body_type string nullable
• color string nullable
• mileage integer nullable
• owners string nullable
• wheel string nullable
• special_marks string nullable
• generation string nullable
• complectation string nullable
• generation_url string nullable
• complectation_url string nullable
• vin string nullable
• condition string nullable
• pts_mismatch boolean nullable
• description string nullable
• 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 — Listing not found (well-formed URL but the listing page does not exist or was removed) 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.