If you've received an email from Rewind asking you to refresh your Jira API token, this article walks you through how to revoke the old token, create a new one, and update it in Rewind. This token is used specifically for Jira Automation access and needs to be refreshed every 365 days, which is the longest expiration period Atlassian allows.
Before you begin
Before starting, confirm the following:
- Before generating a new token, confirm that you're logged in to Atlassian as the user who originally installed Rewind. The token inherits the permissions of the account that created it, so using a different account may result in incomplete backups. For more information on the permissions required for Jira Automation, see Atlassian's documentation on permissions required for Jira Cloud Automation rules →
- You have access to the Backup configuration tab in the Rewind Account settings.
Steps to refresh your Jira API token for Rewind
- Go to your Atlassian API tokens page.
- Locate the token you want to replace and select Revoke, then confirm. The token stops working immediately upon revocation.
- On the same page, select Create API token, enter a descriptive label, and set the expiration date to 365 days.
-
Select Create, then Copy to clipboard.
Important: Save the token somewhere secure immediately — it can't be retrieved after you close this screen. - Go to app.rewind.com, navigate to Account settings Backup configuration, and paste in the new API token.
Note: Atlassian API tokens expire after a maximum of 365 days. This token is used specifically for Jira Automation access, so you'll need to repeat these steps every 365 days to keep your Jira Automation backups running. For more information on managing API tokens, see Atlassian's API token documentation →
Need help?
If you have questions or need assistance, contact help@rewind.com or submit a request.