Push Beacon Location
Introduction
The Stolen Vehicle Locator module of the DriveKit SDK enables users' phones to detect nearby iBeacon devices, creating a collaborative detection network across your user community.
When a vehicle is reported as stolen, every detection of its associated iBeacon device, captured by your users' phones, is sent to the DriveQuant platform in real-time.
Principle
The push beacon location service shares iBeacon detection data collected by the DriveKit SDK, installed across your users' mobile applications, with your platform.
The process works as follows:
The Stolen Vehicle Locator module detects a nearby iBeacon device and sends its location and detection date to the DriveQuant platform.
If the iBeacon is linked to an active theft report, and if you have subscribed to the beacon location push service, the data is forwarded to your platform immediately upon receipt.
This approach ensures you always receive the most up-to-date location information, with no need to implement a polling strategy to track your stolen vehicles.
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. If your service still refuses the request after 30 days, the push data will be permanently discarded.
Sample Message
The OpenAPI specification can be downloaded here in OpenAPI YAML format.
Last updated
Was this helpful?