/carwale/used_cars

POST /api/carwale/used_cars

Price: 20 credits

Get a CarWale used-car listing by id or URL: price with market valuation and new-car price, year, registration, km, fuel, transmission, colour, owners, insurance, seller details, certification report by component, specifications, features, highlights and photos

How to use it

Find listing ids with carwale/used_cars/search; is_sold marks a listing that has been sold.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — CarWale used-car listing id or listing URL (examples: "7cuodc1k", "https://www.carwale.com/used/mumbai/kia-seltos/7cuodc1k/")

Response

• @type string (default: "CarwaleUsedListing")
• id string required
• profile_id string nullable
• url string required
• make string nullable
• make_id string nullable
• make_alias string nullable
• model string nullable
• model_id string nullable
• generation string nullable
• generation_id string nullable
• version string nullable
• version_id string nullable
• year integer nullable
• month string nullable
• registered_at integer nullable
• registration_number string nullable
• registration_type string nullable
• registration_city string nullable
• currency string (default: "INR")
• price number nullable
• price_text string nullable
• market_price number nullable
• market_price_range string nullable
• new_car_price number nullable
• price_verdict string nullable
• price_notes array (default: [])
• emi_text string nullable
• km_driven integer nullable
• fuel_type string nullable
• additional_fuel string nullable
• transmission string nullable
• color string nullable
• interior_color string nullable
• body_type_id string nullable
• owner_count integer nullable
• insurance string nullable
• insurance_expiry string nullable
• fuel_economy string nullable
• city string nullable
• city_id string nullable
• available_at string nullable
• is_certified boolean nullable
• is_sold boolean nullable
• is_luxury boolean nullable
• updated_at integer nullable
• seller_type string nullable
• seller_name string nullable
• seller_area string nullable
• seller_address string nullable
• seller_pincode string nullable
• seller_state string nullable
• seller_google_rating number nullable
• seller_listing_count integer nullable
• dealer_id string nullable
• seller_note string nullable
• seller_special_message string nullable
• is_home_test_drive boolean nullable
• home_test_drive_fee number nullable
• video_url string nullable
• reason_for_sale string nullable
• inspection_score number nullable
• inspection_condition string nullable
• inspection array (default: [])
  • @type string (default: "CarwaleInspectionItem")
  • name string required
  • score number nullable
  • condition string nullable
  • checks array (default: [])
• image string nullable
• images array (default: [])
• highlights array (default: [])
• key_features array (default: [])
• specs array (default: [])
  • @type string (default: "CarwaleSpec")
  • group string nullable
  • name string required
  • value string nullable
• features array (default: [])
  • @type string (default: "CarwaleSpec")
  • group string nullable
  • name string required
  • value string 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 — CarWale 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.