Push Deleted trip


There are use cases where the DriveKit SDK allows the user to delete a trip.

The request to delete a trip results in the permanent deletion of all trip data from DriveKit's local database and DriveQuant's database.

If the trip data has been posted to your backend as well (via the push data service,), it should be deleted accordingly.

In order to perform this, a push deleted trip service can be configured.


The push deleted trip sends the event information when the user deletes the trip via a push service.


Trip deletion event is sent as a POST request to a client URL. The URL must be provided to DriveQuant in order to set up and activate the push update trip service.

The body of the request is a JSON object with a set of fields that contain the id of the trip, and the trip modification event.

It is mandatory to configure a response code. If the post is accepted, we expect a status code of 200 (OK). In case of failure, for any answer other than 200, the service will attempt to post the data again. The retry strategy is described below.

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


The security configuration must be identical to thatof the push data service.

Automatic Retry

DriveQuant will retry to push the deleted trip data in case of a HTTP error. In order to avoid too many consecutive retries, the push deleted trips replay will be performed one time per day from the day after a fail, this until the trip deletion has been accepted. If after 30 days the trip deletion has not been accepted, the replay will not be performed anymore.

REST request

Last updated