How to Read a Che168 Inspection Report Before Shortlisting a Car
Understand Che168 inspection availability, provider conclusions, partial reports and insurance evidence when building with XAPI China.
7 minute read
A report advertised on a Che168 listing and a report whose findings are accessible through an API are different things. In XAPI China, check both available and data_available before displaying a vehicle-condition summary.
This guide explains the API's report states and how to preserve provider evidence. It is not a universal translation of every inspection provider's grading system. XAPI China is an independent service, not affiliated with Che168 or the report providers.
A buyer’s checklist before reading API fields
Keep the original report together with the listing URL and seller-confirmed vehicle identity. Record the provider, report date and inspected scope before comparing the findings with another car.
| Question | Evidence to retain |
|---|---|
| Does this report belong to the candidate? | Vehicle identity and original source link |
| When was the inspection performed? | Report date and any later information supplied |
| What was actually inspected? | Report scope and original findings |
| What could not be checked or accessed? | Missing sections and explicit unknown states |
| Who can explain the remarks? | Responsible seller or inspecting specialist |
Use this worksheet to request clarification and photographs for specific findings. An inspection grade from one provider should not be treated as equivalent to the same-looking grade from another provider without its source meaning.
The API examples below explain how a dealer or research tool can preserve this evidence. They are optional implementation steps for a buyer reading the original document.
Start with the listing and the report provider
Keep the listing ID and source_url when you retrieve a vehicle. Use the ID from your actual search, rather than a sample ID from documentation. Then request the inspection summary:
export XAPICHINA_API_KEY="xcn_YOUR_KEY"
# Replace LISTING_ID with a current ID returned by search.
curl --fail-with-body \
"https://api.xapichina.com/v1/cars/LISTING_ID/inspection?lang=en" \
-H "X-API-Key: $XAPICHINA_API_KEY"
The default summary includes provider conclusions and coverage information where supported. Sources can include CARtech, Chaboshi and supported Che168 reports. Coverage depends on the particular listing and report.
Retain report_provider and the source report date when present. Two providers may use different category names or grade scales. A matching letter or translated label does not establish an equivalent assessment.
Read availability before conclusions
| Field | What it answers | What it does not establish |
|---|---|---|
available | Is an inspection or condition report advertised? | That its findings were extracted |
data_available | Were supported findings extracted? | That every section is complete |
parse_status | How did extraction finish? | The vehicle's condition |
conclusions | What classifications did the provider supply? | A universal condition score |
categories | Which source categories and coverage are present? | That absent categories passed |
The extraction status can be not_available, parsed, partial, unsupported or unavailable. These describe access and extraction. An unsupported report is not a failed vehicle inspection, and a parsed report is not automatically a clean result.
A partial response can contain useful findings, but the gaps must remain visible. Show “findings unavailable” when there is no accessible evidence, rather than interpreting an empty array as “no problems.”
Separate full component findings from summary labels
To inspect supported component-level findings, request the full view:
curl --fail-with-body \
"https://api.xapichina.com/v1/cars/LISTING_ID/inspection?view=full&lang=en" \
-H "X-API-Key: $XAPICHINA_API_KEY"
This can add category items, remarks and original provider wording. Preserve distinctions such as normal, abnormal, unknown, absent and uninspectable. A component that could not be inspected should not become a passed check in your interface.
Prefer native provider categories and the explicitly separated derived observations. Older compatibility fields such as damage_severity are deprecated; do not build a new condition model around them. See the provider documentation for source-specific behavior.
Keep Chinese evidence alongside English labels
lang=en translates supported display values. Some remarks and original source fields can remain Chinese. Keep fields such as source_label, source_status, source_remarks and source_fields where supplied, so a translated summary can be traced to the original evidence.
Do not assign a severity simply because a label is unfamiliar. Display the original provider wording and leave an uncertain interpretation unresolved. The English access guide explains how translated and native values coexist.
Inspection findings are different from insurance history
A physical inspection's accident, flood or fire classification describes that inspection. It is not proof that no insurance claims occurred in the past.
XAPI China's insurance endpoint currently does not provide structured insurance claim history. Its available field is false. It can still expose report-advertising information and supported insurance-event query evidence:
curl --fail-with-body \
"https://api.xapichina.com/v1/cars/LISTING_ID/insurance?lang=en" \
-H "X-API-Key: $XAPICHINA_API_KEY"
Query evidence can include source notices, lookup dates or receipt links. A result of no_records_returned does not establish that a vehicle has a clean history. Missing values must stay missing, rather than becoming “no claims.”
Display reports without hiding the limits
A useful report panel shows the provider, report date when supplied, extraction status and accessible findings together. Keep a link to the original listing and report where available. Report links can expire or have provider access requirements.
For a partial report, label the missing coverage beside the findings. For an unknown component, preserve an unknown state. For a provider grade, show its source context instead of converting every provider into an invented common score.
If your next step is implementation, follow the Che168 Python tutorial and the inspection and insurance documentation. Each successful report request consumes a data request, so retrieve reports for a deliberate shortlist rather than every search result.
Continue reading
Related guides
Che168 Asking Price vs Exporter's Quote: What Explains the Difference?
Separate a Che168 listing price from inspection, exporter and transport charges, then compare two quotations using the same scope and currency.
China-Spec vs GCC-Spec Cars: A Checklist for UAE Buyers
Compare the exact China-market and GCC-market vehicle versions, with a worksheet for equipment, warranty, software, charging and registration questions.
China or Korea? How to Compare Used-Car Sourcing Options
Compare used-car candidates from China and Korea using the same vehicle requirements, condition evidence and itemized destination quotations.