Sale events
Vehicles sold at auction and through the trade, with sale price, mileage and condition, published daily.
The sale events feed is a daily record of vehicles sold at auction and through the trade. Each row is one sale: which vehicle, where and when it sold, and for how much. It is the bulk counterpart to the sale data behind the valuations API.
Cadence and file
- Published: daily, overnight.
- Coverage: a full snapshot of the recent sale-events window as at the build date.
- File name:
sale-events_YYYY-MM-DD.jsonl(or.csv). - Formats: JSONL or CSV. See File formats.
Fields
Each row carries a cazanaId but no specification columns. Join cazanaId to the codebook for the full vehicle specification (make, model, derivative, body style, engine and so on).
| Field | Type | Notes |
|---|---|---|
saleId | string | Unique identifier for the sale event. |
saleDate | date | Date the vehicle sold (YYYY-MM-DD). |
vrm | string | Registration mark, where known. |
vin | string | Vehicle identification number, where known. |
cazanaId | integer | Cazana ID for the vehicle. Join to the codebook for its specification. |
mileage | integer | Recorded mileage at sale. |
saleChannel | string | Auction or trade. |
source | string | Auction house or sale source. |
salePrice | integer | Sale price in pounds (GBP). |
conditionGrade | string | Condition grade, where supplied by the source. |
Notes
- Prices are in pounds (GBP), as whole numbers.
- Each daily file is a complete snapshot of the current window. The same
saleIdis stable across files, so you can match a sale from one day to the next. - A vehicle can appear more than once if it sells more than once; each sale has its own
saleId. - The vehicle's specification is never repeated on a sale row. Resolve it from the codebook using
cazanaId.