/cars/dealers/listings

POST /api/cars/dealers/listings

Price: 5 credits

Get the vehicle inventory of a single Cars.com dealer/seller by id. The dealer id is the seller_id returned on Cars.com listings. Returns listing cards with vehicle summary, price, mileage and photos.

How to use it

List all vehicles for sale from one Cars.com dealer/seller. Pass the seller_id (UUID) taken from any Cars.com listing's seller_id field. Sort by best match, price, mileage, year or recency. count is required.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• dealer string required — Dealer/seller id (the seller_id returned on Cars.com listings) (examples: "526e7d6f-3e93-5493-bb4f-54d92ab64807"; minLength: 1)
• sort string — Sort order (default: "best_match"; one of: "best_match", "price_low", "price_high", "mileage_low", "mileage_high", "distance", "best_deal", "year_new", "year_old", "newest_listed", "oldest_listed")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "CarsListing")
• id string required
• url string nullable
• vin string nullable
• make string nullable
• model string nullable
• year integer nullable
• trim string nullable
• body_style string nullable
• stock_type string nullable
• is_cpo boolean (default: false)
• is_verified boolean (default: false)
• price number nullable
• msrp number nullable
• mileage number nullable
• drivetrain string nullable
• exterior_color string nullable
• fuel_type string nullable
• seller_id string nullable
• seller_zip string nullable
• financing_type string nullable
• image string nullable
• images array (default: [])
• image_count integer nullable
• rank_enthusiast number nullable
• rank_family_friendly number nullable
• rank_luxury number nullable
• rank_off_road number nullable
• rank_sporty number 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 — The entity was not found, or a precondition failed 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.