/carsensor/models

POST /api/carsensor/models

Price: 5 credits

Get CarSensor new-car catalog details for a model by maker/model slug: name, spec ranges (power, displacement, drive, seats, fuel economy), body dimensions, new-car price range, generations and review rating.

How to use it

Fetch the CarSensor catalog entry for a car model by maker and model slugs (e.g. maker='toyota', model='prius'). Returns maker_name, model_name, max_power, displacement, drive, seats, length/width/height/wheelbase, fuel economy (WLTC/JC08/10.15), eco_standard, fuel_standard, new_price_min/max (JPY), review_rating, review_count, generations (code/period/url) and image.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• maker string required — CarSensor catalog maker slug (examples: "toyota"; minLength: 1)
• model string required — CarSensor catalog model slug (examples: "prius"; minLength: 1)

Response

• @type string (default: "CarsensorModel")
• maker string required
• model string required
• maker_name string nullable
• model_name string nullable
• url string required
• max_power string nullable
• displacement string nullable
• drive string nullable
• seats string nullable
• length string nullable
• width string nullable
• height string nullable
• wheelbase string nullable
• fuel_economy_wltc string nullable
• fuel_economy_jc08 string nullable
• fuel_economy_1015 string nullable
• eco_standard string nullable
• fuel_standard string nullable
• new_price_min number nullable
• new_price_max number nullable
• review_rating number nullable
• review_count integer nullable
• generations array (default: [])
  • @type string (default: "CarsensorModelGeneration")
  • code string required
  • period string nullable
  • url string nullable
• image string nullable

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 (valid slug format but the catalog page does not exist) 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.