Application tokens
Application tokens let your software access the emnify REST API without personal sign-in credentials. To manage them, go to Integrations and then Application tokens.
A Workspace can hold up to 300 application tokens. The counter next to Add token shows how many your Workspace has. When you reach the limit, Add token is turned off until you delete a token you no longer use.
Only users with the Admin role see Add token and the edit and delete buttons.
Add a token
Go to Application tokens and click Add token.
In Name, enter a name that identifies the token, such as the integration that uses it.
The name can have 2 to 64 characters: letters, digits, spaces (including the full-width space), and - _ . : / ( ) [ ] @ + #, as well as full-width （ ）.
In Role, select the role that sets what the token can access. For help choosing, see Assign a role to an application token.
In Set expiry date, keep the default of one year from today or choose another date. The date must be at least tomorrow and less than 10 years from today. The token expires at the end of that day, at 23:59:59 UTC.
You can only see and copy the token in the Token created dialog. After you close it, you can’t retrieve the token again.
In the Portal, you can only change a token’s name after you create it. The expiry date and IP restriction are fixed for the life of the token. To change them, add a new token, move your integration to it, and then delete the old one.
Assign a role to an application token
Every application token has exactly one role, and the token can only do what that role allows. It works the same way as a user’s role: a token with the Observer role can read data but can’t change it. You choose the role when you add the token.
In the Role list, you can choose one of the following:
- Admin, User, or Observer. For what each role allows, see Roles and permissions.
- A custom role that your Workspace created, if custom roles are available to you.
The Support role can’t be assigned to a token.
Choose the most limited role that fits the integration. If you select Admin, the Portal warns you that anyone with the token has full access to your Workspace if it leaks.
Tokens created before roles were available, and tokens created with the v1 application token API, have the Administrator role. To give such a token a more limited role, add a new token with that role, or update the token through the API.
View your tokens
The Application tokens table lists the active tokens in your Workspace. By default, it shows these columns:
The Created (UTC), Token ID, and Last used IP address columns are hidden by default. To show, hide, or reorder columns, click the Table settings icon at the end of the table header row. For details, see Customize tables in the emnify Portal. Click a column header to sort the table by that column.
Edit a token
The Edit token dialog also shows the token’s details, which you can read but not change:
- Status & usage: when and from which IP address the token was last used, and when it expires.
- Access: the assigned role and the IP restriction.
- Origin: when and by whom the token was created and last edited, and the token ID.
Delete a token
Deleting a token is permanent. Integrations that use the token can’t authenticate with it anymore, so add a replacement token first if you still need access.