Tire and brake wear update
Last updated
Last updated
The tire and brake wear estimator returns the level of wear expressed in percent and the autonomy in kilometer.
It is possible to update the distance and the wear percentage based on observations made by a mechanic or during a technical inspection or a maintenance intervention on the vehicle.
In the case of a replacement, the distance and the wear must be set back to 0 km and 0% for the new component.
If you have your admin API key, you can try the API via this .
PUT
https://service.drivequant.com/v3/drivekit/admin/vehicles/{vehicleId}/wear
Update the front/rear tire and brake wear values using the vehicle unique identifier.
The date of the recalibration is equal to the date of the request.
The parameters wear and distance are mandatory.
A component replacement is declared with wearPct = 0 % and declaredDistance = 0 km.
If the component is replaced, all synthesis data will be reset automatically.
It is not possible to reset the front and rear axle components at the same time. It is necessary to make two separated requests.
To declare that the front tires of the vehicle have a wear level of 40% after 14,000 km, the body of the request is as follows:
To declare that the rear brakes of the vehicle have just been changed, the body of the request must be as shown below:
component
int
Component considered for the update:
(1) Tires
(2) Brakes
drive
int
Drivetrain considered for the update:
(1) Front drive
(2) Rear drive
wear
double
Level of wear observed for the considered component.
This value is in percent (min. = 0% / max. = 100%)
distance
double
Distance traveled with the component in kilometer
min. = 0 km / max. = 300 000 km
vehicleId
string
Vehicle unique identifier
DriveKit-Admin-API-Key
string
Admin API Key
component
integer
Component to update
drive
integer
Drivetrain of the component
wear
number
Level of wear in %
distance
number
Component distance in kilometer