Asset
Tracks for an asset, resolved across every tracker the asset was attached to over the period.
An asset is tracked through whichever device is attached to it at the time, and that device can change. These operations take an asset and resolve its trackers, which is what separates them from track/*, where the caller supplies tracker IDs directly.
Each entry in a response carries its own interval: the window during which the asset was attached to that tracker, not the window the request asked for. An asset moved between devices mid-period therefore comes back as several entries.
A track arrives as one of four kinds, selected by its type. regular is an ordinary trip. single_report covers a device reporting in interval mode, or a period holding only one point. merged is the whole period as one track, returned when split was false. cluster groups one-point trips by coordinate, returned when cluster_single_reports was true.
Point object
The point object both operations return, in points_list on a track and in track_points on a read:
Whether a point counts as trip or as parking is decided by the Navixy platform's parking detection settings.
API actions
API base path: /asset/track.
Return the tracks of an asset over a period, one entry per tracker the asset was attached to.
Each entry carries its own interval, which is the window during which the asset was attached to that tracker, not the window you asked for.
This is the asset track resource, asset/track/*, which takes an asset and resolves its trackers for you. It is a different resource from track/*, which takes tracker IDs directly.
A request with an empty body reports interval as a missing parameter alongside asset. That is the internal name of the field holding both dates; the public parameters are from and to.
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.
Start of the period. The response begins with the next track point after this time.
2026-08-24 09:00:00End of the period. Must be later than from.
2026-08-24 09:00:00Optional. Default true. Drop tracks judged too short by length and point count.
Optional. Default true. When false, all tracks in the period are combined into one, returned as a merged track.
Optional. Default true. When false, GSM LBS points are excluded.
Optional. Default false. When true, single-point trips are grouped by coordinates into cluster tracks.
Optional. Default false. When true, each multi-point track carries event_count.
Optional. Default false. When true, address fields come back empty.
Optional. Default false. When true, each track carries its points_list.
Optional. Reduce the returned points to about this many, from 2 to 3000. Without it the server's own simplification settings apply. Not a hard limit: the response may contain more.
The asset's tracks, per tracker
true if request finished successfully.
trueBad request. The response body carries the API-level error code in status.code. Validation failures also include an errors array naming each offending parameter.
Error 211: the period between from and to is longer than the API configuration allows.
Error 201: the asset in the request does not exist. The description names it, for example "Employee #1 not found".
Error response object
POST /v2/asset/track/list HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 248
{
"asset": {
"id": 1,
"type": "vehicle"
},
"from": "2026-08-24 09:00:00",
"to": "2026-08-24 09:00:00",
"filter": true,
"split": true,
"include_gsm_lbs": true,
"cluster_single_reports": true,
"count_events": true,
"omit_addresses": true,
"with_points": true,
"point_limit": 1
}{
"success": true,
"list": [
{
"tracker_id": 1,
"limit_exceeded": true,
"interval": {
"from": "2026-08-24 09:00:00",
"to": "2026-08-24 09:00:00"
},
"tracks": [
{
"id": 1,
"type": "regular",
"start_date": "text",
"start_address": "text",
"end_date": "text",
"end_address": "text",
"length": 1,
"points": 1,
"max_speed": 1,
"avg_speed": 1,
"event_count": 1,
"norm_fuel_consumed": 1,
"precision": 1,
"gsm_lbs": true,
"points_list": [
{
"lat": 1,
"lng": 1,
"alt": 1,
"satellites": 1,
"mileage": 1,
"get_time": "text",
"address": "text",
"heading": 1,
"speed": 1,
"precision": 1,
"gsm_lbs": true,
"parking": true,
"buffered": true
}
],
"bounds": {
"nw": {
"lat": 1,
"lng": 1
},
"se": {
"lat": 1,
"lng": 1
}
}
}
]
}
],
"total": {
"count": 1,
"length": 1,
"trip_duration": "text",
"parking_duration": "text",
"norm_fuel_consumed": 1
}
}Errors
These errors come in addition to the general error codes:
201 - Not found in the database, when no asset has the given ID.
211 - Requested time span is too big, when the interval between
fromandtoexceeds the maximum the API configuration allows.
The timestamp on each point is the moment the tracker recorded it, adjusted to the user's time zone.
Return the individual track points recorded for an asset over a period, one entry per tracker the asset was attached to.
Each point's timestamp is when the tracker recorded it, in the user's time zone.
This is the asset track resource, asset/track/*, which takes an asset and resolves its trackers for you. It is a different resource from track/*, which takes tracker IDs directly.
A request with an empty body reports interval as a missing parameter alongside asset. That is the internal name of the field holding both dates; the public parameters are from and to.
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.
Start of the period. The response begins with the next track point after this time.
2026-08-24 09:00:00End of the period. Must be later than from.
2026-08-24 09:00:00Optional. Return only the points of this track. Without it, every valid track point in the period is returned.
Optional. Default true. When false and no track_id is given, GSM LBS points are excluded.
Optional. Default true. When true, the returned data is simplified to fewer points.
Optional. Only applies when simplify is true. Reduce the returned points to about this many, from 2 to 3000. Not a hard limit: the response may contain more.
Optional. When true, tracks are filtered, which currently affects LBS tracks only. When false, parking points are included.
The asset's track points, per tracker
true if request finished successfully.
trueBad request. The response body carries the API-level error code in status.code. Validation failures also include an errors array naming each offending parameter.
Error 211: the period between from and to is longer than the API configuration allows.
Error 201: the asset in the request does not exist.
Error response object
POST /v2/asset/track/read HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 173
{
"asset": {
"id": 1,
"type": "vehicle"
},
"from": "2026-08-24 09:00:00",
"to": "2026-08-24 09:00:00",
"track_id": 1,
"include_gsm_lbs": true,
"simplify": true,
"point_limit": 1,
"filter": true
}{
"success": true,
"list": [
{
"tracker_id": 1,
"limit_exceeded": true,
"interval": {
"from": "2026-08-24 09:00:00",
"to": "2026-08-24 09:00:00"
},
"track_points": [
{
"lat": 1,
"lng": 1,
"alt": 1,
"satellites": 1,
"mileage": 1,
"get_time": "text",
"address": "text",
"heading": 1,
"speed": 1,
"precision": 1,
"gsm_lbs": true,
"parking": true,
"buffered": true
}
]
}
]
}Errors
These errors come in addition to the general error codes:
201 - Not found in the database, when no asset has the given ID.
211 - Requested time span is too big, when the interval between
fromandtoexceeds the maximum the API configuration allows.
More in this section
Asset groups
Last updated
Was this helpful?