Stock feed template
A DealerToolkit stock feed is a public JSON or CSV link listing every vehicle a seller has for sale. Each vehicle needs a stable id, make, model, year, price, mileage and photo links. Fuel, gearbox, body type, colour and description are optional but recommended. Vehicles missing from the feed are treated as sold.
Fields
| Field | Needed | Type | Notes |
|---|---|---|---|
id | Required | text | Unique and never changes for the same vehicle (stock number, registration or UUID). |
make | Required | text | Manufacturer, e.g. "Skoda". Accents are not needed. |
model | Required | text | e.g. "Octavia". |
year | Required | number | Year of manufacture or first registration. |
price | Required | number | Whole pounds, digits only. |
images | Required | list of URLs | Public https links, best first. Up to 20 are used. |
mileage | Required for cars and vans | number | Miles, digits only. |
variant | Optional | text | Trim or derivative, e.g. "2.0 TDI 150 SE L 5dr DSG". |
vehicle_type | Optional | text | car, van, motorcycle, motorhome, caravan or other. Default car. |
status | Optional | text | available, reserved or sold. |
fuel_type | Optional | text | Free text, e.g. "Petrol/Electric Hybrid". |
transmission | Optional | text | Free text, e.g. "Manual", "DSG". |
body_type | Optional | text | Free text, e.g. "Estate", "SUV". |
colour | Optional | text | Free text, e.g. "Smokey Silver Metallic". |
interior_colour | Optional | text | |
condition | Optional | text | Excellent, Very good, Good, Fair or Poor. |
doors | Optional | number | |
seats | Optional | number | |
engine_size_cc | Optional | number | e.g. 1968, shown as 2.0L. |
registration | Optional | text | Only shown if the seller chooses to. |
previous_owners | Optional | number | |
mot_expiry | Optional | date | YYYY-MM-DD. |
description | Optional | text | Line breaks allowed. |
features | Optional | list of text | e.g. ["Heated seats", "Apple CarPlay"]. |
url | Optional | URL | The vehicle’s page on the seller’s website. |
updated_at | Optional | date-time | ISO 8601. |
Unknown extra fields are ignored. Free-text values are mapped to Facebook’s options by DealerToolkit.
JSON example
{
"version": 1,
"vehicles": [
{
"id": "AB26CDE",
"make": "Skoda",
"model": "Octavia",
"variant": "2.0 TDI 150 SE L 5dr DSG",
"year": 2026,
"mileage": 5681,
"price": 30395,
"fuel_type": "Diesel",
"transmission": "Automatic",
"body_type": "Estate",
"colour": "Smokey Silver Metallic",
"images": [
"https://example.com/photos/1.jpg",
"https://example.com/photos/2.jpg"
]
}
]
}CSV example
Use the field names as the header row. Separate list values (images, features) with |.
id,make,model,variant,year,mileage,price,fuel_type,transmission,images
AB26CDE,Skoda,Octavia,2.0 TDI 150 SE L,2026,5681,30395,Diesel,Automatic,https://example.com/1.jpg|https://example.com/2.jpgAlternative column names
Many existing portal feeds work as they are, because these names are also understood: stock_id for id, price_gbp for price, image_urls or photos for images, fuel for fuel_type, gearbox for transmission, body_style for body_type, color for colour, odometerfor mileage, reg or vrm for registration, and derivative or trim for variant.
Hosting rules
- The link must work without logging in. A long secret token in the address is fine.
- Return every vehicle currently for sale in every response.
- Keep each vehicle’s
idthe same for as long as it is in stock. - Photo links must be public
httpsaddresses.
Questions from providers
Email support@dealerpricing.co.uk and we will help you test your feed. See also the provider guide.