Position History service

Service version: 1
Last edit: 2019.09.18

Purpose

The Location History API provides the ability to save and read positions.

It is tightly coupled with the Objects service. Position always corresponds to the object.

To save the position, an endpoint only requires an API Key.

The Location History service contains the following endpoints:

POSTSend position: This endpoint saves a position.
GETGet object's last position: This endpoint requests the last position that has been saved for the object.
GETGet object's positions: This endpoint requests history of positions in the given time range.
DELETEClear objects' positions history: This endpoint provides a command used to delete historical positions.

Please use the navigation menu on the left-side of each page to find the topic and data you need.