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

# Authentication

Requests to the API is authorized using an access token that should be specified in the `Authorization` header with the value `Bearer <access token>` , where `access token` is an api key obtained from the IntServ Access portal.

Example:

`Authorization: Bearer <access token>`

There are mainly two different types of access tokens that can be used: *Integration API Key* and *App API Key.* Which type of access token to use depends on the context of the request and is described in the documentation for each endpoint.

| Access Token Types  |                                                               |
| ------------------- | ------------------------------------------------------------- |
| Integration API Key | Used to authorize a request to target a specific integration. |
| App API Key         | Used for operations that is scoped to an integration app.     |


---

# 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.intserv.se/basics/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.