The secret key used between Tago and your device is called Device Token. Any access request 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.
Full - when using this token, the device will be able to send and receive dataWrite only - the device will only be able to send dataRead only - the device will only be able to read data
This field defines the life of the token, it can be temporary or infinite (never expire).
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.