> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xapichina.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data fields

> Understand CNY/EUR prices, native Chinese values, listing IDs, and missing data.

## Listing identity

Search and detail responses represent `id` 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

| Field | Unit or interpretation |
| - | - |
| `price_cny` | Listing price in yuan, not units of 10,000 yuan |
| `price_eur` | Converted euro value, rounded to cents; nullable |
| `original_price_cny` | Source-provided original price, when available |
| `mileage_km` | Kilometers |
| `displacement_liters` | Liters |
| Search `year` | Listing year, where provided |
| Detail `model_year` | Model-year value, distinct from registration |
| `registration_date` | Source registration value, distinct from model year |

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](/pagination-and-filters).

## 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

The `che168` 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](/electric-vehicles) for source-key meanings, [CNY/EUR prices](/currencies-and-prices) for conversion and budget rounding, and [language behavior](/translations) 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](/inspection-and-insurance) before deriving a vehicle condition label.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.