Getting Full Vehicle Detail, Photos and Inspection Reports from the Encar API

Searching listings gets you a car's id plus enough fields for a results grid. To build an actual listing page with extended specs, available photo URLs and accident history, use GET /v1/cars/{car_id}.

Full detail

curl "https://api.xapikorea.com/v1/cars/40907726?lang=en" \
  -H "X-API-Key: enc_your_key_here"

The response can include extended specifications, available media and condition fields:

{
  "id": 40907726,
  "manufacturer": "Hyundai",
  "model": "Tucson",
  "badge": "Diesel 2.0 2WD Modern",
  "year": "202103",
  "mileage_km": 45000,
  "price_krw": 23500000,
  "original_price_krw": 31000000,
  "fuel_type": "Diesel",
  "transmission": "Automatic",
  "engine_cc": "1999cc",
  "color": "White",
  "vin": "KMHxxxxxxxxxxxxxx",
  "photos": ["https://ci.encar.com/.../001.jpg", "..."],
  "had_accident": false,
  "had_simple_repair": false,
  "damage_severity": "none",
  "inspection_grade": "Good",
  "options": ["Navigation", "Sunroof", "Heated Seats", "Rear Camera"],
  "inspection_report_url": "https://fem.encar.com/cars/report/inspect/40907726"
}

The accident/damage fields (had_accident, damage_severity, panel_damage, usage_history, is_rental) come straight from Encar's official inspection data. It's the same condition information Korean buyers rely on, just in structured JSON instead of a rendered report page.

A 404 means the car isn't listed anymore (sold or removed). A 502 means Encar's own backend hiccuped on that request. Both are worth handling explicitly if you're building anything that fetches detail pages in bulk.

Just the photos, or just the inspection

If you only need photo URLs or inspection fields, two focused endpoints return smaller, purpose-specific response payloads:

• GET /v1/cars/{car_id}/images: returns the plain array of photo URLs, nothing else.
• GET /v1/cars/{car_id}/inspection: returns just the condition/inspection fields (had_accident, damage_severity, inspection_grade, inspection_report_url, etc.) without the rest of the spec sheet.

The inspection endpoint is smaller for the client, but it is not a lighter upstream operation: the backend still fetches the full vehicle detail to derive the inspection response. Use it when the narrower response shape is convenient, not to reduce upstream fetching.

"You might also like"

GET /v1/cars/{car_id}/similar returns other listings of the same manufacturer and model, excluding the car itself. It's the same shape as /v1/search results, so it drops straight into the same UI component you're already using for search results. A one-line way to add a "similar listings" section to a detail page.

curl "https://api.xapikorea.com/v1/cars/40907726/similar?limit=6&lang=en" \
  -H "X-API-Key: enc_your_key_here"

Where the data comes from

Detail, image and inspection responses are cached for 5 minutes, so repeat requests for a popular listing do not re-hit the upstream site during that window. Similar-listing responses use the 60-second search cache. Cached responses still count toward your monthly quota. If you need summary rows for thousands of cars instead of detail records one at a time, see the bulk export guide for the Pro and Enterprise NDJSON stream.