Application diagnosis
This API returns information about a user's application diagnosis. It can be used to determine whether the application settings are correct:
In a nominal state, the user's trips will be detected and recorded.
If the smartphone is not correctly configured, or if the user has not granted the proper accesses for the application, the trip recording may be altered.
When a user reports an issue with trip detection or recording, this API can help identify the most probable cause, which can greatly accelerate user support.
If you have your admin API key, you can try the API via this link.
Path parameters
Field | Type | Description |
---|---|---|
userId |
| Driver's unique identifier |
Response
The table below summarizes the list of a driver application's diagnosis data.
Field | Type | Description |
---|---|---|
userInfo | User information | |
smartphoneData | Information about the user's smartphone | |
lastUpdate |
| Last update of application diagnostic data Date format: |
status |
| Global smartphone status, which indicates if the mobile application is configured to record user trips (see the definition). Allowed values: |
comments |
| Short description of mobile application configuration status. See Comment |
sensors | Sensors status | |
permissions | Permissions status | |
settings | Additional settings status | |
events | Events related to user actions |
UserInfo
The table below summarizes the content of the userInfo
object.
Field | Type | Description |
---|---|---|
userId |
| User unique identifier |
firstname |
| User firstname |
lastname |
| User lastname |
companyName |
| Company name |
registerDate |
| User registration date Date format: |
firstTrip |
| Date of the first trip Date format: |
lastTrip |
| Date of the last trip Date format: |
SmartphoneData
The table below summarizes the content of the smartphoneData
object.
Field | Type | Description |
---|---|---|
phoneModel |
| Device model name |
appBuildNumber |
| Application build number |
osVersion |
| Version of the operating system |
osType |
| Platform: iOS or Android |
sdkVersion |
| Version of the DriveKit SDK |
phoneLanguage |
| Phone language |
rawPhoneLanguage |
| Raw phone language |
Comments
The table below summarizes the content of the comments
object.
Field | Type | Description |
---|---|---|
code |
| Comment identifier |
comment |
| Short description (in English) See Known Comments |
Sensors
The table below summarizes the content of the sensors
object.
Field | Type | Description |
---|---|---|
location |
| Location sensor status Allowed values: |
bluetooth |
| Bluetooth sensor status Allowed values: |
Permissions
The table below summarizes the content of the permissions
object.
Field | Type | Description |
---|---|---|
location |
| Location permission status Allowed values: |
bluetooth |
| Bluetooth permission status Allowed values: |
activity |
| Activity permission status Allowed values: |
notification |
| Notification permission status Allowed values: |
Settings
The table below summarizes the content of the settings
object.
Field | Type | Description |
---|---|---|
permissionAutodelete |
| Status of permission revocation functionality in case of prolonged inactivity (Android only). Allowed values:
|
batteryOptimisation |
| Battery optimization status (Android only) Allowed values: |
lowPowerMode |
| Low power mode status (iOS only) Allowed values: |
Events
The table below summarizes the content of the events
object.
Field | Type | Description |
---|---|---|
device |
| Status indicating whether the phone is on Allowed values: |
app |
| Status indicating whether the application is installed on the phone Allowed values: |
user |
| Status indicating whether the user is logged in Allowed values: |
Definitions
Global status
The global status value depends on the status of each individual parameter:
Status | Description |
---|---|
| At least one of the parameters is in CRITICAL state (🔴). |
| At least one of the parameters is in WARNING state (🟡), but no parameter is in CRITICAL state (🔴). |
| No parameter is in CRITICAL (🔴) or WARNING states (🟡). |
Note:
We chose not to consider parameters with an UNKNOWN
or NOT_APPLICABLE
status in the global status. More informations about the global status can be retrieved in the comments section.
Individual parameters criticality
The criticality of each parameter is determined by its status and, in some cases, is specific to the OS of the smartphone. We define 3 levels of criticality:
Level | Description |
---|---|
🔴 CRITICAL | Trip detection and/or recording is not possible |
🟡 WARNING | Trip detection and/or recording is impaired, and trips are likely to be lost |
🟢 MINOR | Trip detection and/or recording should work as expected |
The table below describes, for each parameter, the level of impact of a given status on trip detection and/or recording:
Type | Parameter | Criticality | Status |
---|---|---|---|
sensors | location | 🔴 |
|
sensors | bluetooth | 🟡 |
|
permissions | location | 🔴 |
|
permissions | bluetooth | 🟡 |
|
permissions | activity | 🟡 |
|
permissions | notification | 🟢 |
|
settings | permissionAutodelete | 🟢 |
|
settings | batteryOptimisation | 🟡 |
|
settings | lowPowerMode | 🟢 |
|
events | device | 🔴 |
|
events | app | 🔴 |
|
events | user | 🔴 |
|
Known Comments
The table below gives more details about the known values for the comments object. We encourage you to use the comment code to identify the messages, as the comment value might change in the future.
Code | Condition | Comment |
---|---|---|
0 | No issue detected | Trip detection and/or recording should work as expected |
1 | At least one event in warning state | Trip detection and/or recording is impaired, and trips are likely to be lost |
2 | At least one event in error state | Trip detection and/or recording is not possible |
3 | The | The data has not been updated for more than 7 days. It is not possible to guarantee that the current application settings are correct. |
4 | The location sensor status OR the location permission status are | Location sensor status or the permission to access the location sensor could not be retrieved. It is not possible to determine if the application is running normally. |
5 | Multiple phone models were used at the same time in the last 30 days | Shared account detected. There is no guarantee that the diagnosis data will correspond to the driver’s current smartphone. |
Last updated