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

# EV and native vehicle fields

> Read source battery, range, charging, motor, and warranty values without guessing missing data.

## Retrieve native specifications

Use the [vehicle detail endpoint](/api-reference/details). EV source fields are under `che168.electric_vehicle`, rather than a separate battery endpoint.

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

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

| Native key | What to retain |
| - | - |
| `isev` | Source new-energy vehicle flag |
| `batterypower` | Source battery capacity value and its supplied units |
| `lifemileage` | Source range figure and its stated convention |
| `quickcharge`, `slowcharge` | Source charging figures |
| `batterytype`, `batterybrand` | Source battery type and brand labels |
| `drivingnum` | Native motor/drive configuration value |
| `accelerate` | Source acceleration figure |
| `ev100power` | Source energy-consumption value |
| `evwarranty` | Source battery warranty description |
| `baastype` | Native battery-service information, when supplied |

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

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

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.


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