Device Token

Device Token

The secret key used between TagoIO and your device is called Device Token. An access from a device will only be granted with a valid device token. This token should be kept in secret and only be shared with those you trust.

Each time a device is created, the system automatically creates a device token.

The token information can be found by clicking on the reveal option. It’s possible to copy the token by clicking in the Copy token option.


Managing Device Tokens

Device tokens can be managed by going to the ‘Tokens’ section of the device. More than one token can be created for the same device. You can add permission, expiration date, serial number and verification code to a token.


Type of Permissions

  • Full - when using this token, the device will be able to send and read data
  • Write only - the device will only be able to send data
  • Read only - the device will only be able to read data

Expiration

This field defines the life of the token, it can be temporary or infinite (never expire).

Device Type

If you want just to create a token for HTTP requests, you probably won’t need to select a Device Type. But, if your device goes through another system before coming to Tago (which is normally referred as Middleware), you should select the type of device here. The device owner will be able to find your device on Tago and insert your data through this token. You will need to provide a Serial Number and, if necessary, the Verification Code as well.

If your hardware is not on the list, you can enter in contact with us and we will give you instructions on how to integrate your device and make it available in the list.

Serial Number and Verification Code

There are two advanced options that may be requested based on the type of device. Normally, the ‘Serial Number’ and the ‘Verification code’ are only requested by a device connected to a TCP or UDP servers - some examples are devices connected through Sigfox network or customized products. Look for the setup instructions that comes with the specific hardware device that you are trying to add

    • Related Articles

    • Account Token

      The secret key used between Tago and external applications are Account Tokens. Any access from an account will only be granted with a valid device token, so it is vital that this token be kept secret and only be shared with those you trust. All sort ...
    • Device Emulator

      The device emulator is a powerful tool for developers to send data to buckets as if it was sent by a real device. The emulator is intuitive and requires just a few clicks to validate and send your data package. To access the device emulator, go to ...
    • Device List Widget

      The Device List widget is a table that dynamically populates with information about your devices, such as names, tags, configuration parameters, and IDs. It can't access devices' data, however. 1. Editing the device list It works as a dynamic table, ...
    • Sending Data to Device

      TagoIO supports two-way communication with all your devices so that it can send and receive data. There are some options for you to send data from your application to the device. Among the methods, you can use: Publish to MQTT Post data to a ...
    • Using the Device Emulator

      If you want a quick way to send data to your applications, but you don't have your hardware device available at the moment, or you simply need to send data to debug your applications, you can do that very easily using the Device Emulator. To access ...

    Webinar Announcement - Image Only

        Take a look at our updated roadmap here!
          What would you like to see on TagoIO?

            Future and past Webinars