About this Page
This page explains the temporary use of unscoped API tokens for specific configuration backups and our roadmap to transition to Forge authentication as public APIs become available.
Are Service Account Tokens Supported?
-
Revyz uses Atlassian API tokens to back up specific configurations (like automation rules, ScriptRunner configuration, and asset field context). These are internal APIs, and the scopes for them are not defined.
-
Since these internal APIs cannot be authenticated by the service account, we do not support it yet.
-
Therefore, users are requested to create the API token without scope and create an API token from the account of a user who is an admin.
How to Create the Required API Token?
Please refer to our dedicated guide for step-by-step instructions.
Find the complete Add Atlassian API Token Guide here.
Note: It should be noted that the use of the internal APIs is a "stop-gap arrangement" until Atlassian offers public APIs for these use cases. For Automation rules, we should soon switch from internal APIs to public APIs after which we will use the Forge authentication.