Encar API

Get Encar data with one API

The Encar API returns used-car listings from South Korea's largest car marketplace as clean JSON.

E
/encar/v1

3 active endpoints, on 0 and 1 credit tiers.

  • POST/encar/v1/search
  • POST/encar/v1/detail
  • POST/encar/v1/makes

What Encar endpoints does ReefAPI ship?

3 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.

3 endpoints

search

1 cr

Search live Encar used-car listings by structured filters.

required
optional
make, model, trim, car_type, fuel, transmission, region, price_min, price_max, year_min, year_max, mileage_min, mileage_max, sort, page, size

detail

1 cr

Full detail for one car by id.

required
id
optional

makes

0 cr

Browse all Korean (domestic) and imported makes available on Encar, each with its live listin…

required
optional
car_type

Every parameter, every allowed value →

Encar API

3 of 3 endpoints, ready to run

View docs ↗

Search live Encar used-car listings by structured filters.

1 credit0 required · 2 optional
POST/encar/v1/search
idle
// Press "Try it" and this pane shows exactly what the
// live site returned this second — including an empty
// result, if that is the truth. No key, no account.

How the Encar API works

Encar is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.

01
Authenticate
x-api-key header

No OAuth app, no request signing, no per-site account. One key covers all 185 engines.

02
Call
POST /encar/v1/…

Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.

03
Pay
0 or 1 credits per call

Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.

04
Read
{ ok, data, meta, error }

One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.

Encar units, Korean enum values and the two different car ids

Encar is a Korean-language marketplace, and the API keeps its native units and vocabulary rather than translating them. The 만원 price unit and the pair of ids are the two places integrations get the numbers wrong. Every value below was read from live search, detail and makes calls on 2026-08-27.

FieldMeasured valueWhat it means
price_manwon2630The price in 만원 (10,000 KRW), the unit Encar itself uses. That is ₩26,300,000, not ₩2,630.
price_krw26300000The same price in won. price_manwon x 10,000 = price_krw held on every car sampled.
price_min / price_max1000 = ₩10,000,000The search filters are in 만원 too, not won.
origin_price_manwon4043The car's original list price when new, also in 만원 (₩40,430,000). detail only.
mileage_km93428Kilometres, as an integer. mileage_min and mileage_max are km as well.
year / year_month / form_year2017 / "2017-08" / "2018"Model year, first-registration month, and the Korean 연식. form_year can be one year ahead of year.
fuel_type"디젤", "가솔린", "가솔린+전기"Korean strings for diesel, gasoline and gasoline+electric. The fuel filter still takes English keys.
make"현대" (detail adds make_en "Hyundai")search returns Korean only. detail adds make_en, model_group_en and grade_en.
transmissionnull in search, "오토" in detailSearch rows returned null transmission on every car sampled; only detail resolves it.
idsearch 41994544 -> detail 41991990Two different numbers for the same car. See the note below.

The id a search row gives you is not the id detail answers with. Three cars checked on 2026-08-27: 41994544 came back as 41991990, 41543563 as 41543552, and 42033010 as 42032424. The detail id is the canonical one, matching the photo filenames and the carid in the URL detail returns. Pass the search id and detail resolves it correctly, but do not join search rows to detail rows on id. Store both.

What people build with Encar

The jobs this data is most often used for.

3

endpoints

0/1

credits per call

01

Automotive pricing tools call search to track Korean used-car prices by make, model and mileage.

02

Dealer-intelligence products use detail to assess a specific listing's condition and spec.

03

Market analysts use makes and search to size supply and price ranges across the Korean market.

What Encar data costs

The cheapest call here is 0 credits, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.

Full pricing →
$0.67–$1.50 / 1,000 credits
  • 1,000 free credits on signup, no card
  • One key, all 185 APIs, one credit pool
  • Failed and blocked calls are never charged
  • Credits roll over and never expire

Call it in two lines

Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.

curl
curl -X POST https://api.reefapi.com/encar/v1/search \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"make":"Hyundai","size":20}'
python
import requests

r = requests.post(
    "https://api.reefapi.com/encar/v1/search",
    headers={"x-api-key": REEF_KEY},
    json={
  "make": "Hyundai",
  "size": 20
},
)
print(r.json()["data"])
FAQ

Have a question? We got answers.

The questions people actually ask before wiring up Encar.

Get a free key →
Does price_manwon 2630 mean 2,630 won?

