- Scoped access: read, write and reveal secret are separate permissions. A reconciliation script, for example, only needs “Usage & personal records · Read”.
- Expiry: 30 days by default. You can also pick 90, 180 or 365 days, a custom date, or never. We recommend a longer period.
- IP allowlist: IPv4, IPv6 and CIDR are supported, and the allowlist can’t be changed after creation. Leave it empty while you test, then create a separate production token with an allowlist once everything works.
- Count: up to 20 per account. Use one per script, so a leak means deleting just that one.
ACCESS_TOKEN_LEGACY_RETIRED. We’ll review usage and may extend the date, but we recommend switching to a personal access token now. You only need to replace the value in the Authorization header. Your code stays the same.
See What Is a Personal Access Token and How Do I Replace the System Token? for setup steps, the permission table and common errors. The Balance Query, Log Query and Token Management API docs have been updated.
← Back to Live Updates · 📚 Monthly archive