Application tokens allow you to interact with a single application at a scope level you define. Using an application token, users can create, read, update or delete any child resource of the parent application – as well as the application itself.
You can view the the API tokens for an application by choosing
API Tokens in the Application subnavigation.
The list of application tokens includes the token’s name, a summary of its scope, its creator (which may be yourself, another member of your organization or even another API token) and the token’s expiration date.
Application API tokens can be added to your application by using the
Add Application Token button on the
API Tokens page. Token setup requires four pieces of information:
The token’s name is required, and it is simply for display purposes and is required to help you differentiate your user tokens. The token’s name in no way affects its functionality. Optionally, a longer description may be provided for additional information on the token.
By default, the ”Never expires” option is selected. This means that by default user tokens never expire. Optionally, if you would like a user token to expire, choose ”Expires at …” and then set a future date/time after which requests using this token should no longer be accepted. The default expiration date with this option is one year from creation.
Note: the expiration date cannot be changed after token creation. If the expiration date passes while the token is in use, you will have to generate a new token and replace it within your authentication requests.
There are four options for setting the token’s scope …
All permissions allows the token to create, read, update and delete sub-resources of the application, including (but not limited to) devices, device state reports, workflows, additional application API tokens and the application itself. Losant resources and actions added in the future will automatically be accessible using an “All permissions” token.
Read only allows the token to read – but not modify – any application sub-resource. This includes reading (but not reporting) device state and commands, as well as data queries, devices, workflows and the application itself. Future Losant resources’ “read” actions, as well as new “read” actions added to existing resources, will automatically be accessible using a “Read only” token.
CLI developer permissions allows the token to read and write to all resources managed by the Losant CLI. Future Losant resources’ “CLI” actions, as well as new “CLI” actions added to existing resources, will automatically be accessible using a “CLI developer permissions” token.
Custom … allows for selecting specific resource / action combinations from the Losant REST API that the token should be allowed to access. Choosing this option reveals a list of all application-specific API calls in the Losant Platform, each of which may be individually added to the token’s scope. For example, to only allow the querying of device data for use in a third-party dashboard tool, you might select only the checkboxes shown in this screenshot …
The checkboxes next to the resource names will automatically check or uncheck all actions under that resource. However, checking such a box does not provide the token access to any new actions that may be added under that resource in the future. If a new action is added under a resource, and you would like your token to have access to that action, you will have to generate a new token.
Note that a token’s scope cannot be changed after token creation. If you find you need additional permissions not allowed by the token, you will have to create a new token. Likewise, if you would like to revoke permissions originally supplied to a token, you will have to delete the token and create a new one with the desired scope.
Create Application Token, the newly created token will be displayed. You will either need to copy it to a secure location or download it to a file on your computer.
IMPORTANT: Losant does not store API tokens and they cannot be recovered or regenerated if lost. If you fail to save your token before closing the modal, you will have to generate a new application API token.
When you’re finished, check the
I have copied my application token to a safe place box and click
To temporarily deactivate an application API token …
- Toggle the switch in the list view, OR
- From the token’s detail page, select the “Inactive” radio button under the “Status” label and save the token.
If a token has expired, is no longer needed or is thought to have been compromised, you may permanently delete it by:
- Clicking on the
Deleteicon in the token list, OR
- Clicking the
Delete Application Tokenbutton on the token’s detail page
API tokens with appropriate permissions can be used to create, access, modify, and delete dashboards scoped to the same application using the Application Dashboard and Application Dashboards API endpoints. Tokens cannot be used to create, access, modify, or delete a dashboard using the regular Dashboard or Dashboards endpoints.