POST /api/cars/listings
Price: 1 credit
Get a single Cars.com vehicle listing by VIN: make, model, year, trim, body style, price, MSRP, mileage, drivetrain, transmission, exterior and interior color, engine, fuel type and MPG, EV range and charge time, CPO status, photos, dealer name and rating, deal rating and the seller's notes.
Fetch one Cars.com vehicle listing by its VIN (17-character Vehicle Identification Number, e.g. 1HGCV2F30LA028120). Returns one item with the full vehicle specification, photos, dealer info and seller notes. Use cars/listings/search to discover VINs.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)vin string required — Vehicle Identification Number (VIN) of the listing (examples: "1HGCV2F30LA028120"; minLength: 1)@type string (default: "CarsListingDetail")id string requiredurl string nullablevin string nullablemake string nullablemodel string nullableyear integer nullabletrim string nullablebody_style string nullablestock_type string nullableis_cpo boolean (default: false)is_verified boolean (default: false)price number nullablemsrp number nullablemileage number nullabledrivetrain string nullableexterior_color string nullablefuel_type string nullableseller_id string nullableseller_zip string nullablefinancing_type string nullableimage string nullableimages array (default: [])image_count integer nullablerank_enthusiast number nullablerank_family_friendly number nullablerank_luxury number nullablerank_off_road number nullablerank_sporty number nullableinterior_color string nullableengine string nullablempg string nullableev_range string nullablecharge_time string nullabletransmission string nullabledescription string nullabledeal_rating string nullabledealer_name string nullabledealer_rating number nullable422 — 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 (no active Cars.com listing matches the given VIN) 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.