BLE beacon data

What a tracker saw of the radio tags around it, as history or as last known values.

BLE beacon data is what a tracker saw of the radio tags around it: iBeacon, Teltonika EYE Beacon and Sensor, Eddystone, and similar devices. Each scan records which tag was seen, how strong its signal was, and where the tracker stood at the time.

Two operations read that data. beacon/data/read returns the scans recorded between from and to, sorted by get_time. beacon/data/last_values returns the most recent scan of each beacon currently visible to the given trackers, and with an empty body it covers the last hour across every tracker the caller can reach.

BLE beacon data entry

API actions

API base path: /beacon/data.

---

Read BLE beacon data history

post

/beacon/data/read

Return BLE beacon scans recorded between from and to, sorted by get_time.

Beacon data is what a tracker saw of the radio tags around it: iBeacon, Teltonika EYE Beacon or Sensor, Eddystone and similar.

Omitting trackers means every tracker available to the caller, not none. The interval is additionally clipped by each tracker's history-depth limit, and a tracker whose limit excludes the whole interval contributes nothing rather than raising an error.

Authorizations

AuthorizationstringRequired

Either a user session hash or an API key, with the "NVX " prefix, for example "NVX 22eac1c27af4be7b9d04da2ce1af111b". Obtain a session hash from the userAuth operation, or create an API key from the API keys operations. A small number of operations accept a session hash only and reject an API key with error code 4; each says so in its description.

Body

fromstringRequired

Start of the period, in YYYY-MM-DD HH:MM:SS format.

Example: 2026-08-24 09:00:00

tostringRequired

End of the period, in YYYY-MM-DD HH:MM:SS format. Must be after from.

Example: 2026-08-24 09:00:00

trackersinteger[]Optional

Optional. Tracker IDs. Omit to search every tracker available to the caller. Cannot be an empty array.

beaconsstring[]Optional

Optional. Beacon hardware IDs. Each must be 1 to 64 characters. Omit to return data for all beacons.

Responses

200

Matching beacon scans

application/json

successbooleanRead-onlyOptional

true if request finished successfully.

Example: true

400

Bad request. The response body carries the API-level error code in status.code. Validation failures also include an errors array naming each offending parameter.

application/json

403

Error 208: one of the trackers is blocked, normally because its tariff ended. Error 217: one or more of the tracker IDs does not exist or belongs to another user.

application/json

default

Error response object

application/json

post/beacon/data/read

POST /v2/beacon/data/read HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 91

{
  "from": "2026-08-24 09:00:00",
  "to": "2026-08-24 09:00:00",
  "trackers": [
    1
  ],
  "beacons": [
    "text"
  ]
}

{
  "success": true,
  "list": [
    {
      "tracker_id": 1,
      "hardware_id": "text",
      "rssi": 1,
      "get_time": "text",
      "latitude": 1,
      "longitude": 1,
      "ext_data": {
        "ANY_ADDITIONAL_PROPERTY": "anything"
      }
    }
  ]
}

Errors

These errors come in addition to the general error codes:

• 208 - One of the trackers is blocked, normally because its tariff ended.

• 217 - One or more of the tracker IDs does not exist or belongs to another user.

---

Read last BLE beacon values

post

/beacon/data/last_values

Return the most recent scan of each BLE beacon currently visible to the given trackers.

Callable with an empty body, which reads every tracker available to the caller over the last hour.

Authorizations

AuthorizationstringRequired

Either a user session hash or an API key, with the "NVX " prefix, for example "NVX 22eac1c27af4be7b9d04da2ce1af111b". Obtain a session hash from the userAuth operation, or create an API key from the API keys operations. A small number of operations accept a session hash only and reject an API key with error code 4; each says so in its description.

Body

trackersinteger[]Optional

Optional. Tracker IDs. Omit to read every tracker available to the caller. Cannot be an empty array.

skip_older_than_secondsintegerOptional

Optional. Default 3600. Ignore scans older than this many seconds.

Responses

200

Last beacon values

application/json

successbooleanRead-onlyOptional

true if request finished successfully.

Example: true

400

Bad request. The response body carries the API-level error code in status.code. Validation failures also include an errors array naming each offending parameter.

application/json

403

Error 208: one of the trackers is blocked, normally because its tariff ended. Error 217: one or more of the tracker IDs does not exist or belongs to another user.

application/json

default

Error response object

application/json

post/beacon/data/last_values

POST /v2/beacon/data/last_values HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 44

{
  "trackers": [
    1
  ],
  "skip_older_than_seconds": 1
}

{
  "success": true,
  "list": [
    {
      "tracker_id": 1,
      "hardware_id": "text",
      "rssi": 1,
      "get_time": "text",
      "latitude": 1,
      "longitude": 1,
      "ext_data": {
        "ANY_ADDITIONAL_PROPERTY": "anything"
      }
    }
  ]
}

Errors

These errors come in addition to the general error codes:

• 208 - One of the trackers is blocked, normally because its tariff ended.

• 217 - One or more of the tracker IDs does not exist or belongs to another user.