Encar scraping automates collection of listings from South Korea’s #1 used-car marketplace (Encar.com, KRW pricing) for exporters, dealers, and aggregators who need prices, mileage, inspection reports, and history without manual copy-paste from Korean UI. VivaCoding builds compliant pipelines: schedules, dedup by listing and VIN, key-field translation, CRM and catalog export — accounting for no public read API and Korea’s export-oriented market dynamics.
Encar (SK group) dominates Korea’s used-car digital market: millions of monthly views, the default reference before purchase and export to CIS, Middle East, and Southeast Asia. The differentiator is detailed inspection reports (Encar Diagnosis / performance check) that overseas buyers miss without structured collection. Below: platform overview, data schema, technical barriers, and VivaCoding pipeline design.
Key takeaways
- Encar leads Korea’s used market; prices in KRW; export brokers and importers are core users.
- Inspection reports and damage photos are high-value data, not just title/price.
- No public read API for third-party aggregators — agreed scheduled collection is required.
- Mobile app and desktop differ — pipeline must pick a canonical source or cover both.
- VivaCoding: legal review, KRW→USD/EUR normalization, dedup, export to ETL and auto catalog.
Encar platform overview
Korea’s used market is digital-first: Encar aggregates dealers and private sellers, shows service history where available, and Encar-certified inspection on many lots. Export brokers watch models with strong overseas demand (Hyundai Sonata, Kia Sportage, Genesis, popular EVs) by KRW price bands.
Encar targets domestic buyers, but export is a parallel industry: bidding, shipping quotes, KRW conversion. Scraping here means structured bundles — specs, inspection PDF/HTML, grade analogs, dealer contact rules (often redacted in public export) — not raw HTML copy.
Technically the site mixes server-rendered pages and dynamic endpoints; mobile traffic is significant. Anti-automation exists but is less aggressive than EU Akamai stacks — still, ToS and Korea’s PIPA personal-data rules apply.
KR export grew on weak KRW and CIS demand for young used Hyundai-Kia-Genesis stock. Typical broker workflow: morning digest of new lots on a model whitelist, inspection grade A/B filter, FOB Busan + freight calc. Manual monitoring of 200+ SKUs fails — scheduled scraping with Telegram alerts on >3% price drops closes the gap. VivaCoding often combines Encar adapters with EU sources in one ETL to compare KR import vs local EU stock.
Encar Performance Check and Encar Diagnosis are not marketing fluff: structured body/frame/engine scores drive overseas bids. Pipelines should store numeric scores, not PDF screenshots alone, to auto-filter grade C and below and skip wasted inspection spend.
Data fields we collect
| Field | Use case | Notes |
|---|---|---|
| car_id / encar_id | Dedup, deep link | Stable listing ID |
| make, model, trim (KR) | Catalog | Map to EN/RU taxonomy |
| price_krw | Export margin | FX snapshot at fetch |
| year, mileage_km | Customs, valuation | Korean odometer norms |
| fuel, displacement, transmission | Homologation abroad | EV battery SOH if listed |
| inspection_report | Trust / grading | Scores, damage map |
| photos[], damage_photos[] | Listing quality | CDN URLs, hash |
| dealer_name, region | Logistics | PII minimization |
| options[] | Trim compare | KR-only option codes |
| listed_at, status | Freshness | Sold = archive |
Technical challenges
Language and taxonomy. Makes and trims in Korean; without normalization, data won’t join EU/US catalogs. Trim dictionaries and optional MT with human QA for marketing copy.
Inspection reports. Some data lives in iframe/PDF or nested JSON — CSS selectors miss scores. We parse structured API responses where visible in network traces; store raw for audit.
No public read API. Encar does not offer OAuth feeds for third-party listings. Commercial Korean vendors exist — verify coverage and freshness for your model.
Export compliance. Separate market data from regulated customs/radiation documents in the pipeline.
Pipeline architecture
- Scope & legal — purpose (pricing vs full catalog), PIPA/GDPR if EU storage, robots/ToS.
- Discovery — seed URLs by model/price; mobile vs web pagination.
- Extract — listing JSON + inspection submodule.
- Translate & normalize — KRW, km, KR trim → global schema.
- Dedup & history — price drops, sold detection.
- Export — API to catalog, broker Telegram bot, Excel.
- Ops — monitoring, KR business-hours tuning.
Custom scraper vs third-party API
| Criteria | Custom (VivaCoding) | Commercial API / KR vendor |
|---|---|---|
| Inspection depth | Full report field control | Often basic specs only |
| Export workflow | Custom CRM, FX rules | Fixed schema |
| Freshness | Your cron (1–6 h) | Vendor SLA dependent |
| Cost | Build + infra | Per-car or subscription |
| Legal clarity | Documented at client | Opaque subprocessors |
| Schema changes | In-house patch | Vendor lag |
Third-party APIs are not the only answer — export houses with 500+ SKUs often prefer custom ETL for inspection fields and shipping CRM integration.
When this service fits
- Export broker KR → RU/CIS, UAE, Mongolia — monitor prices and grade by model.
- Overseas dealer selling “Korean import” — feed for automotive site.
- Analytics: spread between Encar ask and landed cost abroad.
- Multi-source data collection (Encar + EU portals).
When it does not fit
- Harvesting seller PII for cold outreach — we decline.
- Expecting live auction bid streams — Encar is classifieds, not auction API.
- One-time search for 10 cars — Encar UI is enough.
- Bypassing login-only dealer tools without contract — we decline.
Timeline and budget estimates
| Scope | Timeline | Budget from |
|---|---|---|
| MVP: specs + price, CSV, 5 model seeds | 2–4 weeks | €1,790 |
| + inspection reports, FX, dedup, EN labels | 5–7 weeks | €3,990 |
| Multi-source + shipping CRM, SLA | 8–10 weeks | €6,990+ |
Care: trim dictionary, layout monitoring — from €320/mo. Hub: web scraping.
Related services
- web scraping
- automotive websites
- data collection
- catalog website development
- website development
- contact
FAQ
Does Encar offer a read API for listings?
No public read API for aggregators. Dealers use internal publish tools. Market monitoring requires agreed collection or a data partner contract.
Can inspection reports be fetched automatically?
Yes for Encar Diagnosis lots — structured scores and damage flags. Optional PDF archive; primary storage is JSON in your DB.
How do you convert KRW to EUR/USD?
FX rate at fetch timestamp (ECB or xe API); store both currencies for margin reports.
Is scraping Encar from abroad legal?
Depends on purpose, ToS, PIPA/GDPR if stored in EU. Pre-start audit; no personal contacts without grounds.
Encar vs KB Cha Cha?
Encar has largest inventory and inspection narrative. KB Cha Cha is #2; add adapters in the same ETL.
WordPress catalog integration?
Yes — REST sync, custom inspection-grade fields, multilingual titles. See catalog development.
How often to refresh Encar data?
Export brokers: every 2–6 hours in KR business hours. Analytics-only: daily batch is enough.