ironbee login creates so the CLI can send session data as you. Each token is tied to your user and account, and you manage them independently of the shared account API key.
What you see
Each token in the list shows:- Name: the label set at creation (the CLI defaults this to your machine’s hostname)
- Prefix: the first characters of the token, followed by
…; the full value is never shown again after creation - Created: when the token was issued
- Expires: the expiry date, or “Never expires” for non-expiring tokens
Create a token
Click Create token, give it a name, and choose an expiry (30, 60, 90, 180, or 365 days, or no expiration). The full token is shown once on the next screen, copy it somewhere safe, because it cannot be retrieved later. Most people never create tokens here by hand;ironbee login mints one for you. Create one manually when you need a token for a specific tool or a custom expiry.
Revoke a token
Click Revoke next to any token to disable it immediately. Anything still using that token can no longer authenticate.You can hold at most 10 access tokens at a time, including expired ones you have not removed. If you hit the limit, revoke one here before creating or minting another. This is also what frees up
ironbee login when it reports the limit.Tokens vs the account API key
| API token | Account API key | |
|---|---|---|
| Identifies | You | The account |
| Created by | ironbee login or this page | Generated with the account |
| Used for | Interactive CLI use | CI and machine-to-machine, like the GitHub Action |
| Managed on | This page | The Account page |