Korea
Encar
Korea's largest used-car marketplace, with the full depth of listing data.
- A five-level catalog and filtered search
- Vehicle pages with specs, VIN, and photos
- Insurance history and inspection report
Features
One API contract instead of a parser per source
MotorFeed is not a parser for one website — it is the layer between listing sources and your product. Korea and China are served by the same methods, so the integration is written once and adding a market never becomes a second project.
China
CHE168
The Chinese market in the same contract: only providerId changes in the request.
- A catalog of brands, series, and modifications by year
- Vehicle pages with specs, photos, and dealer data
- Listing price converted out of yuan
Need a source that is not on the list yet? Tell us — we add markets to fit a client's case, and the response contract stays the same when we do.
Platform
What MotorFeed handles while you build the product
Everything below works the same way for every connected source — which is the difference between an API and a parser.
Sources
Encar and CHE168 in one contract
Korea and China are served by the same methods. The source is chosen with providerId, not with a separate integration and a second client in your codebase.
Data model
A shared schema instead of raw payloads
Brand, model, generation, and modification resolve into one catalog, and ids are prefixed — encar_42247740 and che168_58234901. Same fields, same sort keys.
Localization
Values in the customer's language
The lang parameter returns names, color, fuel, and transmission in ru-MD, ro-MD, en-US, or the source language. Korean and Chinese dictionary values never have to be translated on your side.
Pricing
Landed cost per market
country, currency, and your rates produce a line-by-line total: shipping, duty, excise, VAT, and fees for Moldova, Russia, Ukraine, and the UAE. Your own tariffs and known values replace the estimates.
Media
Photos with ready-made links
A thumbnail, a cover frame, and full size for every photo, identically for both sources. No files to store and no URLs to assemble by hand.
Condition
History and inspection where they exist
Where the source publishes it, you get the insurance record, the inspection report with body zones on the damage drawing, and the ownership history.
Operations
We keep the parsers running
Proxies, request signing, retries, caching, and source monitoring are on our side. When a source changes its markup or signing rules, we fix it and your response format stays the same.
Access
Keys, limits, and usage
x-api-key, trusted IPs, and rate limits, with predictable 401, 402, 403, and 429 responses. Keys, domains, and usage statistics live in your account.
Documentation
Swagger UI and OpenAPI
Methods, parameters, and response codes are in the schema, so a developer starts the integration alone — no email thread, no examples on request.
Comparison
Your own parser or MotorFeed
The question is not whether you could collect the data yourself — it is who lives with that code afterwards.
| What is compared | Your own parser | MotorFeed |
|---|---|---|
| Launch | Weeks spent on the source, proxies, and value dictionaries. | A key and a first working request the same day. |
| The source changes | The integration breaks and your team fixes it, at the moment it happens. | We fix it, and your response contract does not change. |
| A second market | A second project from scratch: another format, another auth, another dictionary. | providerId in the same request. |
| Languages | Korean and Chinese values arrive as they are. | lang returns finished values in the interface language. |
| Landed cost | Your own table of duties, excise, and fees — and its upkeep. | MD, RU, UA, and AE calculated line by line with your tariffs and rates. |
| Images | Assemble upstream URLs and store the files yourself. | Three ready-made links per photo. |
| Access and metering | Your own auth, limits, and request accounting. | Keys, trusted IPs, limits, and usage in the account. |
| Documentation | Lives in the head of whoever wrote the parser. | Swagger UI and a machine-readable OpenAPI schema. |
Impact
What changes in day-to-day work
Managers find cars faster, developers get a clear API, and the customer sees a price that accounts for their region.
Less manual entry
Listings, photos, parameters, and the landed cost arrive through the API instead of being copied by a manager.
A faster storefront launch
Catalog, search, and the vehicle page cover the main path a visitor takes on the site.
A new market without a new project
Adding China to Korea is a parameter in the request, not a second development cycle.
Predictable maintenance
Changes on the source side stay our problem instead of becoming an emergency for your team.
Ready to connect automotive data to your product?
Message us on Telegram with the sources and the pricing country you need, and where the data will be used: a website, a CRM, a manager dashboard, or an internal tool.