Carpool KR API: Wholesale Korean Car Data for Auto Traders

Carpool KR, a trade marketplace

Carpool KR is aimed at traders rather than private buyers. Its listings carry asking prices, so in KoreaCarsAPI it is a marketplace source with is_auction=false, using the same fields as the rest.

KoreaCarsAPI is an independent data service and is not affiliated with Carpool Korea.

Who uses wholesale listing data

Wholesale data is used by businesses that handle many cars at once.

• Traders abroad who fill containers and plan purchases by model mix.
• Distributors who compare wholesale asking prices with retail marketplaces in Korea.
• Inventory teams who keep a single stock database across several Korean sources.
• Developers who build the import pipeline that feeds all of the above.

What comes back for a Carpool KR listing

Each record has a vehicle part, with year, brand, model, generation, trim, engine volume, fuel, transmission, body type, colour and options, and a listing part, with the Carpool KR URL, title, odometer, price with currency, photos and the created_at, updated_at and last_seen_at dates. Prices keep a dated history.

The important point for volume work is that brand, model and generation are not free text. They link to the API's dictionaries, so a model is the same model whether it came from Carpool KR, Encar or an auction.

Which fields are filled depends on the listing. Where a public inspection or history report exists, it comes back in inspections[] and vehicle_history_reports[]; where it does not, the car's condition is simply unknown from the data. A missing report never means a clean history, which matters even more when a whole batch is planned on the strength of the records.

Using the dictionaries to normalise

Load the dictionaries once, cache them and refresh them now and then. GET /brands lists brands, GET /models/{brand_id} lists a brand's models, GET /generations/{model_id} lists a model's generations, and GET /car-options lists equipment options in English. With these, your filters and reports use one vocabulary across every source.

A practical pattern is to keep three small tables in your own database, brands, models and generations, keyed by the API's IDs, and to join every car to them. Reports on stock mix, purchase plans and price ranges then group cleanly, and a model never splits into two rows because one site spells it differently.

# Brands, then the models of one brand, then its generations
curl --get https://api.auctionsapi.com/brands -d api_key=$API_KEY
curl --get https://api.auctionsapi.com/models/BRAND_ID -d api_key=$API_KEY
curl --get https://api.auctionsapi.com/generations/MODEL_ID -d api_key=$API_KEY

# Equipment options dictionary
curl --get https://api.auctionsapi.com/car-options -d api_key=$API_KEY

Practical tips for volume buyers

Working at volume makes small data choices add up.

• Group stock by generation, not by model name, when you plan a purchase mix.
• Store dictionary IDs in your database, and show names only at the display layer.
• Sync the whole source with GET /cars and next_url, then work from your local copy.
• Track price history per car to spot sellers who adjust prices on a regular rhythm.
• Keep wholesale and retail sources in separate price reports, since they serve different buyers.

Carpool KR among the other Korean sources

Carpool KR belongs with the export and trade marketplaces: Autowini, Autobell Global, Sena Auto, RB Auto Trade, KS Cars and Mango Car. Together they show what Korean sellers offer to professional buyers abroad.

For a trader, the dealer auctions are the other reference point. Lotte Auto Auction, Autobell Auction and K Car Auction come back with is_auction=true and lot data. Comparing wholesale asking prices with auction lot data and with retail marketplaces like Encar shows where a model sits in each channel.

For testing the dictionaries and a Carpool KR export together, a demo key is available on request.

Questions