> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/interfaces/apis/concepts/access-token.md).

# Access Token

Your DataOS access token is the credential that proves your identity to the API. Every request must include it.

The token is a short-lived string that grants access to the data product's endpoints. Include it in every request using the `Authorization` header.

**Header format:**

```
Authorization: Bearer <your-dataos-access-token>
```

> **Token expiry:** Tokens expire periodically. If you receive a `401 Unauthorized` response, request a new token from your DataOS administrator or token endpoint and retry.

Never share tokens or commit them to source control. Rotate them if you suspect exposure. The SDKs accept the token at client construction time and attach it automatically to every request.


---

# 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://v2.dataos.info/references/interfaces/apis/concepts/access-token.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.