> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/data-warehouse/introduction/access-and-authentication.md).

# Access and Authentication

> **Important:** These endpoints live on the internal Commerce API and are **not reachable directly by external clients**. Every external request goes through Omnitron.

External clients reach these endpoints through the Omnitron remote proxy:

```
https://{omnitron_url}/api/v1/remote/{channel_id}/data-warehouse/  ->  proxies to  ->  https://{commerce_url}/api/v1/data-warehouse/
```

A request sent to `https://{omnitron_url}/api/v1/remote/{channel_id}/data-warehouse/baskets/baskets/` is proxied to `https://{commerce_url}/api/v1/data-warehouse/baskets/baskets/` on the internal Commerce API. The `{channel_id}` in the proxy path identifies the sales channel.

Authenticate with a token sent in the `Authorization` header, in the form `Token <your-token>`. The token requires a staff (admin) account. A token issued by another system is rejected.

#### Common Access Errors

| Status             | Meaning                                                     | Resolution                                |
| ------------------ | ----------------------------------------------------------- | ----------------------------------------- |
| `401 Unauthorized` | The token is missing, invalid, or issued by another system. | Send a valid token.                       |
| `403 Forbidden`    | The token belongs to a user without administrator rights.   | Use a token from a staff (admin) account. |


---

# 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://apidocs.akinon.com/commerce-openapis/data-warehouse/introduction/access-and-authentication.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.