Push Deleted Driver

Introduction

There are use cases where the DriveQuant whitelabel application allows users to delete their accounts.

After a user requests their account deletion from the application, their data will be permanently deleted from the DriveQuant platform after a 30-day grace period.

The deletion request can be cancelled during the grace period (and the data be retained) if the user reconnects to the application or records a trip. If the user does not reconnect and no trip is recorded within these 30 days, all user-related data is permanently deleted from the DriveQuant platform.

The push deleted user service can be configured to notify you when a user deletion is finalized, so you can replicate this deletion on your system.

Principle

The push deleted driver sends the event information as soon as the user data is deleted on DriveQuant platform.

Configuration

See Configuration in the parent section.

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

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 until the request is acknowledged.

Sample Message

The Push Data API specification can be downloaded here in OpenAPI YAML format.

Sample message (click to expand)

{
  "userId": "my-user-id",
  "event": "USER_DELETION",
  "date": "2025-01-30T07:23:22.000+0000"
}