No. 만원 is Korea's ten-thousand-won unit, so price_manwon 2630 is ₩26,300,000, roughly the price of a used Grandeur hybrid, which is what that car was. The API removes the guesswork by returning price_krw alongside it, 26300000 for that car, and the relationship price_manwon x 10,000 = price_krw held on every car sampled. The price_min and price_max search filters are in 만원 as well, so price_min 1000 means ₩10,000,000.

Why does detail return a different id than the one I sent?

Encar carries two numbers for one car: the advert id you get from search, and a canonical listing id used by the detail page, its URL and its photo filenames. Sending id 41994544 returned a record whose id was 41991990, with photos at .../41991990_006.jpg. The same happened with 41543563 to 41543552 and 42033010 to 42032424. detail resolves the search id correctly, so the calls work, but if you key a database on id you will fail to match the two responses. Store the search id as your request key and the detail id as the canonical one.

Why is transmission null in search results?

The search listing surface does not carry it. transmission came back null on every car in a live Hyundai search on 2026-08-27, even though transmission is a valid search filter. detail resolves it, returning the Korean value "오토" for automatic. So you can filter by transmission, automatic or manual, and get correct results, you just cannot read the value back off a search row. Call detail for the cars you care about.

Why are make, model and fuel_type in Korean?

Because they are Encar's own values, kept as-is rather than translated. A Hyundai search returned make "현대", models like "싼타페 DM" and "더 뉴 그랜저 IG 하이브리드", and fuel_type "디젤", "가솔린" and "가솔린+전기". The inputs are friendlier than the outputs: make accepts English names and translates them, and fuel takes English keys such as diesel, gasoline, hybrid and electric. model and trim are the exception and need the exact Korean string from a search result. detail also returns make_en, model_group_en and grade_en, so "현대" comes back with "Hyundai", "그랜저" with "Grandeur" and "르블랑" with "Le Blanc".

What do accident_record_available and seizing_count mean?

accident_record_available, accident_resume_available and inspection_available say whether that report exists for the car, not what it says. A car sampled on 2026-08-27 returned accident_record_available false with accident_resume_available true and inspection_available true, so false there means no such record is offered, not that the car is accident-free. seizing_count and pledge_count are the legal encumbrance counts, 압류 and 저당, and 0 for both is the clean case you want. status "ADVERTISE" means the advert is live.

What is the difference between year, year_month and form_year?

year is the model year as an integer, year_month is the first-registration month as "YYYY-MM", and form_year is the Korean 연식 returned as a string. They are not always the same: one car returned year 2017, year_month "2017-08" and form_year "2018". The year_min and year_max filters take a plain year, 2020, or a YYYYMM value, 202006, if you want month precision.

How do I find valid make values, and how much inventory does each have?

The makes action returns all 25 makes with live counts pulled from the search index, each with make, make_en, car_type and count. On 2026-08-27: Kia (기아) 52,357, Hyundai (현대) 52,149, BMW 17,874, Mercedes-Benz (벤츠) 16,438, Genesis (제네시스) 13,496, Audi (아우디) 4,622, Porsche (포르쉐) 3,221 and Tesla (테슬라) 1,475. car_type separates domestic Korean brands from imported ones and is also a search filter on its own.

What is origin_price_manwon useful for?

It is the car's original list price when new, in the same 만원 unit, so it gives you depreciation without a valuation dataset. A 2022 Grandeur hybrid returned origin_price_manwon 4043 against price_manwon 2630, meaning ₩40.43M new and ₩26.3M now. It is a detail-only field; search rows do not carry it. Note that option_codes on the same record are 3-digit numeric strings, "001", "004", "005", rather than option names.

What is the Encar API?

Encar API is a ReefAPI endpoint group for encar It returns live JSON through POST requests under /encar/v1.

Is the Encar API free to try?

Yes. ReefAPI starts with 1,000 free credits, no card required. Encar calls use the same shared credit balance as every other ReefAPI engine.

Do I need an Encar login or account?

No login to Encar is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

How fresh is the Encar data?

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

How many credits does the Encar API use?

Encar actions currently cost 1 credit per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

Can I call Encar from an AI assistant or MCP client?

Yes. Connect ReefAPI once through MCP and your assistant can call encar actions with the same key, credit pool and JSON envelope used by normal REST requests.

37 E-commerce & Marketplaces APIs on the same key

One key, one credit pool, one response envelope. If you are pulling Encar, you are one call away from the rest of the category — no second contract, no second integration.

Try it on your own data before you pay anything

The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 184 APIs, and the same envelope everywhere.

Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts.