Enterprise API
The Enterprise API is specially designed to respond to the needs of insurers offering fleet insurance for professionals, or companies requiring multiple fleets of vehicles to be independently managed.
With this solution, you can manage your clients individually and isolate their data by creating dedicated teams.
The Enterprise API includes services to:
-
Create teams and control access to driving analysis services.
-
Configure "hyper-administrator" accounts authorized to access all of your teams' data.
-
Access statistics and manage the transfer of trips or accidents data to your data lake.
Get the location of the end of a trip with the DriveKit SDK
The DriveKit SDK now includes a new method, getLastTripLocation(), to retrieve the end of trip location.
This method returns the following information:
-
GPS coordinates (latitude and longitude) at the end of the trip,
-
the date and time of the trip,
-
and an accuracy indicator.
This data can be integrated into your mobile application to:
-
Create a geofence to locate the vehicle.
-
Help users find their vehicle.
-
Notify the driver of arrival at a specific destination.
Unique local trip identifier
A trip's unique identifier is assigned once the data analysis has been completed and the driving indicators calculated.
For this reason, it is not possible to know this identifier until the trip has been analyzed.
If your application needs to identify a trip's data before it is analyzed, DriveKit also contains a local unique trip identifier. This is accessed via the getCurrentTripInfo() method.
This method contains three attributes:
-
Unique local trip identifier.
-
Trip start date.
-
Trip recording trigger mode.
The local trip start identifier is shared with trip or accident data when it is transmitted to your data lake.
Enhancement of the Trip Listener Interface
The TripListener interface plays a crucial role in providing real-time insights into the progress of trip recording and analysis.
The latest version of the DriveKit SDK (2.9.0) introduces new methods to the TripListener in order to get all the states of a trip's analysis cycle.
-
tripRecordingStarted indicates that the start of a trip has been detected.
-
tripRecordingConfirmed confirms that the trip can be recorded, as it is a vehicle trip.
-
tripRecordingCanceled indicates that the trip has been canceled.
-
tripRecordingFinished informs that the trip is finished.
-
tripFinished informs that the trip data has been analyzed and the driving indicators have been calculated.
The tripStarted and tripCancelled methods have been deprecated, but remain operational.
We recommend to replace them with the new tripRecordingConfirmed and tripRecordingCanceled methods to obtain more detailed and comprehensive data.
End of support for Android 6 and 7
We kindly remind you that the DriveKit SDK will no longer be compatible with Android 6 and 7 from version 2.10.0. This version will be released in January 2025.
Therefore, we highly recommend configuring your application to support Android 8 (API 26) or later versions.
Using recent versions of Android is recommended and has many advantages for you and your users:
-
The collection of permissions that regulate data collection in the background is more transparent to users and complies with the recommendations of the GDPR;
-
The updates proposed by Google improve the security of the user's data.
End of iOS 12 support for DriveKit
Starting with DriveKit SDK version 2.11.0 in February 2025, iOS 12 will no longer be supported. We recommend that you plan your migration now.
iOS 12 was introduced by Apple in 2018. We have decided to deprecate this version because it limits the adoption of new features. In addition, it no longer benefits from security updates since January 2023.
The following models cannot be updated beyond iOS 12: iPhone 5s (2013), iPhone 6 (2014) and iPhone 6 Plus (2014).
Overall, over 99% of your users' iPhones are running iOS 13 or later versions.
