For dealerships

A car catalog on your website, filled without manual work

A dealership site is worth exactly as much as its catalog is fresh. MotorFeed delivers listings, photos, specs, and the landed price through an API: the storefront updates itself, and managers spend their day on customers instead of copying cards.

storefront request

JSON
POST /search
{
  "lang": "ru-MD",
  "country": "MD",
  "currency": "EUR",
  "logisticsTariff": {
    "basis": "price",
    "priceCurrency": "KRW",
    "tiers": [
      { "maxPrice": 16000000, "costUsd": 4900 },
      { "minPrice": 16000000, "costUsd": 4400 }
    ]
  },
  "filters": {
    "saleOnly": true,
    "brandId": "001",
    "year": { "min": 2020 },
    "mileage": { "max": 100000 }
  },
  "sort": "newest",
  "limit": 20
}

Three problems

What breaks while a catalog is filled by hand

Three reasons a dealership site usually lags behind reality — and what the API does about each of them.

Content

A manager copies listings by hand

MotorFeed syncs them: listings, photos, specs, and options arrive through the API. There is nothing left to retype — the catalog is not a week behind, it carries no copy-paste typos, and sold cars do not linger on the storefront.

Price

The customer sees the price in Korea

MotorFeed shows the landed price with shipping and taxes. The calculation for Moldova, Russia, Ukraine, or the UAE arrives line by line: shipping, duty, excise, VAT, and fees — in the customer's currency and with your tariffs. The budget is clear on the first screen, not after the third email.

Engineering

The developer has to reverse-engineer Encar

They get a proper API: documented methods, stable ids, and localized values instead of the source's internal formats. Swagger UI and OpenAPI are open — the integration can start the same day.

How the storefront works

Four steps from an empty site to a working catalog

The same order works for Korea and for China: the source is a parameter, not a second integration.

01

Filters

Build the cascade of brands, models, generations, and trims. Reference endpoints are cached and never spend the request package.

GET /catalog/...

02

Results

Show the listings with photos, year, mileage, and price. Sold cars are dropped by the saleOnly filter.

POST /search

03

Vehicle page

Open a car with its specs, options, gallery, insurance history, and inspection report.

GET /vehicles/:id

04

Price

Add the landed cost for the customer's country to both the vehicle page and the results, so the price filter works on the total.

?country=MD&currency=EUR

Outcome

What changes for each side

One integration settles three conversations that normally run in parallel: with the customer, with sales, and with engineering.

The customer

Sees current listings, the landed price in their own currency, photos, and the condition of the car — instead of a contact form and last year's selection.

The manager

Retypes nothing, answers the price question immediately with the breakdown on screen, and reads the history and inspection before the call.

The developer

Works with documented methods and a stable response schema, verifies everything in Swagger UI before building the UI, and does not repair a parser after every upstream change.

The website

The catalog refreshes without manual work, sold cars leave the results, and pages fill up with the data people actually search for.

Ready to launch the catalog on your dealership site?

Create an account and get a key, or message us on Telegram — we will point out which methods cover your storefront and how many requests it will use.