POST /api/cardekho/used_cars/search
Price: 5 credits
Search CarDekho used-car listings in a city or across India by brand, model, price, registration year, kilometres, fuel, transmission, body type, ownership, seller kind, seats, colour and certification: price, year, km, location, seller, EMI, price badge and highlights
Pass a returned id to cardekho/used_cars for the full listing. An unknown city, brand or model alias answers 412 rather than an unfiltered list.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)city string nullable — City alias as used in CarDekho used-car URLs; all India when omitted (examples: "mumbai", "new-delhi", "bangalore"; minLength: 1)brand string nullable — Brand alias (examples: "hyundai", "maruti", "tata"; minLength: 1)model string nullable — Model alias within the brand (examples: "creta", "swift"; minLength: 1)price_min_lakh integer nullable — Minimum price in lakh rupees (min: 0; max: 1000)price_max_lakh integer nullable — Maximum price in lakh rupees (min: 1; max: 1000)year_min integer nullable — Earliest registration year (min: 1990; max: 2100)year_max integer nullable — Latest registration year (min: 1990; max: 2100)km_max integer nullable — Maximum kilometres driven (min: 1000; max: 1000000)fuel string nullable — Fuel type (one of: "petrol", "diesel", "cng", "electric", "lpg")transmission string nullable — Transmission (one of: "automatic", "manual")body_type string nullable — Body type (one of: "suv", "sedan", "hatchback", "muv", "minivan", "coupe", "convertible", "pickup-truck", "wagon", "hybrid")owner string nullable — Ownership (one of: "first-owner", "second-owner", "third-owner-or-more", "unregistered")seller string nullable — Seller kind or partner network (one of: "partner", "enterprise", "direct-owner", "c24", "spinny")seats integer nullable — Seating capacity (min: 2; max: 9)color string nullable — Exterior colour (one of: "white", "grey", "blue", "silver", "red", "black", "brown", "maroon", "green", "orange", "yellow", "gold", "violet", "other")certified boolean — Only CarDekho-certified cars (default: false)sort string — Result order (default: "relevance"; one of: "relevance", "newest", "price_asc", "price_desc", "km_asc", "year_desc")count integer required — Max number of results (min: 1; max: 1000)@type string (default: "CardekhoUsedCar")id string requiredlisting_id string nullableurl string nullablemake string nullablemodel string nullablemodel_name string nullablevariant string nullablevariant_id string nullableyear integer nullableprice number nullableprice_text string nullablecurrency string (default: "INR")km_driven integer nullablefuel_type string nullabletransmission string nullablebody_type string nullableowner_count integer nullablecity string nullablecity_id string nullablelocality string nullablelatitude number nullablelongitude number nullableseller_type string nullableinventory_type string nullabledealer_id string nullablestore_id string nullableis_active boolean nullableis_certified boolean nullableimage string nullableimage_count integer nullableemi_monthly number nullableemi_interest_rate number nullableemi_months integer nullableprice_badge string nullabletrust_tags array (default: [])highlights array (default: [])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 did not recognise the city, brand or model alias 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.