Create new task.

required subuser rights: task_update


name description type
task <task> object without fields which are IGNORED JSON object

Minimal JSON object to create a new task must contain:

"tracker_id": 22, //optional, if the field is specified then the task will be assigned to the employee associated with the tracker, otherwise it won't be assigned to anybody
"location": { //area (circle geofence), entering and leaving of geofence will be controlled
"lat": 56.83717295, //latitude
"lng": 60.59761920, //longitude
"radius": 150 //radius in meters
"label": "Name", //task name, length 1-200 characters
"description": "Description example", //task description, length 0-1024 characters
"from": "2014-02-03 04:05:06", //start date of the interval - when the specified location has to be visited (in the user's time zone)
"to": "2014-03-04 05:06:07"//end date of the interval - when the specified location has to be visited (in the user's time zone)

task/create(..) call returns the identifier of the created task in the form of JSON:

"success": true,
"id": 222


"success": true,
"id": 111 //id of the created task

Note: The “id” parameter is unique, it is automatically generated by the server when you create a task. Therefore, if you call task/create (..) two times with the same parameters, every time the new task will be created. These two tasks will differ only by id. Respectively, if the created task has to be connected to a certain record in external system, you have to remember the id of this record to use it in future when you want to change/delete the associated task in our system.


  • 201 – Not found in database (if task.tracker_id is not null and belongs to nonexistent tracker)
  • 236 – Feature unavailable due to tariff restrictions (if device’s tariff does not allow usage of tasks)

If you have more questions please contact our support team

Contact Us

USA: +1 858 815 9045

Mexico: +52 334 1642158

UK: +44 808 1641499

France: +33 644 605141

Germany: +49 157359 88250

Russia: +7 495 317 1622

Log in