With organizational tokens, Ubidots admin accounts can create TOKENS and provision devices specifically to a predetermined organization. With them, you'll avoid having to assign each device to an Organization within your App's architecture.

Before starting, let's go over some context first. To keep Organizations and Devices separated and organized correctly, Ubidots uses a two-tier device identifier model—TOKENS and Device Labels. First, the Ubidots TOKEN is the key for each piece of hardware to send data to Ubidots; every Ubidots account has a parent TOKEN. With this guide you'll learn how to create a subtoken called "organization token", the key for each Organization's data within your application's architecture. The second tier for Ubidots device identification are Device Labels, which are unique identifiers per device, across a single Ubidots Administrator's account. Using both the TOKEN and Device Label, Ubidots users keep their data associated with the right hardware data in the right places.

In the below diagram we can see the quadrants 3 and 4 have an incorrect logic and any attempt to send data through these structures will be rejected. In quadrant 3 we see a repeated Device ID, which will be rejected as it has been claimed by Organization 1 already. In quadrant 4 we see a rejection because the Organization TOKEN does not align with the intended Organization 4.

To create a TOKEN for an Organization, go to "Users" → "Organizations". Once there, follow these steps:

Once finished, click on the "save" button at the lower right corner of the modal.

Now that you have the organization TOKEN created, you can manage devices and variables using Ubidots API.

1. The POST request below automatically creates a new device with a variable assigned to the organization of the new TOKEN returned.

Structure of a POST request:

Example of a POST request:

As you can see in the example request above, we are assigning the device label "new-device" with a variable "humidity" to the organization of the TOKEN returned.
​
​Resulting command response:

Now that we have a successful response from the server, go to the Device section of your Ubidots application where you'll see the device created for the Organization.

As you can see above, the device is automatically assigned to the organization of the TOKEN_RETURNED.

NOTE: If the device label assigned in the request is already created in the Organization, the variable set will update anytime data is sent from that device.
​
2. As described previously, if both the TOKEN and Device ID are not properly ordered, the POST will be rejected.
​
Using the TOKEN_RETURN, we try to update a device that has already been assigned to another Organization by the device ID (Quadrant 3 in the illustration above).

Resulting response:

As you can see, the above request is rejected because the device ID has already been provisioned to another organization.
​

To access and manage an Organization's Tokens, simply go to the "Tokens" section of the Organization's settings.

Other users also found useful...