You can now create multiple API tokens for your workspace instead of relying on a single one. Each token has its own name and its own expiry, and can be managed independently of the others.
What this means:
- Rotate tokens without downtime. Create a new token, switch your integration over to it, then delete the old one — nothing breaks in between.
- Use a separate token for each need. Give every integration, script or environment its own token, so you always know what is using which.
- Mix long-lived and short-lived tokens. Keep a permanent token for a production integration, and hand out one that expires in a few days for a quick test or a temporary job.
- Limit the impact of a leaked token. Regenerating or deleting one token leaves all your other tokens working.
How it works:
- Each workspace can have up to 10 active tokens.
- Set an expiry in days when you create a token, or leave it empty for a token that never expires.
- Every token shows when it was created, when it was last used and when it expires, so unused tokens are easy to spot and clean up.
- As before, a token's value is shown only once, when it is created or regenerated — copy it and store it somewhere safe.
Existing tokens keep working exactly as they did. No changes are needed to your current integrations.