Due to security measures, each user must individually create their Access Token, which acts like a password. Administrators are not authorized to create Access Tokens on behalf of other users.
To obtain an API Token, please follow these steps:
Visit Atlassian API Tokens.
If you're not logged into your Atlassian Account, you'll need to sign in first. After logging in, navigate to the 'Security' section and then proceed to 'Create and manage API tokens' to continue with your task.
Select the ‘Create API token’ button.
In the pop-up dialog, provide a clear and memorable Label (we recommend using the app's name) for your token and click ‘Create’.
Use the ‘Copy’ option to copy the token, and then save it into your script or another secure location for reference.
Important! Make sure you see the confirmation 'API token copied to clipboard' before closing the pop-up. Once the pop-up is closed, you won't be able to retrieve the token again. If you forget to copy it, you'll need to create a new one.
Now navigate to the app within your Confluence Cloud instance.
In the left-side menu go to ‘Tokens’ ➡️ ‘Confluence API Token’.
Input Your Conflunce email and then paste the API Token you copied earlier into the designated field. Once done, click 'Validate & Save' to complete the process.
This step is crucial for authenticating and saving your API Token in the system.
Once the warning sign turns orange, it indicates that your API Token has been successfully saved in the system. You can now use this token as your credential in the BI tool of your choice for secure data operations.
A single Confluence API Token can be used to log into multiple BI tools. There's no need to create separate tokens for each tool, simplifying the process and enhancing user convenience in managing various BI integrations.
To delete old API tokens, use the 'Revoke' button on the same page where they were created. Once a token is revoked, it becomes invalid and can no longer be used for importing Confluence data into your BI tool. This ensures that only current, valid tokens are in use for data security purposes.
Still have questions? Feel free to reach out to us for any additional information or to request new features!