/cardekho/used_cars

POST /api/cardekho/used_cars

Price: 20 credits

Get a CarDekho used-car listing by id or URL: price with new-car price and fair-price band, year, km, fuel, transmission, colour, ownership, RTO, seller and location, EMI, full specifications and features, images, trust tags and similar listing ids

How to use it

Find listing ids with cardekho/used_cars/search; similar_ids are listing ids this endpoint accepts. is_active is false for a listing that has been sold or withdrawn.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — CarDekho used-car listing id or listing URL (examples: "ead7f2cb-0991-4533-bd71-68d257a9ba56", "https://www.cardekho.com/used-car-details/used-renault-kiger-rxz-turbo-cvt-cars-mumbai_ead7f2cb-0991-4533-bd71-68d257a9ba56.htm")

Response

• @type string (default: "CardekhoUsedListing")
• id string required
• listing_id string nullable
• url string nullable
• make string nullable
• model string nullable
• model_id string nullable
• model_name string nullable
• variant string nullable
• variant_id string nullable
• year integer nullable
• price number nullable
• price_text string nullable
• currency string (default: "INR")
• new_car_price number nullable
• fair_price_min number nullable
• fair_price_max number nullable
• price_badge string nullable
• km_driven integer nullable
• fuel_type string nullable
• transmission string nullable
• body_type string nullable
• color string nullable
• seats integer nullable
• engine_cc integer nullable
• owner_count integer nullable
• rto_code string nullable
• city string nullable
• locality string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• seller_type string nullable
• inventory_type string nullable
• dealer_id string nullable
• store_id string nullable
• is_active boolean nullable
• is_booked boolean nullable
• emi_monthly number nullable
• emi_interest_rate number nullable
• emi_months integer nullable
• summary string nullable
• image string nullable
• images array (default: [])
• overview array (default: [])
  • @type string (default: "CardekhoFact")
  • name string required
  • value string nullable
• specs array (default: [])
  • @type string (default: "CardekhoSpec")
  • group string nullable
  • name string required
  • value string nullable
• features array (default: [])
  • @type string (default: "CardekhoFeature")
  • group string nullable
  • name string required
• trust_tags array (default: [])
• reasons_to_buy array (default: [])
• model_rating number nullable
• model_review_count integer nullable
• similar_ids 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 — CarDekho has no used-car listing under that id 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.