Skip to main content
Authorization tokens can be created by users and administrators to provide fine-grained access control to resources (channels) or scopes when using the API or CLI. These tokens can be used in place of username-based authentication, particularly for third-party applications or automation tools. This topic provides guidance on the following actions:

Understanding tokens

Scope-based

Scope-based tokens give the token holder permission to take specific actions. It is possible to create private tokens with a specific set of scopes.

Resource-based

Resource-based tokens provide access to specific resources. Channel group permissions granted by the token will determine what actions the user is allowed to take.

Understanding scopes

In our model, scopes are represented as a concatenated string, like so: Resource:Action
Some features in the table below may contain “(by user with manage permissions)”, like in the feature associated with channel:edit in the third row down, for example. This means the token has a role with a corresponding permission level (in this case, manage) for a specific resource (in this case, channel).
Italicized items in table are under development.

Listing the available authorization scopes

Via the API
Via the CLI

Listing the user authorization tokens

Via the API
Via the CLI

Create a new user authorization token

Via the API
Via the CLI

Removing a user authorization token

Via the API
Via the CLI