MTS API Migration Guide

introduction this guide helps you migrate from the motion tracking service apis to be deprecated by the end of march to the current api versions migration will ensure the apps continue to work seamlessly when older apis are deprecated r ecommended steps for migration identify usage audit your usage to locate all places you call the deprecated mts apis this is crucial to know what needs to change take note of differences review the api documentation to understand the key differences in requests/responses between the old and new api version update endpoints update the endpoints your application calls to use the new apis modify payloads based on the documentation, modify request/response payloads to align with the new api spec test thoroughly be sure to test end to end to detect any issues early verify that expected data is still returned apis sunset date sunset date older apis will be deprecated by end of march 2024 trace put /mts/track/{trackname}/traces get /mts/track/{trackname}/traces put /mts/track/{trackid}/traces get /mts/track/{trackid}/traces get /mts/devices/{deviceid}/apps/{app}/trace put /mts/devices/{deviceid}/apps/{app}/trace missing sequence numbers get /mts/track/{trackname}/missing sequence get /mts/track/{trackid}/missing sequence get /mts/devices/{deviceid}/apps/{app}/missing sequence snapped distance get /mts/track/{trackname}/snapped distance get /mts/track/{trackid}/snapped distance get /mts/devices/{deviceid}/apps/{app}/snapped distance geofences post /mts/geofences/ put /mts/geofences/{geofenceid} delete /mts/geofences/{geofenceid} get /mts/geofences/{geofenceid} put /mts/geofences/{geofenceid}/devices get /mts/geofences/{geofenceid}/devices get /mts/geofences/{geofenceid}/devices/{deviceid} put /mts/geofences/{geofenceid}/devices/{deviceid}/unsubscribe post /mts geofences/ put /mts geofences/{geofenceid} delete /mts geofences/{geofenceid} get /mts geofences/{geofenceid} put /mts geofences/{geofenceid}/devices get /mts geofences/{geofenceid}/devices get /mts geofences/{geofenceid}/devices/{deviceid} put /mts geofences/{geofenceid}/devices/{deviceid}/unsubscribe subscription post /mts/pubsub/devices/{deviceid}/subscription get /mts/pubsub/devices/{deviceid}/subscription/{subscriptionid} put /mts/pubsub/devices/{deviceid}/subscription/{subscriptionid}/deactivate post /mts pubsub/devices/{deviceid}/subscription get /mts pubsub/devices/{deviceid}/subscription/{subscriptionid} put /mts pubsub/devices/{deviceid}/subscription/{subscriptionid}/deactivate track apis the following apis have been categorized by sim, gps, and mobile phones the previous apis will be deprecated by the end of march older apis to be deprecated in march 2024 post /mts/providers/tracks get /mts/providers/tracks get /mts/providers/tracks/{externalrefid} get /mts/providers/tracks/{trackid} put /mts/providers/tracks/{trackid} put /mts/providers/tracks/{externalrefid} new apis developers need to migrate to these new apis post /mts/sim/tracks get /mts/sim/tracks get /mts/sim/tracks/{trackid} put /mts/sim/tracks/{trackid} get /mts/sim/tracks/{trackname} put /mts/sim/tracks/{trackname} post /mts/smart phone/tracks get /mts/smart phone/tracks get /mts/smart phone/tracks/{trackid} put /mts/smart phone/tracks/{trackid} get /mts/smart phone/tracks/{trackname} put /mts/smart phone/tracks/{trackname} post /mts/gps module/tracks get /mts/gps module/tracks get /mts/gps module/tracks/{trackid} put /mts/gps module/tracks/{trackid} get /mts/gps module/tracks/{trackname} put /mts/gps module/tracks/{trackname}