/cardekho/models/prices

POST /api/cardekho/models/prices

Price: 20 credits

Get the on-road price of every variant of a CarDekho car model in one city: ex-showroom price, RTO, insurance, other charges and optional accessories itemised, EMI, the model's price range in nearby and major cities, and the brand's dealers in that city

How to use it

City aliases follow CarDekho price pages (mumbai, new-delhi, bangalore); other_city_prices returns more aliases through each url. An unknown city answers 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• model string required — CarDekho model as brand/model alias or model page URL (examples: "hyundai/creta", "https://www.cardekho.com/tata/nexon")
• city string required — City alias as used in CarDekho price pages (examples: "mumbai", "new-delhi"; minLength: 1)

Response

• @type string (default: "CardekhoModelPrice")
• model_id string required
• model_alias string required
• model_name string nullable
• brand string nullable
• city string required
• city_alias string required
• url string required
• currency string (default: "INR")
• on_road_price_min number nullable
• on_road_price_max number nullable
• ex_showroom_price_min number nullable
• ex_showroom_price_max number nullable
• variants array (default: [])
  • @type string (default: "CardekhoVariantPrice")
  • alias string nullable
  • name string required
  • full_name string nullable
  • url string nullable
  • fuel_type string nullable
  • transmission string nullable
  • tag string nullable
  • currency string (default: "INR")
  • ex_showroom_price number nullable
  • rto_charges number nullable
  • insurance number nullable
  • other_charges number nullable
  • other_charge_items array (default: [])
    • @type string (default: "CardekhoCharge")
    • name string required
    • amount number nullable
  • optional_accessories number nullable
  • optional_accessory_items array (default: [])
    • @type string (default: "CardekhoCharge")
    • name string required
    • amount number nullable
  • on_road_price number nullable
  • on_road_price_without_optional number nullable
  • emi number nullable
  • is_top_selling boolean nullable
• other_city_prices array (default: [])
  • @type string (default: "CardekhoCityPrice")
  • city string required
  • on_road_price_min number nullable
  • on_road_price_max number nullable
  • price_text string nullable
  • url string nullable
  • on_road_price number nullable
• dealers array (default: [])
  • @type string (default: "CardekhoDealer")
  • id string required
  • name string required
  • brand string nullable
  • url string nullable
  • address string nullable
  • locality string nullable
  • city string nullable
  • pincode string nullable
  • latitude number nullable
  • longitude number nullable
  • phone string nullable
  • email string nullable
  • open_time string nullable
  • close_time string nullable
  • is_sponsored boolean 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 — CarDekho has no price page for that model and city 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.