/cars24/listings/search

POST /api/cars24/listings/search

Price: 10 credits

Search Cars24 used-car listings in a city or across India by make, models, price, year, kilometres, fuel, body type, transmission, colour, seats, owners and seller kind: price with discount and EMI, year, km, registration RTO, insurance expiry, hub location, category and badges

How to use it

Pass a returned id to cars24/listings for the inspection report, specifications and features. Make and model names come from cars24/models for the same city.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city string nullable — City alias as used in Cars24 URLs; all India when omitted (examples: "mumbai", "delhi-ncr", "bangalore"; minLength: 1)
• make string nullable — Make name (examples: "hyundai", "maruti", "tata"; minLength: 1)
• models array nullable — Model names within the make (examples: ["creta"], ["wagon r 1.0","swift"])
• price_min integer nullable — Minimum price in rupees (min: 0)
• price_max integer nullable — Maximum price in rupees (min: 1)
• year_min integer nullable — Earliest model year (min: 1990; max: 2100)
• year_max integer nullable — Latest model year (min: 1990; max: 2100)
• km_min integer nullable — Minimum kilometres driven (min: 0)
• km_max integer nullable — Maximum kilometres driven (min: 1)
• fuel array nullable — Fuel types (one of: "petrol", "diesel", "cng", "hybrid", "electric")
• body_type array nullable — Body types (one of: "suv", "sedan", "hatchback")
• transmission string nullable — Transmission (one of: "manual", "automatic")
• color array nullable — Exterior colours (one of: "white", "red", "black", "silver", "blue", "green", "yellow", "brown", "orange", "purple")
• seats array nullable — Seating capacities
• owners array nullable — Owner counts
• seller string nullable — Cars24-owned stock or verified individual sellers (one of: "gs", "c2c")
• sort string — Result order (default: "relevance"; one of: "relevance", "newest", "price_asc", "price_desc", "km_asc", "km_desc", "year_desc", "year_asc")
• count integer required — Max number of results (min: 1; max: 5000)

Response

• @type string (default: "Cars24Listing")
• id string required
• url string nullable
• make string nullable
• model string nullable
• variant string nullable
• year integer nullable
• currency string (default: "INR")
• price number nullable
• original_price number nullable
• discount number nullable
• new_car_ex_showroom_price number nullable
• emi_monthly number nullable
• emi_interest_rate number nullable
• emi_months integer nullable
• km_driven integer nullable
• fuel_type string nullable
• transmission string nullable
• body_type string nullable
• color string nullable
• seats integer nullable
• owner_count integer nullable
• registration_number string nullable
• registration_rto string nullable
• registered_at integer nullable
• insurance_expires_at integer nullable
• status string nullable
• sub_status string nullable
• listed_at integer nullable
• city_id string nullable
• locality string nullable
• hub_city string nullable
• latitude number nullable
• longitude number nullable
• business_vertical string nullable
• seller_type string nullable
• category string nullable
• segment string nullable
• assurance string nullable
• business_tag string nullable
• usp string nullable
• image string nullable
• image_count integer nullable
• badges array (default: [])
• features 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 — Cars24 has no listing page for that city 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.

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.