Company admin token generation

To create a TMY data request, a user with Company admin role needs to generate a token for communication. In addition to other necessary information, the token contains information about the used subscription and user (for the case of user tokens). Based on the valid token information request is further processed.

The system supports the generation of two types of tokens as described in the “TMY introduction section” :

  • User tokens – tokens are directly connected with the user for whom it is generated

  • Userless tokens – anonymous tokens but with the same purpose as “User tokens”


When token is generated, it must be saved by user - generated token cannot be retrieved from database after the window for token generation is closed

User tokens

Token generation

To generate a user token, a user with Company admin role needs to first assign a user to the subscription. Once the user is assigned, the system will activate the option to “Generate token” for the selected user. By selecting this option, the system displays a modal window with the generated token. Admin can either copy token to clipboard or download the token in CSV format. The generated token cannot be retrieved again, thus it is important to store it before closing the modal window with the generated token.

Figure 5 - User activation, token generation

Note: When a user is removed from the company or API Subscription, all user’s tokens are deleted.


Edit generated tokens

For each assigned user, the user with Company admin role can generate multiple tokens. The “Edit tokens” option is displayed when at least one token was already created.

Figure 6 – User tokens actions

Tokens overview

Company admin can manage generated tokens through the overview page that is displayed via the “Edit tokens” option



Userless tokens

Userless tokens work on the same principle as user tokens. However, since these tokens are not connected with any user, it is possible to generate them without the necessity of user activation. It brings a small drawback – it isn’t possible to identify, who/whose token was used for TMY data generation. (It is possible to track which token was used for the action).