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 or GPS tracker .

App

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

Enabling access for couriers

To grant couriers access to the RouteQ app:

1. Log in to your company account and go to Routing Workspace.
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 app documentation.

GPS tracker

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.
• Wialon Retranslator.

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

Configuration requirements

Configuration features:

• 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.

• If you're use Wialon Retranslator, provide the device ID in the unit_id field. Track & Trace uses this value as the tracker IMEI — no separate identifier mapping is provided. For every successfully received and recorded packet, the server sends a one‑byte acknowledgment with the value 0x11. If you don't receive an acknowledgment, resend the packet after reconnecting. This behavior is standard for the Wialon client.

Configuration settings and device identification

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:

The API only supports numeric IDs and IMEIs.

Data relay setup via Wialon Retranslator

Before starting, verify that the following conditions are met:

• The device or the Track & Trace platform supports data streaming via the Wialon Retranslator 1.0 (TCP push) protocol.
• A GPS tracker registered in Track & Trace has an IMEI that strictly matches the unit_id value sent in the packets. If this condition is not met, you won't see coordinates in the track, even if the server successfully acknowledges packet receipt.
• For each sensor on an active route, a sensor with a known sensor_number has been created in Track & Trace. The parameter name in Wialon must match the sensor_number byte‑for‑byte.

How to check data transfer

To check data reception from a GPS tracker, try one of these methods:

• Routing Workspace. For more information, see GPS trackers.

• API:

  Send a POST request to the gps-trackers/status resource. In the request body, specify the company ID and one or more GPS tracker IMEI numbers.

  Request

  cURL

  curl -H "Authorization: OAuth <your-token>" \
       -H "Content-Type: application/json" \
       -X POST https://courier.yandex.ru/api/v1/companies/gps-trackers/status \
       -d '{
             "company_id": <your-company-ID>,
             "imeis": [123456789012345, 987654321098765]
           }'
  

  Result

  The method returns an array of objects. Each object corresponds to a GPS tracker and contains the following fields:

  • imei: The GPS tracker number.
  • imei_str: The GPS tracker number in string format.
  • time: The date and time of the courier's last known position, in ISO 8601 format.

  Sample response:

  [
  {
      "imei": 123456789012345,
      "imei_str": "123456789012345",
      "time": "2026-07-24T10:30:00.000Z"
    }
  ]
  

  If a tracker hasn't sent any data, it won't be included in the response.

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