/carsensor/models/prices

POST /api/carsensor/models/prices

Price: 10 credits

Get CarSensor market price information for a model by maker and model code: new and used price ranges, review rating with category breakdown, popularity ranking, listing count and dealer count.

How to use it

Fetch CarSensor market-price (相場) data for a model by maker (named) and model code (e.g. 'S122' for Prius). Returns model_name, period, new_price_min/max and used_price_min/max (JPY), review_rating and review_count, the rating breakdown (design/driving/comfort/drivability/loading/running_cost), ranking_category and ranking_position, listing_count and dealer_count. The model code is the same code used as the model filter on listings search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• maker string required — Car maker (one of: "lexus", "toyota", "nissan", "honda", "mazda", "subaru", "suzuki", "mitsubishi", "daihatsu", "isuzu", "mitsuoka", "tommykaira", "hino", "ud_trucks", "fuso", "domestic_other", "mercedes_benz", "mercedes_amg", "mercedes_maybach", "amg", "maybach", "smart", "bmw", "alpina", "audi", "volkswagen", "opel", "porsche", "brabus", "artega", "mini", "cadillac", "chevrolet", "buick", "pontiac", "saturn", "hummer", "gmc", "ford", "lincoln", "mercury", "saleen", "chrysler", "dodge", "plymouth", "amc", "amc_jeep", "jeep", "oldsmobile", "winnebago", "dmc", "tesla", "us_lexus", "us_infiniti", "us_acura", "us_toyota", "scion", "us_nissan", "us_honda", "us_mazda", "us_subaru", "us_mitsubishi", "rolls_royce", "bentley", "jaguar", "daimler", "land_rover", "aston_martin", "lotus", "london_taxi", "mclaren", "mg", "rover", "austin", "morris", "bl", "moke", "marcos", "vanden_plas", "wolseley", "riley", "caterham", "westfield", "morgan", "panther", "triumph", "healey", "ginetta", "vauxhall", "volvo", "saab", "scania", "peugeot", "renault", "citroen", "ds", "bugatti", "alpine", "fiat", "alfa_romeo", "ferrari", "lamborghini", "maserati", "lancia", "autobianchi", "abarth", "innocenti", "de_tomaso", "ktm", "hooten", "lada", "byd", "hyundai", "thai_toyota", "td", "birkin", "import_other")
• model string required — CarSensor model code (e.g. 'S122' for Prius) (examples: "S122"; minLength: 1)

Response

• @type string (default: "CarsensorModelPrices")
• maker string required
• model string required
• code string required
• url string required
• model_name string nullable
• period string nullable
• new_price_min number nullable
• new_price_max number nullable
• used_price_min number nullable
• used_price_max number nullable
• review_rating number nullable
• review_count integer nullable
• rating_design number nullable
• rating_driving number nullable
• rating_comfort number nullable
• rating_drivability number nullable
• rating_loading number nullable
• rating_running_cost number nullable
• ranking_category string nullable
• ranking_position integer nullable
• listing_count integer nullable
• dealer_count integer 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 code format but the market-price 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.