POST /api/cardekho/models
Price: 20 credits
Get a CarDekho new-car model by brand/model alias or URL: price range, every variant with ex-showroom and on-road price, key specs, mileage by fuel, colours, prices in major cities, user rating breakdown, expert verdict with pros and cons, images and rival models
Find aliases with cardekho/models/search or cardekho/brands. City-level on-road price breakdown is cardekho/models/prices and full owner reviews are cardekho/models/reviews, both taking the same alias.
access-token string requiredtimeout 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/maruti/swift")@type string (default: "CardekhoModel")id string requiredalias string requiredurl string requiredname string requiredshort_name string nullablebrand string nullablebrand_alias string nullablestatus string nullablebody_type string nullableimage string nullableimages array (default: [])price_min number nullableprice_max number nullableprice_text string nullableprice_city string nullablecurrency string (default: "INR")fuel_types string nullabletransmission string nullableengine string nullablemileage string nullableseats integer nullablerating number nullablereview_count integer nullablerating_distribution array (default: [])@type string (default: "CardekhoRatingBucket")label string requiredstars integer nullablecount integer nullableexpert_rating number nullableexpert_verdict string nullablepros array (default: [])cons array (default: [])variant_count integer nullablevariants array (default: [])@type string (default: "CardekhoVariant")id string nullablealias string nullablename string requiredfull_name string nullableurl string nullablestatus string nullablefuel_type string nullablesummary string nullablemileage number nullableex_showroom_price number nullableon_road_price number nullablecurrency string (default: "INR")waiting_period string nullableis_top_selling boolean nullableis_top_pick boolean nullablekey_features array (default: [])missing_features array (default: [])key_specs array (default: [])@type string (default: "CardekhoSpec")group string nullablename string requiredvalue string nullablecolors array (default: [])@type string (default: "CardekhoColor")id string nullablename string requiredhex_code string nullableparent_color string nullableimage string nullableurl string nullablemileage_by_fuel array (default: [])@type string (default: "CardekhoSpec")group string nullablename string requiredvalue string nullablecity_prices array (default: [])@type string (default: "CardekhoCityRange")city string requiredon_road_price_min number nullableon_road_price_max number nullableprice_text string nullableurl string nullableimage_count integer nullablerivals array (default: [])@type string (default: "CardekhoRival")id string nullablealias string nullablename string requiredbrand string nullableurl string nullableimage string nullableprice_min number nullableprice_max number nullablerating number nullablebody_type string nullablespecs array (default: [])@type string (default: "CardekhoFact")name string requiredvalue string nullable422 — 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 model page under that 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.