Why there is no English Encar
Encar is built for the Korean domestic market, where essentially every user reads Korean. An English edition would serve exporters and foreign buyers — a small fraction of its traffic — so it has never been a priority. There is no sign of that changing.
What machine translation does to a trim name
Korean badge strings are dense: a single field might encode engine, seat count, drivetrain and trim level at once. A general-purpose translator renders these literally and produces names that no longer match any real variant, which makes them impossible to compare or search. Translating the page is not the same as translating the data.
The two numbers that catch everyone once
Price is quoted in units of 10,000 KRW, so a listing showing 4339 is roughly €29,070 and not €4,339 — an order-of-magnitude error that looks plausible enough to act on. And the year field is YYYYMM, so 201902 means February 2019, not the year 201,902. Every integration makes one of these mistakes exactly once.
Translated at the source instead
Rather than translating rendered pages, this API attaches an English and a German block to every listing, covering manufacturer, model group, model, badge and fuel type. Those come from mapping Korean values to their real counterparts, so a 3 Series stays a 3 Series and a trim name stays comparable across listings.
Browsing the market in English today
The brand and model pages on this site are the Korean market rendered in English and nine other languages: live counts, median prices, model mixes and Korean trim tables, each page naming the request that produced it. Start from the brand you care about and work down.
