> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Token expiry rules

> How access-token expiry works in e6data - units, defaults, maximums, and enforcement.

Expiry is optional for both personal access tokens and service account keys, but recommended.

| Rule | Value |
| - | - |
| Unit entered | Days (in the Console) |
| Default | 90 days |
| Maximum | 3650 days |
| Never expires | Allowed (only with a rotation process in place) |
| Stored as | An RFC 3339 timestamp |
| Enforcement | Checked on every request |

When a token expires, requests return `401 Unauthorized` (`invalid or expired API token`). Expired tokens **cannot be extended** - create a replacement and revoke the old one.

Suggested expiries by use case:

| Use case | Suggested expiry |
| - | - |
| BI tool connection | 90 days - rotate quarterly |
| CI/CD pipeline key | 365 days - rotate annually or on team changes |
| Short-lived script | Hours to days |

## See also

* [Token lifecycle states](/platform/reference/tokens/lifecycle-states)
* [Create, use, rotate, and revoke tokens](/platform/tokens/create-rotate-revoke)
* [Token limits](/platform/reference/limits/token)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.