> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/build/connections/auth-types.md).

# Auth types

The values in the Auth column and on a connection's detail page, and what each one means for keeping the connection working.

The **Auth** column on the [Connections](/build/connections.md) page, and **Auth method** on a connection's detail page, show the type of auth method the connection was made with. They show the stored value, not a display name.

| Value     | Method in the connect dialog | What the user gave                                                      | What keeps it working                                                                                                     |
| --------- | ---------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| `OAUTH_2` | OAuth 2.0                    | Signed in to the app and approved access.                               | The access token expires, and fastn renews it with the refresh token. If renewal fails, the connection becomes `Expired`. |
| `API_KEY` | API Key                      | An API key.                                                             | The key staying valid in the app. Deleting or rotating it there breaks the connection.                                    |
| `BEARER`  | Bearer Token                 | A token, for example a personal access token.                           | The token staying valid in the app, including any expiry date the app sets.                                               |
| `BASIC`   | Basic Auth                   | A username and password.                                                | The password not changing.                                                                                                |
| `DIGEST`  | Digest Auth                  | A username and password.                                                | The password not changing.                                                                                                |
| `INPUT`   | Custom                       | The fields the connector defines, for example an account ID plus a key. | The entered values staying valid in the app.                                                                              |
| `NO_AUTH` | No Auth                      | Nothing.                                                                | Nothing to keep up.                                                                                                       |

The detail page adds a plain-language note under the value, for example *Your customer signed in and approved access.* for `OAUTH_2`.

For OAuth connections, check the **Token and activity** panel on the [detail page](/build/connections/inside-a-connection.md) to see when the token expires and when fastn last renewed it.

The full list of methods, and the fields each one asks for, is in [Creating a connector → Authentication](/build/connectors/creating-a-connector.md#authentication).


---

# 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.fastn.ai/build/connections/auth-types.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.
