> 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/authorization.md).

# Authorization

The Vulcan API uses Bearer token authentication. Tokens are issued by your DataOS platform and must be included in every request.

## How It Works

Unlike OAuth 2.0 flows with redirect URIs, DataOS uses a direct token model. Your administrator or CI/CD pipeline generates a DataOS API token for a user or service account. That token is passed in the `Authorization` header of every API call.

```
Authorization: Bearer <dataos-api-token>
```

## Token Scopes and Access

Tokens inherit the permissions of the DataOS user or service account they belong to. Access to a data product is determined by the tenant and resource configuration. If a token lacks permission for a resource, the API returns `403 Forbidden`.

## Using Tokens with the SDKs

Pass the token once at construction time — the SDK attaches it to every request automatically:

```python
# Python
client = VulcanClient(fqdn="...", dp_name="...", access_token="<token>", tenant="...")
```

```typescript
// TypeScript
const client = new VulcanClient({ fqdn: "...", dpName: "...", accessToken: "<token>", tenant: "..." });
```

> **Security:** Store tokens in environment variables or a secrets manager — never hardcode them in source files or commit them to version control.

## Postman

Set the `access_token` collection variable once. The collection-level Bearer auth applies it to every request automatically — no need to set it per 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/authorization.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.