Track Device Variables

variables are sent as a json object , where parameter is the variable name and value is the value of the variable, e g "variables" { "some variable name" "some value", "another variable name" "another value" } if a variable already exists on the device, its value will be overwritten device variables can also be set during activation by providing a variables parameter in the activation payload, with the same syntax as described on this page for more details see activate license (online method) docid\ mt2ygm6cjzh2bumu gfww , deactivate bundle (offline method) docid\ ucxi3f0ly0ysvouqhh8lf schema request body type trackdevicevariablesrequestbody = { // required parameters product string, hardware id string, variables { \[key string] string | number | boolean, } // required for key based products license key string, // required for user based products username string, } json schema response body type trackdevicevariablesresponsebody = ({ variable string, value string | number | boolean, device id number, created at number, // unix timestamp in milliseconds, e g 1737128752745 })\[]; json schema license authorization method there are two types of product licenses based on how the client application authorizes itself to interact with a license key based product licenses client interactions with the license have to be authorized using a license key user based product licenses the license has a corresponding "license user" instead of a license key client interactions with the license have to be authorized using a username errors if an error occurs, the response will have an http status code of 400 or higher, and the response body will contain an error description in the following format { status number, code string, message string } json schema { "$schema" "https //json schema org/draft/2020 12/schema", "type" "object", "properties" { "status" { "type" "number" }, "code" { "type" "string" }, "message" { "type" "string" } }, "required" \[ "status", "code", "message" ], "additionalproperties" false } list of exceptions unknown product (400) provided product was not found license not found (400) license with the provided license user not found license not active (400) the license is not active license not enabled (400) the license is not enabled device not found (400) an active device matching the hardware id not found blacklisted (400) this device is blacklisted