Introduction

DriveQuant offers a range of services designed to integrate the data collected by our telematics solution directly into your platform. This data can be used to analyze your drivers behavior, manage your claims and diagnose the performance of your DriveKit SDK-enabled mobile application.

We provide the following services to transfer key data to your platform or data lake:

1. The push trip data includes raw data recorded by the phone's sensors, driving behavior indicators and multiple trip statistics. This data is shared automatically after each completed trip. This data enables driving pattern analysis, driver behavior feedback, safety scoring, and insights generation for fleet management, insurance telematics, or mobility services applications.

2. The push deleted trip declares that a trip has been deleted on the DriveQuant platform, and informs you to replicate this deletion if the trip had also been saved on your platform. This notification is sent immediately when a deletion action occurs. This data ensures consistency and compliance across systems when users delete trips for privacy or data accuracy reasons.

3. The push diagnosis data includes information on the configuration and status of the phone on which a mobile application integrating the DriveKit SDK is installed. This data is shared periodically or when significant configuration changes are detected on the device. These data help to monitor SDK integration health, troubleshoot recording issues, ensure optimal sensor configuration, and provide technical support.

4. The push crash data includes accident data detected by the DriveKit SDK. This data is shared immediately after an accident occurs - typically in less than 30 seconds following the shock detection. These crash notifications are primarily used to provide rapid assistance to drivers, enabling emergency response services or roadside assistance to be dispatched quickly.

5. The push crash report data provide detailed and contextual information that is useful for claims management and accident investigation. Unlike the push crash, this data is delivered only after the trip during which the accident occurred has been completed. This report is generated using data from both the trip where the accident happened and the preceding trip.

6. The push deleted driver declares that a driver has been deleted on the DriveQuant platform, and informs you to replicate this deletion if the driver had also been saved on your platform. This notification is sent immediately when a deletion action occurs. This data ensures consistency and compliance across systems when users delete driver profiles for privacy, GDPR compliance, or data accuracy reasons.

Configuration

Each push service will send the data as a POST request to a specific URL on your platform. The body of the request is a json object, whose content is described in each individual section.

You will need to provide your service URL to DriveQuant in order to set up and activate the push services.

Http response code

Your service should respond with a 2xx http status code (typically 200 OK) when the push request is accepted. Any other code will be considered as a failure, and the service will attempt to send the data again as defined in the Retry Policy section.

If your service responds with a 2xx http status code, while the data has not been accepted by your platform, then there will be no further attempt to send the data!

Security & TLS

The data sent over the push services may include driver’s private information (location, username, email...) and authentication data. For this reason, the provided URL must be using TLS (> 1.2) protocol (HTTPS).

Authentication & Authorization

The service must be authenticated using oauth2 (our recommended and preferred solution), or alternatively basic auth.

The authentication is shared between all the push services.

Recommended solution (OAuth 2.0)

The OAuth 2.0 configuration requires an additional endpoint, which will be used to retrieve an authorization token. This endpoint must be secured with Basic Auth. For the configuration of the push service, you will be required to provide the following information:

• url: URL used to generate bearer token.

• clientId: client id used in basic authentication.

• clientSecret: client secret used in basic authentication.

Additionally, specific headers or query parameters can be provided, if the OAuth2 endpoint requires it:

• headers: Headers added to the request.

• params: Parameters added to the request.

The token will be renewed if the push data service returns an http status code 401 or 403, depending on the endpoint configuration.

Alternative (Basic Auth)

The Basic Authentication is a simple authentication scheme but less secure than the OAuth 2.0 protocol. For the configuration of the push service, you will be required to provide valid credentials (username and password) for your service.

Retry Policy

DriveQuant will attempt to resend the push data if an HTTP error occurs during the initial attempt.

Each service has its own retry policy; please refer to the respective section for details.