New Authorization method
TagoIO Team
We updated the way integrations with services like those with LoRaWAN and Sigfox are done by adding Authorization.
The verification-code is being deprecated for the integrations, the field is no more available in the device setup. If you already have a device using verification-code it will still work. But, for newer devices you must follow the new documentation the explains how to generate an Authorization.
Authorization gives access to all devices from given connector integrated with your account. If necessary, Authorization is easy to change, and it makes the process of creating devices much fast and easier.
Check out the Authorization documentation here.
Note: Authorization is different from device-token.
Use authorization only when integrating with external services, such as LoRaWAN or Sigfox. Continue using Device-Token when using HTTPS or MQTT to connect directly with TagoIO APIs.
TagoIO Team.
We updated the way integrations with services like those with LoRaWAN and Sigfox are done by adding Authorization.
The verification-code is being deprecated for the integrations, the field is no more available in the device setup. If you already have a device using verification-code it will still work. But, for newer devices you must follow the new documentation the explains how to generate an Authorization.
Authorization gives access to all devices from given connector integrated with your account. If necessary, Authorization is easy to change, and it makes the process of creating devices much fast and easier.
Check out the Authorization documentation here.
Note: Authorization is different from device-token.
Use authorization only when integrating with external services, such as LoRaWAN or Sigfox. Continue using Device-Token when using HTTPS or MQTT to connect directly with TagoIO APIs.
TagoIO Team.
