> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/absolute-integration-setup.md).

# Absolute Integration Setup

### Getting Started

Use this guide to connect Absolute to your BalkanID tenant. BalkanID reads your Absolute console users, roles, device groups, and managed devices, and the permissions that connect them, so you can review who can reach which device group or device and how.

You will need an API token from your Absolute console and access to the Integrations section in BalkanID.

#### Requirements:

Before you begin, collect the following values from Absolute:

* **API Base URL**
* **API Token ID**
* **API Secret Key**

### Configure Absolute within your BalkanID tenant

1. To create the **API Token ID** and **API Secret Key**, sign in to your Absolute console as an administrator. The console login address depends on your region — `cc.absolute.com`, `cc.us.absolute.com`, `cc.eu2.absolute.com`, `cc.in1.absolute.com`, or `cc.fr1.absolutegov.com`.
2. Create your API token, choosing **Generate Token**. Absolute shows the **API Secret Key** only once — copy it immediately, as it cannot be retrieved again after you leave the page.
3. When creating the token, grant it view access to Users, Roles, Device Groups, Devices, and API Credentials (see [Integration Scopes](#integration-scopes) below). Token permissions are limited to a subset of the creating user's role and cannot be changed after creation — if you need to add a permission later, create a new token.
4. Note the **API Base URL** for your region (for example, `https://api.absolute.com`) — this is your console's matching API host, not the console login address itself.
5. In BalkanID, go to **Configure** > **Integrations** and select **Add integration**, then search for **Absolute**, select the application, and click **Next**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fgit-blob-a11894f1b4ab96042d9eb638d07f898a5e67d93f%2Fabsolute-connect-application.png?alt=media" alt="The Connect a new application step with Absolute found in the application search"><figcaption><p>Connect a new application</p></figcaption></figure></div>

6. Review **Data Sync Preferences**, then click **Next**.
7. Under **Select Extraction Type**, keep **Direct Configuration** selected and paste your **API Base URL**, **API Token ID**, and **API Secret Key** into the corresponding fields, then click **Next**. The Required API Scopes panel above confirms which permissions BalkanID asks for.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fgit-blob-611b226bf11e647879c19a2b879620bdcdf6021f%2Fabsolute-direct-configuration.png?alt=media" alt="The Required API Scopes panel and the Direct Configuration step showing the API Base URL, API Token ID, and API Secret Key fields"><figcaption><p>Direct Configuration</p></figcaption></figure></div>

8. Fill **Optional Configuration**, if required.
9. Once you have filled in the information, click **Save**. Your integration is now configured and you will see the status of the integration displayed alongside other integrations on the Integrations page. When data is available, the integration Status column will read **Connected** and the integration Message will read **Data available**.

### What BalkanID extracts

| Type              | Description                                                                                                                                                                                    |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Users**         | Console users in your Absolute account, including their status, role assignment, and device group assignments.                                                                                 |
| **Roles**         | The roles configured in your Absolute console. Absolute's API does not expose a role's permission list, so BalkanID reports role names and descriptions but cannot show what each role can do. |
| **Device groups** | The device group hierarchy in your Absolute console and its members.                                                                                                                           |
| **Devices**       | Managed endpoints, including operating system, connection status, compliance state, and which device group each one belongs to.                                                                |
| **API token**     | The API credential used for this integration. Absolute's API does not expose an inventory of other tokens in your account, so BalkanID can only report on the one connected here.              |

BalkanID also raises risk findings from this data — for example, an inactive account that still retains device or role access, a non-compliant or stale device, a device reported stolen or missing, and an expired API credential.

BalkanID does not extract employee/HR records or an AI agent inventory from Absolute — its API exposes neither. ("Agents" in the Absolute console refers to the endpoint software agent running on a device, not an AI agent.)

### Integration Scopes

| Read Only Scopes                                                                                                                             | Lifecycle Management Scopes |
| -------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- |
| **Users, Roles, Device Groups, Devices, API Credentials (Read)** — console users, roles, device groups, devices, and the connected API token | N/A                         |

### Requirements and limitations

* Token permissions are a subset of the creating user's role and are fixed once the token is created. If a permission is missing, the affected part of the sync is skipped and BalkanID's integration message reports which one — no manual retry is needed once a new token with the right permissions is connected.
* Device group access is reported through device group membership. Direct device-level access outside of a device group is not reported as a separate relationship in this release.
* A device is only marked non-compliant when Absolute reports it as such. Devices Absolute does not evaluate for compliance (for example, Chromebooks) are not reported as non-compliant.


---

# 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.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/absolute-integration-setup.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.