Push Crash Report Data

Introduction

The data collected by the DriveKit SDK during a trip and a collision enables insurance platforms to streamline claims processing with precise, contextual insights about recorded accidents. This data accelerates the claims management process and supports more informed decision-making.

The DriveQuant Crash Report delivers a comprehensive analysis of the conditions in which an accident occurred, combining trip data, driving behavior metrics, and crash detection information to give insurers a complete picture of each incident.

Principle

The Crash Report push service sends a comprehensive report once the trip during which the accident occurred has ended and has been analyzed.

The overall process is summarized below:

• The SDK begins recording a trip and activates the crash monitoring.

• In case of a suspected collision, the SDK immediately sends a portion of the data to DriveQuant crash analysis service, which calculates the probability that an accident occurred.

• Once the trip ends, the SDK stops trip recording, and sends the data to DriveQuant trip analysis service.

• As soon as the analysis is complete, the crash report is computed and transmitted to your platform through the crash report push service.

Crash reports are exclusively computed for confirmed accidents, for which a trip was recorded and analyzed.

Configuration

See Configuration in the parent section.

The body of the request is a JSON object with a set of fields that contain the raw data and crash indicators. An example of data in JSON format is given at the end of this section.

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!

Retry Policy

Every push request not successfully acknowledged by your service will be retried once a day. After 30 unsuccessful attempts, the push data will be permanently discarded.

Sample Message

The OpenAPI specification can be downloaded here in OpenAPI YAML format.

Sample message (click to expand)

{
  "info": {
    "crashId": "695cdaa9c48d52239bffa7da",
    "itinId": "695cdab2f1ac586b8354f596",
    "userId": "af1bc789-9acd-48c7-b017-088cc7725e21",
    "teamName": "mycompany",
    "crashDate": "2025-10-18T09:40:57.330+0000",
    "tripStartDate": "2025-10-18T14:02:13.330+0000",
    "tripEndDate": "2025-10-18T14:24:56.330+0000"
  },
  "tripConditions": {
    "weather": "CLEAR_SKY",
    "roadContext": "SUBURBAN",
    "day": true
  },
  "driverFatigue": {
    "tripDistance": 15.54,
    "tripDuration": 1363,
    "last12HoursDistance": 202,
    "last12HoursDuration": 17719,
    "breakTime": 7637
  },
  "aggressiveDriving": {
    "safetyScoreAverage": 9,
    "safetyScoreTrip": 8.2,
    "hardBrakingFreqAverage": 10.6,
    "hardBrakingFreqTrip": 38.6
  },
  "phoneUsage": {
    "distractionScoreAverage": 8.31,
    "distractionScoreTrip": 4.45,
    "unlocksTrip": 3,
    "callDurationTrip": 3,
    "callForbiddenDurationTrip": 3,
    "distractionToCrashTime": 0,
    "lastDistractionType": "UNAVAILABLE"
  },
  "speeding": {
    "speedingScoreAverage": 7.01,
    "speedingScoreTrip": 6.2,
    "speedingDistanceTrip": 773,
    "speedingDurationTrip": 24,
    "speedingBeforeCrash": 0
  },
  "riskFactors": {
    "tripConditions": "LOW",
    "driverFatigue": "LOW",
    "aggressiveDriving": "HIGH",
    "phoneUse": "HIGH",
    "speeding": "LOW"
  }
}

Definitions

The body of the request is a JSON object with a set of fields containing general user information and an assessment of the risk factors that may have contributed to the accident. Risk factors are, divided into five categories:

1. Trip conditions: external factors that can increase the risk of accidents (poor weather, heavy traffic, or challenging road conditions).

2. Driver fatigue: lack of adequate rest that can decrease awareness and increase reaction times.

3. Aggressive driving: dangerous behaviors that can increase the risk of accidents.

4. Phone usage: distractions caused by mobile device interaction while driving.

5. Speeding: driving over the speed limit, which can reduce vehicle control and increase collision severity.

The probabilities are expressed as binary values (LOW, HIGH) depending on whether the factor may have contributed to increase the accident risk.

The computation of a speeding risk is only available if the speeding score computation is enabled for your account, and if a speeding score was computed for the associated trip.

Please reach out to us at [email protected] if you need to enable this service.

The computation of the probabilities is based on several features, which are also included in the content of the crash report request. The content of these features is described in the following sections.

Trip Conditions

Field	Type	Description
weather	string	Weather conditions during the trip Allowed values: UNAVAILABLE, UNKNOWN, CLEAR_SKY, CLOUDY, FOGGY, RAINY, SNOWY, ICY
roadContext	string	Main road context of the trip Allowed values: TRAFFIC_JAM, HEAVY_URBAN_TRAFFIC, CITY, SUBURBAN, EXPRESSWAYS
day	boolean	Indicates if the crash happened during the day (true) or at night (false)

Driver Fatigue

Field	Type	Description
tripDistance	number	Trip distance (in km)
tripDuration	integer	Trip duration (in s)
last12HoursDistance	number	Distance traveled in the last 12 hours (in km)
last12HoursDuration	integer	Driving time in the last 12 hours (in s)
breakTime	integer	Break time between the previous trip and the current trip (in s)

Aggressive Driving

Field	Type	Description
safetyScoreAverage	number	Driver average safety score
safetyScoreTrip	number	Trip safety score
hardBrakingFreqAverage	number	Driver average frequency of hard braking events (in events / 100 km)
hardBrakingFreqTrip	number	Trip frequency of hard braking (in events / 100 km)

Phone Usage

Field	Type	Description
distractionScoreAverage	number	Driver average distraction score
distractionScoreTrip	number	Trip distraction score
unlocksTrip	integer	Number of phone unlocks during the trip
callDurationTrip	integer	Total call duration during the trip (in s)
callForbiddenDurationTrip	integer	Duration of forbidden calls during the trip (in s)
distractionToCrashTime	integer	Time between last distraction and crash (if < 60 s) (in s)
lastDistractionType	string	Type of last distraction. Allowed values: AUTHORIZED_CALL_START, AUTHORIZED_CALL_END, FORBIDDEN_CALL_START, FORBIDDEN_CALL_END, PHONE_UNLOCK, PHONE_LOCK, UNAVAILABLE

Speeding

Field	Type	Description
speedingScoreAverage	number	Driver average speeding score
speedingScoreTrip	number	Trip speeding score
speedingDistanceTrip	number	Trip speeding distance (in m)
speedingDurationTrip	integer	Trip speeding duration (in s)
speedingBeforeCrash	integer	Mean velocity above the speed limit during the 20 seconds before the crash (in km/h)