Skip to main content

Parts Interpretation API

The Parts Interpretation API allows you to preload vehicle information by submitting a vehicle identifier (like a VIN or license plate) before a user requests it. This queues a job within Partly to fetch, translate, and cache all relevant data for that vehicle.


Why Preload Vehicle Data?

Preloading vehicle data via the Tier1 API allows for significantly faster response times in Partly frontend applications (e.g., the Repair App or Workshop App), which improves the user experience.


Preparing Vehicles

To initiate a preload, you send a POST request to the /api/2026-01/tier1.prepare endpoint. The body of the request defines the vehicles to load and the parameters for the job. This endpoint supports bulk requests of up to 100 vehicles at once.

tier1.prepare

Queue up a given vehicle VIN for future use in other Partly services.

header Parameters
authorization
required
string (std.string.String)

UTF-8 encoded string

partly-integration-id
required
string <uuid> (uuid.Uuid)

UUID value type

Request Body schema: application/json
required
required
Array of ChassisNumber (object) or integrations_server.service.tier1.v1.model.LocationV1 (object) (integrations_server.service.tier1.v1.model.VehicleIdentifierV1)

An array of vehicle identifiers to preload. Each identifier object must conform to one of the two structures detailed below (Chassis Number or VRM). Must contain between 1 and 100 identifiers. VRM (License Plate) is recommended over Chassis Number as a VRM lookup often yields better data quality and allows us to disambiguate possible vehicle variants (e.g. trim or color options) more effectively.

Responses

Request samples

Content type
application/json
{
  • "identifiers": [
    ]
}

Response samples

Content type
application/json
{ }