Documentation
EnCarAPI documentation. Learn how to access Korean car data via direct API endpoints. Integration guides and code examples.
Industry Experience
Automotive data API provider with years of experience in the Korean market.
7-Day Support
Support team available 7 days a week for API integration help.
24/7 Service
Round-the-clock monitoring for reliable data delivery.
Real-Time Listing Alerts
Get instant API access to new car listings as they're posted.
CSV downloads
Download make, model and badge lists as CSV - cache them and skip live facet calls.
Flexible Export Formats
Get data in CSV, JSON, Excel, and custom formats for easy integration.
Base URL
All API requests are made to the following base URL:
https://api.encarapi.comFor example, to fetch offers:
GET https://api.encarapi.com/api/catalog?manufacturer=bmw&fuel=diesel&lang=en&count=trueAuthentication
Authenticate your requests using an API key. Pass it as a query parameter or via the Authorization header.
# Send your API key in the x-api-key header (recommended):
curl -H "x-api-key: YOUR_API_KEY" \
"https://api.encarapi.com/api/catalog?manufacturer=bmw&fuel=diesel&lang=en&count=true"
# The api_key query parameter also works:
GET https://api.encarapi.com/api/catalog?manufacturer=bmw&fuel=diesel&lang=en&count=true&api_key=YOUR_API_KEYIntegration Workflow
Follow these four steps to integrate with the EnCarAPI.
Get Available Filters
Retrieve all possible filter values (marks, models, configurations, colors, etc.)
GET /filtersGet Vehicle Listings
Fetch paginated listings with optional filters for make, model, year, price, and more.
GET /offers?page=1Track Changes
Get a change ID for a date, then poll for added, changed, and removed listings.
GET /change_id β GET /changesGet Listing Details
Fetch full details for a specific listing by its inner_id.
GET /offer?inner_id=...API Endpoints
All available endpoints for accessing Korean vehicle data.
Dropdown data (CSV)
Download the make, model and badge lists as CSV, cache them, and build your dropdowns from them - no per-click facet calls and no offline mapping. Each file includes a count column, and the badge file carries the body-style split (Coupe / Sedan / Cabrio).
Download once, cache it - Updated daily
All makes with listing counts
All make and model combinations with counts
All make, model and badge values (incl. Coupe / Sedan / Cabrio) with counts
Add your API key to download - append ?api_key=YOUR_KEY to any file URL. The files are key-protected, so nobody can download them without a valid key.
Data freshness
The catalog (prices, mileage, new and sold listings) is refreshed roughly every 5 hours, with one deeper daily pass. Vehicle detail (specs, photos, condition, accident report) follows its own slower cycle - typically within 3 weeks of a change, sooner if the catalog signals something relevant changed.
Catalog scope
GET /api/catalog covers standard-sale listings only (Encar's βμΌλ°β sell type). Lease-takeover (β리μ€β) and rental (βλ νΈβ) listings are not mixed in - they price by monthly payment rather than a purchase price, which would distort the Price field. Use GET /api/catalog/leasing for those instead.
How long to cache
- Filter values, taxonomy CSVs and /api/nav: cache for 24 hours
- Vehicle listings (/api/catalog): cache for 4 to 6 hours
- Vehicle details (/api/vehicle/:id): cache for 24 hours
This is the Starter model: serve listings from your own database and refresh on this cadence rather than calling live on every user click. There is a daily catalog volume cap on this plan - it is meant for live queries, not for holding a full local copy.
Need a full local copy instead?
Business and Scale plans include GET /api/catalog/export (a full daily CSV snapshot that does not count against the daily cap) and GET /api/catalog/changes?since=... (added, updated, reappeared and removed listings since your last sync). Seed your database from the export once, then poll changes to keep it current - no more re-pulling the whole catalog. Scale also removes the daily catalog volume cap entirely.
Duplicate listings
Korean dealers commonly list the same physical car twice under different listing IDs for extra visibility - same price, mileage, model year and model/badge. We detect these and flag the extra copies with IsDuplicate: true and DuplicateOf: <listing ID of the original> on the catalog item; the original listing is left unflagged. Duplicates are flagged, not removed, so you decide how to treat them - pass exclude_duplicates=true to /api/catalog or /api/catalog/leasing to filter them out server-side.
Frequently Asked Questions
Ready to Get Started?
Contact us on Telegram to get your API credentials and start accessing Korean car data today.