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

# Authentication

Authenticate to the Govern app or Request app API

## Govern app API

There are two methods for making an authenticated request to the Govern API. Select a tab below for instructions.

{% tabs %}
{% tab title="API key method" %}

1. Generate your API key on the **API Keys** tab on your profile page and save the API key somewhere secure.
2. You will pass this API key in the authorization header when you make a request, as illustrated in the example below:

   ```bash
   curl \
       --request GET \
       --header "Content-Type: application/json" \
       --header "Authorization: 846e9e43c86a4ct1be14290d95127d13f" \
       https://your-immuta-url.immuta.com/data/connection/123456789
   ```

{% endtab %}

{% tab title="Bearer token method" %}

1. Generate your API key on the **API Keys** tab on your profile page and save the API key somewhere secure.
2. Pass this API key in the authorization header and make the following request to the `authentication` endpoint:

   ```bash
   curl \
       --request POST \
       --header "Content-Type: application/json" \
       https://your-immuta-url.immuta.com/bim/apikey/authenticate \
       -d '{ "apikey": "YOUR_API_KEY" }'
   ```
3. You will receive a response that includes your bearer token. Pass that bearer token in the authorization header when you make a request, as illustrated in the example below:

   ```bash
   curl \
       --request GET \
       --header "Content-Type: application/json" \
       --header "Authorization: Bearer dea464c07bd07300095caa8" \
       https://demo.immuta.com/data/connection/123456789
   ```

{% endtab %}
{% endtabs %}

## Request app API

Immuta uses JWTs to match users with their tenants. The JWTs contain this metadata in the claims, which is required for the request context in the Request app API.

### Generate a personal access token (PAT)

In Immuta,

1. Navigate to the [**Developer Settings** page](https://app.immutacloud.com/auth/settings/account/developer/tokens).
2. Click **Generate token**.
3. Enter a **Token Name**.
4. Select an **expiration**. You may select **No expiration**, which will allow the token to remain active until it is manually revoked.
5. Click **Generate token**.
6. The new PAT will be displayed. Store this token somewhere secure; it is only presented once and cannot be retrieved again later.
7. To use your generated PAT, insert it as the Bearer token for your API calls:

   ```
   curl -L \
     --url '{correct base path from above}/api/access-agreement' \
     --header 'Authorization: Bearer <your-PAT>'
   ```


---

# 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://documentation.immuta.com/SaaS/developer-guides/api-intro/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.