Integrations / Kandji

Kandji

Kandji Apple device management for devices, blueprints, users, app inventory, and endpoint compliance workflows.

Bearer token

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Kandji tenant you can administer.

Administrator who can create API tokens under Settings.

Vendor setup

Get the credential

Open API tokens

In Kandji, go to Settings → Access → API tokens (or Settings → API).

Create a token

Click Add API token. Name it for Telara. Copy the bearer token once.

Paste in Telara

Settings → Integrations → Kandji. Paste the token. Enter the Kandji subdomain if the form asks for it.

In Telara

Connect in Telara

Bearer token

Kandji API token generated from Settings > Access. Store base_url as the tenant API host without scheme.

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for

Base Url
API token

Knowledge

What gets indexed

Resource	Coverage
Device	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Device	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Device.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Tokens inherit the creating admin’s blueprint visibility.

EU vs US Kandji tenants are different hosts.