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:
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
How access-token expiry works in e6data - units, defaults, maximums, and enforcement.
| 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 |
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 |