AutoHub API: Listing Data From the Yongin Used Car Complex

A marketplace with a physical address

Most marketplaces are online only. AutoHub's listings belong to a large physical complex, so the cars can be visited in one place. That makes AutoHub data a planning tool: you shortlist online, then inspect in person or send someone to do it.

KoreaCarsAPI is an independent data service and is not affiliated with AutoHub. Note that autohubauction.co.kr is a different site: it opens Kolon Auto Auction, a dealer auction, not the Yongin complex listings.

Who uses AutoHub data

The physical side of AutoHub shapes who finds its data useful.

• Exporters and their agents in Korea who plan a day of viewings and want a precise list before they arrive.
• Buyers abroad who work with a local inspector and send a shortlist of cars to check.
• Resellers who compare complex prices with online marketplaces for the same models.
• Developers building a viewing planner or shortlist tool for agents.

What the API returns for AutoHub

AutoHub records follow the marketplace format. The vehicle part holds year, brand, model, generation, trim, engine volume, fuel, transmission, body type, colour and options. The listing part holds the AutoHub URL, title, odometer, price with currency, photos, the created_at, updated_at and last_seen_at dates and a price history.

For a visit, last_seen_at is the key field. It tells you when the listing was last active, which helps you avoid travelling for a car that has already gone.

Photos carry extra weight here as well. If an agent will see the car in person, the photo set is the checklist: it shows what to look at, and it lets the agent compare the car on the day with how it was listed. Where the listing has public inspection or history data, it appears in inspections[] and vehicle_history_reports[], which gives the agent more to check against.

Shortlisting by mileage and model

GET /search is the natural tool for a shortlist. Filter by brand, model, year, fuel, transmission and an odometer range, and add domains[] with AutoHub's ID from GET /domains to keep the search on AutoHub. For the whole AutoHub stock, use GET /cars with its entry in domains[].

# Shortlist: one model, automatic (transmission=1), 20,000 to 70,000 km
curl --get https://api.auctionsapi.com/search \
  -d "brands[0][id]=BRAND_ID" \
  -d "brands[0][models][0][id]=MODEL_ID" \
  -d transmission=1 \
  -d odometer_from=20000 \
  -d odometer_to=70000 \
  -d api_key=$API_KEY

# Add -d "domains[]=SOURCE_ID" (ID from GET /domains) to keep only AutoHub listings

Practical tips before a visit

The goal is a short, accurate list on the day you go.

• Refresh the list the evening before and drop anything with an old last_seen_at.
• Print or share the external.url for each car, so the person on site can match the listing.
• Check the photo set for the points you will want to see in person.
• Note the price history: a car with recent cuts may be worth a closer look.
• Look for public inspection or history data, but never read a missing report as a clean history.

AutoHub alongside the online marketplaces

AutoHub is a good counterweight to purely online stock. Comparing its asking prices with Encar, KB ChaChaCha and K Car for the same model and mileage tells you whether the complex is a good place to look for a given car. All of them share a record format, so the comparison needs no extra parsing.

If a car on AutoHub has a VIN, GET /cars/vin/{vin} shows whether it is also listed online, sometimes with more photos or a different price.

For the trade side, dealer auctions such as Lotte Auto Auction and K Car Auction come back with is_auction=true. They are a different channel from a retail complex, so keep them in a separate column of your comparison.

Questions