Sources & site slugs

A site slug identifies which auction source a listing came from. It is the value you pass to /api/search?site=, the first path segment of /api/auction/{site}/{id}, the site parameter of /api/car-details, and the site_name fee-model selector on the import calculator.

eCarsTrade

eCarsTrade behaves like every other source — there is no special code path and no separate endpoint. It is a valid value everywhere a source is accepted:

GET  /api/search?site=ecarstrade
GET  /api/auction/ecarstrade/{auction_id}
GET  /api/auction/ecarstrade/{auction_id}/price-history
GET  /api/auction-images/ecarstrade/{auction_id}
GET  /api/car-details?site=ecarstrade&id={id}
POST /api/calculator/calculate   { "site_name": "ecarstrade" }

The one source-specific detail worth knowing: an eCarsTrade gallery arrives under the ImageUrls key of car_identification on the auction detail payload. You do not normally need it — /api/auction-images/ecarstrade/{id} returns the same gallery already ordered, vaulted and CDN-served with served_url, width and height, and the identical body rides on the detail response as vault_gallery. Reach for the raw key only when you want exactly what the source published.

Japanese auctions

Japanese export inventory pooled from the major domestic auction houses — USS, ARAI, AUCNET, BAYAUC and CAA — addressed by the slug japanauction, which is a valid value everywhere a source is accepted. Two things differ from the EU sources: its listings carry the JP origin country, and /api/car-details?site=japanauction takes the offer id/UUID rather than the numeric auction id — the same as auto1. It publishes less detail than the three EU auction houses, so expect vehicle_details to be sparse or absent.

Not a source: the European classifieds network

The classifieds network is retail market-reference data, not auction inventory: 9,808,689 live listings gathered from 681 origin portals across 39 European countries. It is stored in its own tables, is never merged into the auction feed, and is deliberately a light dataset — no detail fetch, no image vault, no per-listing detail payload. It therefore never appears in /api/sites and is not a valid site value; passing it returns 400. Query it through its own /api/theparking/* endpoints under the theparking scope — that slug is the scope name, not a source name.