Skip to main content
GET
Vehicle info (V2)

Overview

Returns decoded vehicle information for a single vehicle, looked up by IMEI, vehicle ID, or VIN. Exactly one of the three query parameters must be supplied; otherwise the call returns 422. The response is a flat list of { label, value } pairs, so all available fields are returned without a fixed schema. Common fields include make, model, engine specs, body dimensions, and manufacturer details. This is a new V2-only endpoint with no V1 equivalent.
Rate limit: 144,000 req/s · 60/min · 144,000/hr · 144,000/day — in practice 60 requests per minute per API key

Endpoint

GET /v2/api/vehicles/info

Query parameters

Exactly one of the following must be provided:
string
Tracker IMEI, matched exactly (trimmed). The lookup is not limited to your companies: if more than one vehicle carries this IMEI, one is picked arbitrarily, and the call returns 404 if that vehicle is not one of yours or has no public ID.
integer
Public vehicle ID (deviceId).
string
Vehicle Identification Number, matched trimmed and case-insensitively among your companies’ vehicles. If several share the VIN, an arbitrary one is returned.

Response

200 OK — VinDecodeItemDto[] A flat list of label/value pairs. The set of labels returned depends on what has been decoded for the vehicle. The response is [] (an empty array) when the VIN has not been decoded; nothing from the vehicle record appears then either. When a decode exists, these labels are taken from the vehicle record whenever the record has a value: Make, Model, Model Year, Body Type, Fuel Type, Transmission, Engine Size, Number of Doors, Colour, Fuel Capacity, Battery Capacity, Number Plate, Registration State, Registration Country. Each one replaces a decoded value with the same label, or is appended. Fuel Type, Body Type and Transmission are identifiers such as Petrol, Diesel, HybridElectric, Suv, PickupTruck, Auto or Manual. Because Fuel Type comes from the vehicle record, it can disagree with a decoded label such as Fuel Type - Primary.

Common labels

The set of labels returned depends on what has been decoded for that VIN. Below are labels observed from actual API responses, plus the vehicle-record labels listed above (Body Type, Engine Size and Number Plate rows are illustrative):
Not all labels will be present for every vehicle — availability depends on what data is on record for that VIN.

Example response

Error responses

Authorizations

Authorization
string
header
required

JWT Bearer token obtained from POST /v2/api/authentication/token/api-key.

Lifetime: ~24 hours (86,399 seconds). Cache the token and reuse it. Re-authenticate 5 minutes before expiry.

Scoping: API key tokens are scoped by the key's company and its action set; see Token scoping.

No refresh endpoint — re-authenticate with your API key when the token expires.

Query Parameters

imei
string
id
integer
vin
string

Response

Successful response

label
string

Field name (e.g. "Make", "Model Year", "Engine Power (kW)")

value
string

Field value (always a string, even for numeric or array values)