MTS APIs

mts apis onboarding a new device to onboard a new device, send a post request with the device's unique id this allows the device to start sending trace data via the mqtt broker or api onboard a new device onto mts to start sending trace data via mqtt broker or api use the post api to send data; ensure the hardware id is unique for every device update trace data the https //docs getos1 com/reference/insert trace data using trackname api is used to insert trace data to mts you can insert trace data using either https //docs getos1 com/reference/insert trace data using trackname or https //docs getos1 com/reference/insert trace data using trackid get trace data the https //docs getos1 com/reference/get trace data api fetches trace data for a specific device within a specified time range using the https //docs getos1 com/reference/get trace data using trackname or https //docs getos1 com/reference/get trace data using trackid get missing sequence numbers the https //docs getos1 com/reference/get missing sequence numbers using trackname api fetches missing sequence numbers for a specific trackid and trackname and in between the provided time deregister device the https //docs getos1 com/reference/deregister device api is used to deregister devices in mts by passing the isactive parameter in the body get all devices the https //docs getos1 com/reference/get all devices api returns all devices pertaining to a specific tenant id