/carsensor/listings

POST /api/carsensor/listings

Price: 10 credits

Get full CarSensor used-car listing details by listing id: title, maker, model, body and total price, year, mileage, repair history, inspection, body type, drive, color, steering, transmission, fuel, seats, doors, displacement, warranty, CarSensor quality rating, equipment, monthly loan, dealer, location and photos.

How to use it

Fetch a single CarSensor used-car listing by its id (e.g. 'AU7085680096') or full listing URL. Returns title, maker, model (with catalog slugs), body_price and total_price (JPY), year, year_era (Japanese era), mileage (km), repair_history, inspection, maintenance, body_type, drive, color, steering, transmission, fuel, seats, doors, displacement (cc), recycle_fee, warranty, quality_rating (CarSensor certified stars 1-5), has_quality_report, is_one_owner, is_non_smoking, is_unused, has_maintenance_record, monthly_loan (JPY/month), equipment (list of fitted features), prefecture, city, dealer_id, dealer_name and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — Listing id (e.g. 'AU7085680096') or full listing URL (examples: "AU7085680096"; minLength: 1)

Response

• @type string (default: "CarsensorListing")
• id string required
• url string required
• maker string nullable
• model string nullable
• maker_slug string nullable
• model_slug string nullable
• model_code string nullable
• body_price number nullable
• total_price number nullable
• currency string (default: "JPY")
• year integer nullable
• year_era string nullable
• mileage integer nullable
• repair_history string nullable
• inspection string nullable
• maintenance string nullable
• body_type string nullable
• drive string nullable
• color string nullable
• steering string nullable
• transmission string nullable
• fuel string nullable
• seats integer nullable
• doors integer nullable
• displacement integer nullable
• recycle_fee string nullable
• warranty string nullable
• quality_rating integer nullable
• has_quality_report boolean nullable
• is_imported boolean nullable
• is_one_owner boolean nullable
• is_non_smoking boolean nullable
• is_unused boolean nullable
• has_maintenance_record boolean nullable
• monthly_loan integer nullable
• equipment array (default: [])
• prefecture string nullable
• city string nullable
• dealer_id string nullable
• dealer_pref string nullable
• dealer_name 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 (valid id 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.