2026-09-03: Launched VRM service v3

This version introduces the KType+ data set. Where v1 and v2 returned a single value for attributes that a vehicle can legitimately have several of, v3 returns the complete list, and the response has been reorganized so that each attribute is published where it actually belongs. For this reason v3 is not backwards compatible with v2 and the changes described below require a client update.

Power output is now a list. The attribute powerKW has been replaced by powerOutputs, an array in which every entry carries its own type, fuel type and value in kW, so a vehicle can expose its system power, its combustion power and its maximum electric power separately. The attribute powerHP is still returned as before.

Gearboxes are now a list as well. The single gearbox object has been replaced by gearboxes, which returns the gearbox options available for the vehicle filtered as much as possible, adding key information as the gearbox number, identifier and mounting position. The attribute numberOfGears has been renamed to numberOfSpeeds. The value previously returned as gearbox.transmission does not describe the gearbox and is now returned as engines.timingSystem. For consistency with the rest of the response, the engine array has been renamed to engines.

Electric information has moved into a new energySystem object. The individual packs are returned in energySystem.batteries, while the charging, autonomy and consumption values, which describe the vehicle and not one specific pack, are now returned once at energySystem level instead of being repeated on every entry of the old battery array. The attribute names have not changed, only their position in the response.

Some attributes have moved to vehicleInformation, where they describe the vehicle rather than one of its engines: adBlue and the complete environmental object, which in addition now returns the CO2 emission range through the attributes CO2From and CO2To. New KType+ attributes are also available in vehicleInformation: aircon, SCR, maxWeight and EUClass.

Finally, the behaviour of the lookup has changed when no vehicle can be returned. If neither a KType or NType mapping nor ministry raw information is available, v3 responds with 404 Vehicle not found, while v1 and v2 responded with 200 and an empty vehicles list.

2026-06-17: Launched VIN service

The Vehicle Identification Service now also identifies vehicles from their VIN. The new endpoint /api/v1/vin/:country/:vin decodes a 17 character VIN and returns the TecDoc vehicles it corresponds to, each one with its KType for passenger cars or its NType for commercial vehicles, together with the detailed vehicle, engine, gearbox, brakes, tyres, fluids and axle information loaded from TecDoc. The response follows the same structure you already know from the VRM service.

Keep in mind that a VIN does not always identify one single vehicle version. When several TecDoc vehicles match the VIN, all of them are returned in the vehicles list. To help narrow the result down you can send any of the optional parameters make, model, dateFirstReg, body, doors, fuel, gearboxType, gearboxCode, cc, kw and engineCode. This information will help the VIN decoder identify the right vehicle.

Unlike the VRM service, the VIN service does not return raw registration information: a vehicle is only returned when it can be mapped to a KType or an NType. When the VIN is unknown to the service, or when none of the results can be mapped, the response is 404 Vehicle not found.

The complete list of attributes returned and the technical documentation are available in the VIN menu on the left.

2026-04-27: Launched VRM service v2

Compared to v1, in this new version when a mapping to KType/NType is not possible and ministry raw information is available (make, model, year, VIN, ...), the service will return this raw information using the standard service response model. You will immediately notice this case because there won't be any value returned for the attributes ktype/ntype.

Use this version when you want to use the raw data information to identify the vehicle when a direct KType/NType mapping hasn't been possible. There have not been changes in the data model besides making all attributes optional to allow returning the ministry raw information.