{"id":17081,"date":"2025-06-30T08:31:36","date_gmt":"2025-06-30T05:31:36","guid":{"rendered":"https:\/\/www.fmsdocumentation.com\/api\/api-%d1%96%d1%81%d1%82%d0%be%d1%80%d1%96%d1%97-%d0%ba%d0%be%d0%be%d1%80%d0%b4%d0%b8%d0%bd%d0%b0%d1%82-%d0%be%d0%b1%d1%94%d0%ba%d1%82%d1%96%d0%b2\/"},"modified":"2026-03-24T16:51:46","modified_gmt":"2026-03-24T13:51:46","slug":"api-%d1%96%d1%81%d1%82%d0%be%d1%80%d1%96%d1%97-%d0%ba%d0%be%d0%be%d1%80%d0%b4%d0%b8%d0%bd%d0%b0%d1%82-%d0%be%d0%b1%d1%94%d0%ba%d1%82%d1%96%d0%b2","status":"publish","type":"page","link":"https:\/\/www.fmsdocumentation.com\/uk\/api\/api-%d1%96%d1%81%d1%82%d0%be%d1%80%d1%96%d1%97-%d0%ba%d0%be%d0%be%d1%80%d0%b4%d0%b8%d0%bd%d0%b0%d1%82-%d0%be%d0%b1%d1%94%d0%ba%d1%82%d1%96%d0%b2\/","title":{"rendered":"API \u0456\u0441\u0442\u043e\u0440\u0456\u0457 \u043a\u043e\u043e\u0440\u0434\u0438\u043d\u0430\u0442 \u043e\u0431’\u0454\u043a\u0442\u0456\u0432"},"content":{"rendered":"

Object Coordinates History API main purpose is to output clients\u2019 object historical data (coordinates). Object Coordinates History API has two endpoints, thus there are two types of requests. The first type of request is for one object and a specific date and time. Only data recorded at the specified date and time is shown.<\/p>\n

Request example for a specific date:<\/p>\n

GET \/objects\/{object_id}\/coordinates\/{datetime}\/?version=1&api_key=<..> HTTP\/1.1
\nHOST:api.fm-track.com
\nContent-Type:application\/json;charset=UTF-8<\/p>\n

The request type requires three parameters (not counting the API_key) to be specified in order for the API request to work:<\/p>\n\n\n\n\n\t\n\n\t\n\t\n\t\n\t
Parameter<\/th>Type<\/th>Description<\/th>\n<\/tr>\n<\/thead>\n
object_id<\/td>String<\/td>External object ID<\/td>\n<\/tr>\n
datetime<\/td>Date time<\/td>Requested record for the specified date and time. Date and time format example: \u201c2017-04-13T06:58:48.090Z\u201d in accordance to the ISO-8601 standard<\/td>\n<\/tr>\n
version<\/td>String<\/td>Version of the API, currently only version=1 is available<\/td>\n<\/tr>\n
api_key<\/td>String<\/td>User identification key<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n

Note
\nIt is recommended to use datetime parameter from the second endpoint of the Object Coordinates History API because the date time parameter is specified by the second, and the system does not search for data around the specified date.<\/p><\/p>\n

A response example is shown if all the parameters were included and the API_key is valid:<\/p>\n

\n
{\r\n    \"object_id\" : \"abc123\",\r\n    \"datetime\" : \"2017-04-13T06:58:48.090Z\",\r\n    \"ignition_status\" : \"UNKNOWN\",\r\n    \"position\" : {\r\n        \"altitude\" : 0,\r\n        \"direction\" : 0,\r\n        \"latitude\" : 0,\r\n        \"longitude\" : 0,\r\n        \"hdop\": 0,\r\n        \"satellites_count\" : 0,\r\n        \"speed\" : 0\r\n    },\r\n    \"device_inputs\" : {\r\n        \"digital_input_1\" : true,\r\n        \"digital_input_2\" : true,\r\n        \"digital_input_3\" : true,\r\n        \"digital_input_4\" : true,\r\n        \"power_supply_voltage\" : 0,\r\n        \"ibutton\" : \"xxxxxxxxxx\",\r\n        \"first_driver_id\" : \"xxxxxxxxxx\",\r\n        \"second_driver_id\" : \"xxxxxxxxxx\",\r\n         \"temperature_sensor_0\": 0,\r\n         \"temperature_sensor_1\": 0,\r\n         \"temperature_sensor_2\": 0,\r\n         \"temperature_sensor_3\": 0,\r\n         \"temperature_sensor_0_id\": \"xxxxxxxxxx\"\r\n    },\r\n    \"calculated_inputs\":{\r\n        \"mileage\" : 0\r\n    }\r\n}<\/pre>\n<\/div>\n
If a parameter or the API_key was inputted incorrectly, the system will respond with an error code, all possible error codes are described in the APIs section. Parameters are described at the end of this section.<\/p>\n
The second endpoint of the History API displays an array of\u00a0 history data for a defined period of time. Each set of data has a specified date and time, which can be used when sending the first type of History API request.<\/p>\n
Request example for a specific date period:<\/p>\n
GET \/objects\/{object_id}\/coordinates?version=1&{fromDatetime,toDatetime,continuationToken,limit}&api_key=<..> HTTP\/1.1
\nHOST:api.fm-track.com
\nContent-Type:application\/json;charset=UTF-8<\/p>\n
The request type requires three parameters (not counting the API_key) to be specified in order for the API request to work:<\/p>\n\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t
Parameter<\/th>Type<\/th>Description<\/th>\n<\/tr>\n<\/thead>\n
objectId<\/td>String<\/td>External object ID<\/td>\n<\/tr>\n
fromDatetime<\/td>Date time<\/td>Find records starting from the specified date and time.  Date and time format example: \u201c2017-04-13T06:58:48.090Z\u201d in accordance to the ISO-8601 standard<\/td>\n<\/tr>\n
version<\/td>String<\/td>Version of API<\/td>\n<\/tr>\n
api_key<\/td>String<\/td>User identification key<\/td>\n<\/tr>\n
toDatetime<\/td>Date time<\/td>Find records up until the specified date and time. If it is not specified, the system will search for records up until the current date until the limit of records is reached. Date and time format example: \u201c2017-04-13T06:58:48.090Z\u201d in accordance to the ISO-8601 standard<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n
Optional parameters that are not mandatory, but can be included in the request:<\/p>\n\n\n\n\n\t\n\n\t\n\t\n\t
Parameter<\/th>Type<\/th>Description<\/th>\n<\/tr>\n<\/thead>\n
continuationToken<\/td>Date time<\/td>Including a continuation token, will display the next set of records, after the previous limit of records was reached.   <\/td>\n<\/tr>\n
limit<\/td>Integer<\/td>Limits records to the set count in the system response (default value \u2013 100 records, maximum value \u2013 1000)<\/td>\n<\/tr>\n
api_key<\/td>String<\/td>User identification code<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n
A response example is shown below:<\/p>\n
\n
{\r\n  \"continuation_token\": \"2017-04-13T06:58:48.121Z\",\r\n  \"items\": [\r\n    {\r\n     \"object_id\" : \"abc123\",\r\n     \"datetime\" : \"2017-04-13T06:58:48.090Z\",\r\n     \"ignition_status\" : \"UNKNOWN\",\r\n     \"position\" : {\r\n         \"altitude\" : 0,\r\n         \"direction\" : 0,\r\n         \"latitude\" : 0,\r\n         \"longitude\" : 0,\r\n         \"hdop\": 0,\r\n         \"satellites_count\" : 0,\r\n         \"speed\" : 0\r\n     },\r\n     \"device_inputs\" : {\r\n         \"digital_input_1\" : true,\r\n         \"digital_input_2\" : true,\r\n         \"digital_input_3\" : true,\r\n         \"digital_input_4\" : true,\r\n         \"power_supply_voltage\" : 0,\r\n         \"ibutton\" : \"xxxxxxxxxx\",\r\n         \"first_driver_id\" : \"xxxxxxxxxx\",\r\n         \"second_driver_id\" : \"xxxxxxxxxx\",\r\n         \"temperature_sensor_0\": 0,\r\n         \"temperature_sensor_1\": 0,\r\n         \"temperature_sensor_2\": 0,\r\n         \"temperature_sensor_3\": 0,\r\n         \"temperature_sensor_0_id\": \"xxxxxxxxxx\"\r\n     },\r\n     \"calculated_inputs\":{\r\n         \"mileage\" : 0\r\n     }\r\n    }\r\n  ]\r\n}<\/pre>\n<\/div>\n
All response fields than can be received with every type of parameter are described in the next table:<\/p>\n\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t
Name<\/th>Type<\/th>Description<\/th>Units<\/th>\n<\/tr>\n<\/thead>\n
continuation_token<\/td><\/td>Continuation token is received when requesting large amounts of records, for long periods, which exceeds the set records limit, the continuation token will be  displayed at the end of the response. It can be used afterwards to display the next set of records for the selected period. If no more records are available after the token, the response will return empty.<\/td>Datetime<\/td>\n<\/tr>\n
items<\/td>Array<\/td>Contains all parameters in accordance to the request<\/td><\/td>\n<\/tr>\n
object_id<\/td>String<\/td>Object identifier (external)<\/td>Text<\/td>\n<\/tr>\n
datetime<\/td>Date<\/td>Date and time point of coordinate generated in hardware
\nFormat: \"yyyy-mm-ddThh:mm:ss.sssZ\"
\n<\/td>		According ISO-8601<\/td>\n<\/tr>\n
ignition_status<\/td>Enum<\/td>Indicating if object has ignition on.
\n\"ON\" - Ignition on 
\n\"OFF\" - Ignition off
\n\"UNKNOWN\" - No data about ignition
\n<\/td>		ON- OFF <\/td>\n<\/tr>\n
position<\/td>Array<\/td>Contains all record GPS parameters<\/td><\/td>\n<\/tr>\n
latitude<\/td>Float<\/td>GPS coordinate - latitude value<\/td>Degrees<\/td>\n<\/tr>\n
longitude<\/td>Float<\/td>GPS coordinate - longitude value<\/td>Degrees<\/td>\n<\/tr>\n
altitude<\/td>Integer<\/td>GPS coordinate - altitude value<\/td>Number<\/td>\n<\/tr>\n
direction<\/td>Integer<\/td>Moving direction in degrees<\/td>0 = north, increasing clock-wise<\/td>\n<\/tr>\n
speed<\/td>Integer<\/td>Object moving speed<\/td>km\/h<\/td>\n<\/tr>\n
satellites_count<\/td>Integer<\/td>Number of visible GPS or GLONASS satellites(depends on device configuration) while generating record in device<\/td>Number<\/td>\n<\/tr>\n
device_inputs<\/td>Array<\/td>Container for parameters received from hardware<\/td><\/td>\n<\/tr>\n
power_supply_voltage<\/td>Integer<\/td>Object power supply voltage<\/td>mV<\/td>\n<\/tr>\n
ibutton<\/td>String<\/td>iButton or RFID card code of a driver assigned to a vehicle<\/td>Text<\/td>\n<\/tr>\n
hdop<\/td>Float<\/td>GPS coordinate precision<\/td>Number<\/td>\n<\/tr>\n
first_driver_id<\/td>String<\/td>TCO code of the first driver<\/td>Text<\/td>\n<\/tr>\n
second_driver_id<\/td>String<\/td>TCO code of the second driver<\/td>Text<\/td>\n<\/tr>\n
digital_input_1<\/td>Boolean<\/td>Configurated object or its equipment status
\ntrue - status = active 
\nfalse - status = inactive
\n<\/td>		True - False<\/td>\n<\/tr>\n
digital_input_2<\/td>Boolean<\/td>Configured object or its equipment status
\ntrue - status = active 
\nfalse - status = inactive
\n<\/td>		True - False<\/td>\n<\/tr>\n
digital_input_3<\/td>Boolean<\/td>Configured object or its equipment status
\ntrue - status = active 
\nfalse - status = inactive
\n<\/td>		True - False<\/td>\n<\/tr>\n
digital_input_4<\/td>Boolean<\/td>Configured object or its equipment status
\ntrue - status = active 
\nfalse - status = inactive
\n<\/td>		True - False<\/td>\n<\/tr>\n
temperature_sensor_0<\/td>Float<\/td>Temperature sensor data<\/td>\u00b0C<\/td>\n<\/tr>\n
temperature_sensor_1<\/td>Float<\/td>Temperature sensor data<\/td>\u00b0C<\/td>\n<\/tr>\n
temperature_sensor_2<\/td>Float<\/td>Temperature sensor data<\/td>\u00b0C<\/td>\n<\/tr>\n
temperature_sensor_3<\/td>Float<\/td>Temperature sensor data<\/td>\u00b0C<\/td>\n<\/tr>\n
temperature_sensor_0_id<\/td>String<\/td>Temperature sensor ID<\/td>Text<\/td>\n<\/tr>\n
calculated_inputs<\/td>Array<\/td>Container for parameters calculated in system from other parameters according to the configuration<\/td><\/td>\n<\/tr>\n
mileage<\/td>Float<\/td>Object driven distance (depends on object configuration)<\/td>km<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n
API endpoints, request parameters and responses can be previewed in \u201cSwagger\u201d through this link : https:\/\/api.fm-track.com<\/a><\/p>\n
\n
\u2039   <\/span> API <\/a><\/div> 
API \u0456\u0441\u0442\u043e\u0440\u0456\u0457 \u043a\u043e\u043e\u0440\u0434\u0438\u043d\u0430\u0442 \u043e\u0431’\u0454\u043a\u0442\u0456\u0432 v3   \u203a <\/span> <\/a><\/div><\/p>\n","protected":false},"excerpt":{"rendered":"
Object Coordinates History API main purpose is to output clients\u2019 object historical data (coordinates). Object Coordinates History API has two endpoints, thus there are two types of requests. The first type of request is for one object and a specific date and time. Only data recorded at the specified date and time is shown. Request … Continue reading API \u0456\u0441\u0442\u043e\u0440\u0456\u0457 \u043a\u043e\u043e\u0440\u0434\u0438\u043d\u0430\u0442 \u043e\u0431’\u0454\u043a\u0442\u0456\u0432<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":16492,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-17081","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/pages\/17081","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/comments?post=17081"}],"version-history":[{"count":6,"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/pages\/17081\/revisions"}],"predecessor-version":[{"id":17832,"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/pages\/17081\/revisions\/17832"}],"up":[{"embeddable":true,"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/pages\/16492"}],"wp:attachment":[{"href":"https:\/\/www.fmsdocumentation.com\/uk\/wp-json\/wp\/v2\/media?parent=17081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}