---
metadata:
  - name: generator
    content: Diplodoc Platform v5.52.0
alternate:
  - https://yandex.kz/routing/doc/en/delivery/quickstart/data.md
  - https://yandex.kz/routing/doc/kk/delivery/quickstart/data.md
  - https://yandex.kz/routing/doc/ru/delivery/quickstart/data.md
  - href: en/delivery/quickstart/data.md
    type: text/markdown
    title: Markdown version
  - href: ../llms.txt
    type: text/markdown
    title: llms.txt
title: RouteQ — API implementation procedure — setting up data transfer from devices
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.kz/routing/doc/en/llms.txt


# Setting up data transfer from devices

The Track & Trace API relies on couriers sending their order status and current location data.

The API supports sending data through the [app](#app) or [GPS tracker](#gps) .

## App {#app}

The actual data from the RouteQ app is sent automatically after the route is selected.

### Enabling access for couriers {#app-courier-access}

To grant couriers access to the RouteQ app:

1. Log in to your company account and go to [Routing Workspace](https://yandex.com/courier).
2. In the menu on the left, go to **Settings** → **Mobile app**.
3. Add the couriers' phone numbers in `+1**********` format.

Instructions for mobile apps can be found in the [RouteQ](https://yandex.kz/routing/doc/en/rq-app/index.md) app documentation.

## GPS tracker {#gps}

Receiving actual data from GPS trackers is supported by the following protocols:

* ERA GLONASS Telematics Standard (EGTS), pursuant to Order No. 285 of the Russian Ministry of Transport.
* [FLEX](https://wiki.navtelecom.ru/ru/home/developers).
* [Wialon Retranslator](https://help.wialon.com/ru/wialon-local/2504/user-guide/management-system/retranslators).

Data from the GPS tracker must be sent in real time.

### Configuration requirements {#gps-configuration}

#|
|| **Protocol** | **EGTS** | **FLEX** | **Wialon Retranslator** ||
|| **Server address** | egts.yandex.net | b2bgeo-flex-proxy.maps.yandex.net | telematics-proxy.routeq.yandex.net ||
|| **TCP port** | 4000 | 6000 | 20332 ||
|| **Device ID** | Number set by the device owner | Number set by the device owner | IMEI ||
|| **EGTS_SR_TERM_IDENTITY package** | Required, must include the IMEI number. Used for device identification | — | — ||
|| **EGTS_SR_POS_DATA package** | Contains the FLG field required to specify additional navigation parcel parameters. It includes the VLD bit that indicates the validity of coordinate data. Data is considered valid if the VLD bit is equal to one when data is transmitted. | — | — ||
|| **New session for each package** | Optional; must be **disabled** during relay setup | — | — ||
|| **Frequency of sending location data, in motion** | Every 20 seconds | Every 20 seconds | Every 20 seconds ||
|| **Frequency of sending location data, not in motion** | Every 120 seconds | Every 120 seconds | Every 120 seconds ||
|| **Maximum location data sending delay** | 24 hours | 24 hours | 24 hours ||
|#

When using the EGTS protocol, RouteQ supports **EGTS_AUTH_SERVICE** and **EGTS_TELEDATA_SERVICE**. Other services aren't supported because they aren't designed to send coordinates. 

### Configuration settings and device identification {#gps-configuration-settings} 

Configuration settings are specified in the parameters of the GPS tracker or in the GPS provider's system. 

If location data is not sent for 1 minute, the service will close the connection with the GPS tracker. The system ignores location messages with a time delay of more than one day.

To identify devices, you can use unique values:

#|
|| **Unique number** | **Definition** | **Comments** ||
|| **Device ID** | A number set by the device owner and sent in the EGTS service data | To avoid linking the device ID to the IMEI number, we recommend [specifying the IMEI number](https://yandex.kz/routing/doc/en/vrp/excel-fill-guide.md#vehicles-general) when planning. ||
|| **IMEI** | A number consisting of 15–17 digits | The EGTS protocol transmits only the last 8–10 digits of a 15–17 digit IMEI number. ||
|| **TID** | A number specified in the device documentation | TID is considered the same as IMEI if no `EGTS_SR_TERM_IDENTITY` packet has been received over the EGTS protocol, outlining the TID-IMEI mapping. Authorization not supported. ||
|#

{% note warning %}

The device ID, IMEI, and TID are different numbers.

{% endnote %}

The API only supports numeric IDs and IMEIs.

### How to check data transfer {#check}

You can verify that data from the GPS tracker has been received in the [GPS trackers](https://yandex.kz/routing/doc/en/delivery/interface/gps-trackers.md) section. 

If you couldn't set up the data transfer via the GPS tracker, contact support.

<!-- source: en/delivery/_includes/feedback.md -->
<a href="../feedback">
  <span class="button">Contact support</span>
</a>



[//]: # (Version without HTML\: \[Contact support\]\(../../../feedback.md\))
<!-- endsource: en/delivery/_includes/feedback.md -->