> For the complete documentation index, see [llms.txt](https://docs.drivequant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivequant.com/push-services/push-beacon-location.md).
# Push Beacon Location
## **Introduction**
The [Stolen Vehicle Locator](/stolen-vehicle-locator/how-it-works.md) 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](/backend/stolen-vehicle/create-a-theft-report.md), 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](/push-services/introduction.md#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](#sample-message).
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](#retry-policy).
{% hint style="danger" %}
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!*
{% endhint %}
## 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](https://gist.github.com/DriveQuantPublic/5b773eb6d92a947d78d8515692610e8a) in OpenAPI YAML format.
Sample message (click to expand)
```json
{
"theftReportId": "69d426569c1da34dd83a4aac",
"beaconLocationId": "69db89428079d1524d076039",
"date": "2026-04-18T17:25:01.789Z",
"uuid": "123e4567-e89b-12d3-a456-426614174000",
"major": 1,
"minor": 1,
"latitude": 48.856614,
"longitude": 2.3522219,
"accuracy": 50
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.drivequant.com/push-services/push-beacon-location.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.