> For the complete documentation index, see [llms.txt](https://docs.akkio.com/akkio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akkio.com/akkio-docs/concepts/authentication.md).

# Authentication

Making calls to the Akkio API is authenticated via an API Key. You can find your API Key near the bottom of the [Team Settings](https://docs.akkio.com/akkio-docs/settings/team-settings) of the main website.

In order to successfully use endpoints, supply an `X-API-Key` header set to your API Key with all requests.

***

#### HTTP 401[​](https://api-docs.akkio.com/concepts/authentication#http-401) <a href="#http-401" id="http-401"></a>

A HTTP 401 generally indicates we were unable to successfully authenticate you to the platform as a whole with the provided credentials. Please confirm:

* You have provided an API Key in the `X-API-Key` header
* Your API key is correct
* Your API key is being sent with no leading or trailing spaces

#### HTTP 403[​](https://api-docs.akkio.com/concepts/authentication#http-403) <a href="#http-403" id="http-403"></a>

A HTTP 403 generally indicates that you are trying to access a resource that the organization linked to your API Key does not have access to. Please ensure you are using the API key of an organization that has access to the resource in question.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.akkio.com/akkio-docs/concepts/authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.