Encar API FAQ: your questions, answered

No. Encar.com does not provide a public API, a developer portal or a self-serve partner programme. Encar API is an independent service that delivers the same listing data through a clean REST endpoint.

A REST API that returns live Korean used car listings from Encar.com as JSON. Three endpoints, filters for brand, fuel, year, mileage and price, no scraping required.

Send a GET request to /cars with your filters and you get back paginated JSON. Authenticate by sending your key in the x-api-key header. A free key covers 100 requests a day and is issued instantly on this site.

Each listing includes manufacturer, model, badge, model year, mileage, fuel type, transmission, colour, price, engine output, photo paths, the Korean region the car stands in, and German and English translations of the model and trim. Over 200,000 live listings are available.

There is a free tier: 3,000 requests a month, no card, no expiry. Pro is 49 EUR a month for 150,000 requests, Business is 199 EUR for 750,000, and Enterprise is 499 EUR a month with no request cap. The monthly figure is a daily ceiling spread evenly, so one runaway script cannot spend the month in an afternoon.

Pass the filters as query parameters on /cars: manufacturer, model, fuel, transmission, colour, yearFrom and yearTo, mileageFrom and mileageTo, priceFrom and priceTo in EUR, and sort=priceAsc or priceDesc. Up to 500 listings come back per page.

The Price field on a listing is in units of 10,000 KRW, so 4339 means roughly 29,070 EUR. The priceFrom and priceTo filters, by contrast, are given in EUR and converted for you.

Request the vehicle with /car?id=... — availability is checked live on every detail call. A sold or withdrawn listing answers HTTP 404 with code SOLD_OR_REMOVED, which is your signal to remove it.

Yes, and that is the main use. K-Imports in Germany, Inspecto in Belarus and BBS Korea Auto Imports in Kosovo all run public inventory on it. Fetch when a visitor asks rather than on a schedule, and you can cache a response for a few minutes on your own server.

Korean source values plus a de and en block on every listing covering manufacturer, model group, model, badge and fuel type. The site and the documentation are published in ten languages.

Only if you want to maintain it. A scraper needs Korean proxies, breaks whenever the front end changes, and still cannot tell you reliably that a car has sold. The comparison page sets out all three approaches honestly, including when a bulk export beats an API.

There is no cache to go stale: the read against the Korean market happens when your request does. A car withdrawn an hour ago is already absent from your search results.