KB ChaChaCha API: Korean Used Car Prices for Comparison

KB ChaChaCha in short

KB ChaChaCha is a marketplace where cars are listed for sale with an asking price. Its parent, KB Capital, belongs to KB Financial Group, one of the large financial groups in Korea. For data purposes, what matters is that it is a separate pool of listings with its own sellers and its own pricing.

KoreaCarsAPI is independent and has no affiliation with KB ChaChaCha or KB Capital. The API returns what the site shows publicly, in a structured form.

Why a second marketplace changes your price picture

Looking at one site gives you one opinion of the market. The same model, year and trim can be listed at noticeably different asking prices on two sites, and a quote built on a single source can be off in either direction. Adding KB ChaChaCha helps in several concrete situations:

• An exporter quoting a client abroad wants a range, not a single listing, before naming a figure.
• A reseller wants to know whether a car on Encar is priced high or low against comparable cars elsewhere.
• A pricing model needs more samples per generation and trim to stay stable for less common versions.
• An analyst tracks how long cars stay listed and how often prices are cut on each site.

The fields that matter for price work

KB ChaChaCha records use the same format as Encar, so the comparison is field to field. On the vehicle side you get year, brand, model, generation, trim, engine volume, fuel, transmission, body type, colour and options. On the listing side you get the price with its currency, the odometer, photos, the source URL and the created_at, updated_at and last_seen_at dates.

Two parts are especially useful for pricing. The price history records each price change with its date, which shows how a seller moved over time. The created_at and last_seen_at dates tell you how long a car has been on the market. Inspection and history data appear when the listing shows them publicly.

Querying comparable cars

GET /search filters by brand, model, generation, trim, year, price, odometer, fuel, transmission and colour. Add domains[] with KB ChaChaCha's ID from GET /domains to search that source only, or add Encar's ID as well to get both, with external.domain on each listing telling you which site it came from. Start with GET /search/count to see how many cars match, then fetch them.

# BRAND_ID from GET /brands, MODEL_ID from GET /models/{brand_id}
curl --get https://api.auctionsapi.com/search/count \
  -d "brands[0][id]=BRAND_ID" \
  -d "brands[0][models][0][id]=MODEL_ID" \
  -d odometer_from=30000 \
  -d odometer_to=80000 \
  -d api_key=$API_KEY

Tips for a fair comparison

Price comparisons go wrong in predictable ways. These rules keep them honest.

• Compare by generation and trim, not just model. A facelift or a higher trim can explain most of a price gap.
• Group mileage into bands instead of comparing exact odometer readings.
• Drop cars whose last_seen_at is old, so sold cars do not drag your average.
• Remember these are asking prices, not final sale prices.
• Keep the currency field with every price you store.

KB ChaChaCha with Encar, K Car and the auctions

The usual setup is three marketplaces in one table: Encar for breadth, KB ChaChaCha as the second opinion, and K Car for stock from a single direct seller. Because all three share one record format, you write one parser and one set of filters. If a VIN appears on more than one site, GET /cars/vin/{vin} returns the listings together, which also catches the same car priced differently in two places.

For the trade side, add dealer auctions such as Lotte Auto Auction or Autobell Auction. They come back with is_auction=true and show lot data, which helps you see how retail asking prices compare with what is offered to dealers.

Questions