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 driver behavior, manage claims and diagnose the performance of your DriveKit SDK-enabled mobile application.

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

1. The push trip data, which includes raw data recorded by the phone's sensors, driving behavior indicators and multiple trip statistics.

2. The push deleted trip, which 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.

3. The push crash data, which includes accident data detected by the DriveKit SDK, and is generally used for assistance or claims management.

4. The push diagnosis data, which includes data on the configuration and status of the phone on which a mobile application integrating the DriveKit SDK is installed.

Configuration

Each push service will send data to a specific URL on your platform. The URL must be provided to DriveQuant in order to set up and activate the push services.

It is mandatory to configure the HTTP response code. If the request to your service is accepted, we expect a http status code 200 (OK). Any other code will be considered as a failure, and the service may attempt to send the data again as defined in the Automatic retry section.

If the service returns a 200 HTTP code while the data has not been accepted by your platform, then there will be no further attempt to send the data.

Security

The data sent over the push services may include driver’s private information (location, username, email...). For this reason, the two following security measures are mandatory:

• The provided URL must be using TLS (> 1.2) protocol (HTTPS).

• The service must be authenticated using OAuth2 (our recommended and preferred solution) or Basic Auth

The OAuth2 configuration is shared between all the push services, and is our recommended solution.

Recommended solution: OAuth 2.0 authorization

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 solution: 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 the following information:

• username: username associated with the Basic Auth

• password: password associated with the Basic Auth

Automatic retry

DriveQuant will retry to push the data if an HTTP error occurs during the first attempt. Each service has a specific retry policy, please refer to the relevant section.