DriveQuant services evaluate driver behaviour and the impact of driving style on the vehicle. The data returned to drivers are mostly driver scores. Vehicle data include the total distance and the evolution of tire and brake wear.
A set of services allow to manage your fleet. In this section, you will find information to answer the following questions:
How to create a new vehicle?
How to set or to initialize distances and wear levels for tires and brakes?
How to set the vehicle distance?
How to retrieve the vehicle’s main statistics?
POST
https://service.drivequant.com/v3/drivekit/admin/vehicle
Create a new vehicle belonging to your organisation.
0
Success
1
Invalid characteristics
2
The vehicle unique identifier already exists
3
4
Beacon already used
For each vehicle in your fleet, you can access to technical characteristics set when you create a vehicle or retrieved in DriveQuant vehicle database:
Brand, model and version of the vehicle
Engine configuration
Consumption data
Gearbox configuration
Vehicle dimensions
Tyre dimensions
GET
https://service.drivequant.com/v3/drivekit/admin/vehicles/{vehicleId}/characteristics
Retrieve vehicle characteristics using the vehicle unique identifier.
vehicleId*
string
Vehicle unique identifier
DriveKit-Admin-API-Key*
string
Admin API Key
Description of each vehicle characteristics is available here.
Loading...
Loading...
Once a vehicle is declared, the distances of all trips are aggregated to calculate the total analyzed distance.
If the vehicle has already been driven before it has been registered on the platform, there will be an offset between the vehicle odometer and the total analyzed distance (computed by DriveQuant services).
If you find an offset between the vehicle's odometer and the total analyzed distance, you can set vehicle mileage.
The vehicle mileage value is updated :
Every time a trip is analyzed.
Each time the odometer update API is used.
PUT
https://service.drivequant.com/v3/drivekit/admin/vehicles/{vehicleId}/distance
Update the vehicle mileage unsing the vehicle unique identifier.
vehicleId
string
Vehicle unique identifier
DriveKit-Admin-API-Key
string
Admin API Key
distance
number
Vehicle odometer reading in kilometer
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.
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.
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
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
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: