Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Manage API Tokens

API tokens use REST APIs to authenticate users when they try to retrieve information from Juniper Mist Routing Assurance. By using API tokens, users can avoid authentication for each request they make. An API token provides visibility into the resources accessed by a user, enabling you to have better control over access to resources.

Table 1 lists the parameters for configuring API tokens.

Table 1: Parameters to Configure API Tokens
Field Description
Name Name of the API token.
Role Role to which the API token is applicable:
  • Super User

  • Network Admin

  • Observer

  • Helpdesk

Key The key auto-generated to identify the application the user is using to access the resources.

Add an API Token

To add an API token for a role:
  1. Click Organization > Settings in the navigation menu.
    The Organization Settings page appears.
  2. Click the Create Token icon.
    The Create API Tokens page appears.
  3. Enter values by following the guidelines in Table 1.
  4. Click Generate.
    The API token is populated in the Key field.
  5. Click Close to return to the Organization Settings page.

Edit an API Token

To edit an API token:
  1. Click Organization > Settings in the navigation menu.
    The Organization Settings page appears.
  2. Click the API token that you want to edit.
    The Edit API Token page appears.
  3. Edit the name, role, and site access by following the guidelines in Table 1.
  4. Click Save.
    You are returned to the Organization Settings page, where you can verify the changes in the API Tokens table.

Delete an API Token

To delete an API token:
Note:

Users using API tokens to access Juniper Mist Routing Assurance resources cannot access the resources after the API token is deleted.

  1. Click Organization > Settings in the navigation menu.
    The Organization Settings page appears.
  2. Click the API token that you want to delete.
    The Edit API token page appears.
  3. Click Delete.
    You are returned to the Organization Settings page, where you can verify that the API token is not listed in the API Tokens table.