> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/token-reference/token-expiry-rules.md).

# 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](/query-engine/reference/token-reference/token-lifecycle-states.md)
* [Create, use, rotate, and revoke tokens](/query-engine/guides/security/access-tokens/create-use-rotate-revoke.md)
* [Token limits](/query-engine/reference/limits-and-quotas/token-limits.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/reference/token-reference/token-expiry-rules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.