MARKET DATA · IMPORT V1

Turn inventory into
market intelligence.

Email us vehicle, part, listing and sales data in one clear JSON format. We review and import the file internally. OE analyses and the economics of each donor vehicle can then be evaluated from the same reliable data foundation.

Send file by email Download format
01

THE DATA MODEL

Every part stays traceable.

5 OBJECTS / 1 CHAIN

An OE number, a physical part and a listing are not interchangeable identities. The target format keeps them separate and connects them through stable source IDs.

01

Donor vehicle

The specific vehicle with VIN, acquisition, mileage, condition and dismantling status.

VINVEHICLE IDCOST
02

Physical part

The actual saleable unit from one vehicle, with OE assignment, condition and inventory status.

OEPART IDCONDITION
03

Listing

One offer on one channel. Several listings can reference the same physical part.

ASK PRICECHANNELSTATUS
04

Event

Price and status changes remain available as a timeline instead of overwriting the previous state.

TIMEPRICEHISTORY
05

Sale

Sale price, line items, shipping, cancellation and return are assigned to the part unambiguously.

REVENUERETURNSELL-THROUGH
02

WHAT WE NEED

The baseline for clean analysis.

MINIMUM + VALUE

The more complete the statuses, timestamps and links, the more precisely demand, time to sale and revenue can be explained.

AreaRequired baselineAdditional analytical value
ExportExport ID, partner ID, mode, export timeCoverage plus location and channel scope
VehicleVehicle ID, VIN, location, statusAcquisition, dismantling, mileage, damage and costs
PartPart ID, vehicle ID, primary OE, conditionCategory, position, reference numbers and test status
ListingListing ID, part, channel, first and last priceStatus history, shipping, views and watchers
SaleSale ID, part, sale time, sale priceDiscount, fees, shipping, cancellation and return
03

ANALYSIS LEVELS

Three views, one data chain.

OE × VEHICLE × MARKET
OE LEVEL

OE market

Supply, ask price, sale price, sell-through and time to sale by exact or normalized OE number.

VEHICLE LEVEL

Vehicle yield

Parts yield, revenue, inventory duration and recycling costs for each VIN and specific donor vehicle.

CHANNEL LEVEL

Channel performance

Price and sell-through differences across marketplaces, shops, locations and periods, without double-counting inventory.

04

JSON CONTRACT

Machine-readable and verifiable.

SCHEMA 1.0.0

The JSON Schema defines required fields, data types, value ranges and allowed statuses. The guide adds domain rules and examples.

ABRIDGED STRUCTURE EXCERPT
{
  "schema_version": "1.0.0",
  "export": {
    "export_id": "exp-20260908-0001",
    "mode": "delta",
    "exported_at": "2026-09-08T08:00:00Z",
    "source": { "partner_id": "verwerter-001" }
  },
  "vehicles": [{ "source_vehicle_id": "veh-1042", "vin": "WVWZZZ1JZXW000001" }],
  "parts": [{
    "source_part_id": "part-9182",
    "source_vehicle_id": "veh-1042",
    "oe_numbers": [{ "raw": "5Q0 919 275 C", "relation": "primary" }]
  }],
  "listings": [],
  "listing_events": [],
  "listing_metrics": [],
  "sales": [],
  "tombstones": []
}

Core rules

  • ✓Stable source_*_id values for upserts instead of changing labels
  • ✓Money as an integer in the smallest currency unit, for example 5990 = EUR 59.90
  • ✓RFC 3339 timestamps; unknown optional values are omitted
  • ✓Exactly one primary OE number for each physical part
05

DOWNLOADS

Everything needed for implementation.

READY TO SHARE

Share the guide, schema and example directly with the software vendor or the person responsible for exports.

MD · 40 KB

Data contract

Domain rules, object model, status values and handover checklist.

Download guide JSON SCHEMA · 49 KB

Validation schema

Binding machine-readable structure using JSON Schema Draft 2020-12.

Download schema JSON · 15 KB

Complete example

Sample file containing a vehicle, parts, listings, events and a sale.

Download example ZIP · 23 KB

Complete package

Guide, schema and example in one ready-to-share package.

Download package
06

FROM EXPORT TO ANALYSIS

A controlled data flow.

4 STEPS
01

Map

Map source fields to the contract's IDs, timestamps, statuses and money fields.

02

Validate

Validate the export locally against the schema and domain reference rules.

04

Process internally

We review, import and combine accepted data at OE, vehicle, location and channel level.

READY FOR THE FIRST EXPORT?

Validate JSON.
Connect market data.

Download the handover package, create a conforming JSON file and email it to [email protected]. We will review and process the delivery internally.

Send file by email Download complete package