Listing identity
Search and detail responses representid as a string. Pass that numeric listing ID into the car endpoint path, and retain source_url to link back to the original Che168 record. Do not confuse a listing ID with a VIN.
Prices and units
EUR conversion depends on an available exchange rate and is not a guaranteed purchase quote.
currency=eur changes search budget interpretation but does not replace CNY output fields. See filter rounding.
Languages
lang=en is the default on endpoints that accept a language. lang=zh returns Chinese display labels. Supported manufacturer, model, specification, location, and report labels are translated; unknown text and seller descriptions can remain Chinese.
The detail response’s che168 block preserves provider-native names, units, and original Chinese values in both languages. Missing native keys are omitted. Do not apply normalized CNY or metric-unit assumptions to arbitrary source fields without checking their meaning.
Native vehicle data
Theche168 object groups source data into catalog, specification, vehicle_identity, location, registration, electric_vehicle, warranty, finance, consumption, seller, media, report_services, and listing.
EV fields depend on the source listing. Missing battery, charging, range, or warranty data is not a zero value or proof that a feature is absent.
See EV and native vehicle fields for source-key meanings, CNY/EUR prices for conversion and budget rounding, and language behavior for fields that retain original Chinese values.
Unknown values
null, omitted source keys, an unavailable report, and an explicitly negative finding have different meanings. Preserve those distinctions in your database and user interface.
In reports, keep inspection dates separate from issue dates, source provider classifications separate from API calculations, and report advertising separate from parsed coverage. Read the report guide before deriving a vehicle condition label.