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

# English and Chinese output

> Use supported translations while preserving original Che168 and report values.

## Choose a display language

English is the default on routes with a `lang` parameter. Use `lang=zh` for Chinese display values:

```bash theme={"system"}
curl --fail-with-body "https://api.xapichina.com/v1/search?brand=BMW&lang=zh" \
  -H "X-API-Key: $XAPICHINA_API_KEY"
```

```bash theme={"system"}
curl --fail-with-body "https://api.xapichina.com/v1/cars/59967821?lang=en" \
  -H "X-API-Key: $XAPICHINA_API_KEY"
```

Language selection is available for manufacturers, model discovery, search, details, similar listings, inspections, and insurance-event evidence. Filters accept a language for manufacturer names. Counts and image galleries do not accept a language parameter.

## What is translated

Supported manufacturer/model names, specification labels, locations, and inspection display labels can be translated. Unknown names, free-form seller descriptions, and unsupported report text can remain Chinese.

`brand` accepts Chinese or supported English names, catalog IDs, or pinyin. The `model` filter accepts Chinese or supported English model names/keywords. Raw `q` is a Che168 keyword, not a general-purpose automatic translation feature.

## Original fields stay available

`che168` in a detail response preserves the source's original field names, language, and units in either display language. Report fields such as `source_name`, `source_status`, `source_remarks`, `source_label`, and `source_fields` preserve original evidence.

Store both a display value and the source value when auditability matters. Do not overwrite original report wording with a guessed English translation or infer a vehicle's condition from an unfamiliar label.

## Build language-aware applications

Include language in your own cache keys for translated responses. Keep stable listing IDs and source URLs separate from display titles. A title can vary with language or upstream edits while referring to the same listing.

See [native data fields](/data-fields) and [provider reports](/inspection-providers) for interpreting untranslated values.


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