In Juniper/Mist you can create 2 types of API tokens. This article is specific to Org Tokens and their benefits.
- Org Token
-
- Token persists under the org
- Token is not bound to any specific user, meaning the access does not depend upon the user’s access to the org
- Token can only be used for that specific org
- Supports N org tokens, which can have different privileges
- Rate limiting is done by the individual token. So if OrgToken1 consumes 5000 API calls and hits the rate limit, OrgToken2 is not impacted
- User Token
-
- Token persists under the user account
- Token is bound to the specific user, meaning the access directly depends upon the user’s access to the org
- Token can be used for any MSP/Org that the user has access to
- Supports N tokens, which all have the same privilege as the user account
- Rate limiting is tied to the account. So if UserToken1 consumes 5000 API calls and hits the rate limit, UserToken2 AND account log in to the GUI is impacted
Navigate to Org/Settings
Lower down on the page you have the ability create an ORG API Token.
Define the permissions for this token.
