POST /api/dongchedi/used_cars
Price: 5 credits
Get a Dongchedi used-car listing by id or URL
Get one used-car listing from Dongchedi: asking price and the new-car price in CNY, registration month, mileage, the seller's description and photos, key specs, the inspection report with defects found, financing terms and the selling dealer. Listing ids come from dongchedi/used_cars/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)used_car string required — Dongchedi used-car listing id or listing URL (examples: "357014057", "https://www.dongchedi.com/usedcar/357014057")@type string (default: "DongchediUsedCar")id string requiredurl string requiredtext string nullableimages array (default: [])currency string (default: "CNY")price number nullablenew_price number nullablenew_price_with_tax number nullableregistration_year integer nullableregistration_month integer nullablemileage_km integer nullablecity string nullablebody_color string nullablemodel_year integer nullablemodel_id string nullablemodel_name string nullableseries_id string nullableseries_name string nullablebrand_id string nullablebrand_name string nullablespu_id string nullableheadline string nullablekey_facts array (default: [])@type string (default: "DongchediNamedValue")name string requiredvalue string nullabledetails array (default: [])@type string (default: "DongchediNamedValue")name string requiredvalue string nullablespecs array (default: [])@type string (default: "DongchediSpecValue")key string requiredvalue string requiredhighlight_features array (default: [])tags array (default: [])is_dongchedi_direct boolean (default: false)seller_perks string nullablevalue_retention_note string nullableprice_comparison object nullable@type string (default: "DongchediPriceComparison")verdict string nullabledescription string nullablesimilar_price_avg number nullablefair_price_min number nullablefair_price_max number nullablesimilar_mileage object nullable@type string (default: "DongchediPriceCohort")listing_count integer nullableprice_avg number nullableprice_min number nullableprice_max number nullablefair_price_min number nullablefair_price_max number nullableprice_percentile number nullablesame_year object nullable@type string (default: "DongchediPriceCohort")listing_count integer nullableprice_avg number nullableprice_min number nullableprice_max number nullablefair_price_min number nullablefair_price_max number nullableprice_percentile number nullablefinancing object nullable@type string (default: "DongchediFinancing")down_payment number nullabledown_payment_ratio number nullablemonthly_payment number nullableterm_months integer nullableinspection object nullable@type string (default: "DongchediInspection")summary array (default: [])@type string (default: "DongchediNamedValue")name string requiredvalue string nullablecategories array (default: [])@type string (default: "DongchediInspectionCategory")name string requiredchecked_count integer nullabledefect_count integer nullablefindings array (default: [])@type string (default: "DongchediInspectionFinding")name string nullabledescription string nullableimage string nullableshop object nullable@type string (default: "DongchediShop")id string nullablename string nullableshort_name string nullablecity string nullableaddress string nullableimage string nullablelicense_image string nullablebusiness_hours string nullablelisting_count integer nullablesales_area 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 — Listing not found or already sold. 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.