Korean car data for Russia and the CIS
Live Korean listings as JSON with a Russian-language reference, used by inspection and import businesses across the region.
Русский →Полная документация на русском — эндпоинты, поля, цены.Who uses it here
Inspecto, a vehicle inspection service in Minsk, runs on these endpoints. The use case is a step away from the usual stock page: a listing id arrives from a client, the single-vehicle endpoint is called for the full record, and the live availability check answers the question the client is really asking — is this car still for sale, or am I looking at a listing that closed last week.
That availability check only exists on single-vehicle lookups, and it is the reason this shape of business works at all against a marketplace that moves as fast as Encar does.
curl -H "x-api-key: YOUR_KEY" "https://api.encar-api.com/api/car?id=38421907"Russian documentation, English identifiers
The site is published in Russian at encar-api.com/ru — prose, endpoint explanations, pricing and FAQ. Parameter and field names stay in Latin script because they are typed verbatim into code, and a translated identifier would be an identifier that does not work.
One thing to be straight about: the per-listing translations are English and German. There is no Russian field block. Russian-language integrators render the en values, which is what the ones named above do.
Fields worth knowing before you start
The unit traps are the same everywhere and worth reading once rather than debugging twice.
| field | what it holds |
|---|---|
| Id | Encar listing id. Pass it to /car to get the full vehicle. |
| Manufacturer / Model / Badge | Korean source values. Badge is partly Korean — prefer the de / en block below. |
| de / en | The same car translated: manufacturer, modelGroup, model, badge, fuelType. Render these. |
| Price | In units of 10,000 KRW. EUR ≈ Price × 6.7, so 4339 is about €29,070 — not €4,339. |
| Year | YYYYMM, not a year: 201902 is February 2019. FormYear holds the plain "2019". |
| Mileage | Kilometres, as an integer. |
| FuelType | Korean. The translated value is in de.fuelType / en.fuelType. |
| Photo / Photos[] | Relative paths. Prefix them with the image host; with Photo, append 001.jpg. |
| priceDrop | Present when the seller cut the price: previousPrice, droppedAt. |
| powerPs / powerKw | Engine output, where the trim is known. |
| OfficeCityState | Where the car stands, as a Korean region name. |
Questions people ask about this
Is there Russian-language documentation?
Yes, the full site is published in Russian at encar-api.com/ru. The per-listing field translations, however, are English and German only — Russian-language integrators render the English values.
Get your API key
Free tier, 100 requests a day. Enter your email and the key arrives immediately, with everything you need to make the first call.
- 100 requests a day
- No credit card
- Your key never expires
Questions, or Pro and Enterprise volume? Reply straight to the key email — it reaches a person, not a form. Or message us on WhatsApp if that is quicker: +383 49 644 168
Get a free key
100 requests a day, no card. Russian documentation and instant issuance.
Keep reading
Not logos. Three live businesses importing Korean cars into three different markets, each serving its public inventory from these endpoints.
Three endpoints, one header, JSON out. Everything below is the complete reference — there is no second, paid tier of documentation.
The data comes from a Korean source, so four of these fields are read wrong by default. Each one fails silently — your page renders, it is simply incorrect.