Skip to main content

​
Retrieve native specifications

Use the vehicle detail endpoint. EV source fields are under che168.electric_vehicle, rather than a separate battery endpoint.
Use an ID from an actual EV listing. The example ID demonstrates the endpoint format and does not guarantee a particular fuel type or field coverage.

​
Source field groups

Values use the provider’s original names and units. Some are strings, flags, or source codes; they are not guaranteed normalized numbers. Missing keys are omitted. The EV block is only exposed when the source marks the vehicle as new-energy. Source payloads can contain placeholder EV fields even for other vehicles; their presence alone does not establish that a car is electric.

​
Warranty and registration

che168.warranty retains source warranty flags/descriptions. che168.registration retains registration, emissions, transfer-count, inspection-expiry, and insurance-expiry context where supplied. An insurance-expiry field is not an insurance claim record. Use normalized detail fields for common display needs, and native blocks for source-specific information. Unsupported or missing battery/warranty data should appear as unknown rather than zero capacity or no coverage.

​
Search for new-energy inventory

Discover the current enums with /v1/filters. The new-energy category is a marketplace classification; check each vehicle’s actual specifications before assigning a narrower fuel or battery label.