/autoru/catalog

POST /api/autoru/catalog

Price: 20 credits

Get the Auto.ru model catalog for a mark/model: all generations (with year ranges, restyle flag, market segment), their body configurations (body type, doors, seats, trunk volume, fuel-tank volume) and per-configuration technical modifications (engine type, displacement, power, transmission, drive, acceleration, top speed, fuel consumption, engine model, cylinders, torque), plus the owner review count and rating.

How to use it

Get Auto.ru model tech-spec catalog. Provide mark (brand slug, e.g. 'bmw') and model (e.g. 'x5'). Returns generations[] each with year_from/year_to, segment and configurations[] (body_type, door_count, seats, trunk volume) whose tech_params[] carry engine_type, displacement, power_hp, transmission, drive, acceleration, max_speed, consumption_mixed, engine_model. Also review_count and review_rating.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• mark string required — Mark/brand slug (e.g. 'bmw', 'toyota') (examples: "bmw"; minLength: 1)
• model string required — Model slug (e.g. 'x5', 'camry') (examples: "x5"; minLength: 1)

Response

• @type string (default: "AutoruCatalogModel")
• mark string required
• model string required
• mark_name string nullable
• model_name string nullable
• review_count integer nullable
• review_rating number nullable
• generations array (default: [])
  • @type string (default: "AutoruCatalogGeneration")
  • id string required
  • name string nullable
  • year_from integer nullable
  • year_to integer nullable
  • is_restyle boolean nullable
  • segment string nullable
  • group string nullable
  • image string nullable
  • configurations array (default: [])
    • @type string (default: "AutoruCatalogConfiguration")
    • id string required
    • body_type string nullable
    • human_name string nullable
    • door_count integer nullable
    • seats array (default: [])
    • auto_class string nullable
    • trunk_volume_min integer nullable
    • trunk_volume_max integer nullable
    • tank_volume integer nullable
    • image string nullable
    • tech_params 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 — Model not found 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.