Manage API Tokens
API tokens authenticate users when they try to retrieve information from Routing Director by using REST APIs. By using API tokens, users can avoid authentication for each request that 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.
| Field | Description |
|---|---|
| Name* |
Name of the API token. |
| Role* |
Role to which the API token is applicable:
|
| Key |
The key auto-generated to identify the application the user is using to access the resources. |
| Tags |
Tags assigned to the API token. If there is more than one tag assigned to the API token, an integer is present next to the displayed tag. For example, +2 in the Tags column indicates that there are two more tags in addition to what is currently listed. You can hover over the integer to view the additional tags assigned to the API token. To assign a tag, edit the API token. See Edit an API Token. |
| Access Control Profile |
Assign one or more access control profiles to grant access to resources (devices, service instances, and perform tagging operations). If an access profile does not exist, click the +Add Access Control Profile link to create a new profile and assign it to the Network Admin user. See Add Access Control Profiles. |
Add an API Token
Edit an API Token
Delete an API Token
Users using API tokens to access Routing Director resources cannot access the resources after the API token is deleted.