Dealerships
For dealerships
A showroom of Korean and Chinese cars that fills itself.
- Catalog and search with no manual listing entry
- The landed price with shipping and taxes
- Vehicle pages with photos, specs, and history
Use cases
How MotorFeed is used in real work
The data is the same; the scenarios are not. One team needs a storefront, another needs a budget the customer can trust, a third needs listings flowing into a CRM. Below is the breakdown by role and by the methods that cover it.
Import
For car importers
Sourcing against a customer request and a transparent budget — from purchase to registration.
- Compare by the landed total, not the listing price
- Your own shipping tariffs and rates in the calculation
- The condition of a car before the deposit
Engineering
For developers and integrators
A finished data source for a website, a CRM, or a client's mobile app.
- Swagger UI and OpenAPI instead of reverse-engineering a source
- Stable ids and one shared schema
- Two markets in one contract — Korea and China
Sales
For an internal sourcing tool
A manager dashboard that shows the options, the customer price, and the condition at once.
- Search through clear filters instead of a wall of marketplace tabs
- Landed cost for the customer's country in one request
- Vehicle pages and reports in the same interface
In common
The path is the same in every scenario
Only what you render changes: a public storefront, a manager dashboard, or a vehicle card inside a CRM.
Key and access
An account, an API key, and the trusted IP or domain of your service. Request usage is visible in your account.
Filters from the catalog
Brands, models, generations, and trims come from the reference endpoints, which never spend the request package.
Results and vehicle page
Search returns the list with photos and parameters; the vehicle endpoint returns everything about one car.
Price for the customer
country, currency, and your rates add a line-by-line breakdown of shipping, duties, and fees to the response.
Integration example
From an Encar API request to a car on your website
A short worked example: your website requests Hyundai cars from 2020 onwards with up to 80,000 km, then displays the response in a vehicle card.
The data is fictional and for illustration only. This is a shortened response, not a live listing.
1. Request vehicles
POST /search
{
"providerId": 1,
"sort": "newest",
"limit": 1,
"filters": {
"saleOnly": true,
"brandId": "002",
"year": { "min": 2020 },
"mileage": { "max": 80000 }
}
}2. Receive structured data
{
"items": [
{
"id": "encar_12345678",
"title": "Hyundai Avante",
"formYear": "2021",
"mileage": 42000,
"price": 1690
}
]
}3. Show the car to your customer
Hyundai Avante, 2021
42,000 km · KRW 16,900,000
The name, year and mileage arrive as separate fields. Encar expresses price in units of 10,000 won: 1690 × 10,000 = KRW 16,900,000. Your website uses these fields in its existing vehicle card. Shipping and tax estimates can be requested using country and currency.
For integration details and plans:
Scenario not listed?
Describe it on Telegram: which sources you need, which country the price should be calculated for, and where the data goes — a website, a CRM, a manager dashboard, or an internal service.