Skip to main content
Telara

Integrations / Jamf

Jamf logo

Jamf

Jamf Pro device management for Apple computers, mobile devices, inventory, users, groups, and endpoint lifecycle workflows.

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Before you connect

Prerequisites

A Jamf Pro server Telara can reach.
A Jamf admin who can create an API role and client (Jamf Pro API).

Vendor setup

Get the credential

1
Open API roles
In Jamf Pro, go to Settings → System → API roles and clients.
2
Create a role and client
Create an API role with the permissions this page lists. Then create an API client, assign that role, and copy the client id and secret.
3
Paste in Telara
Settings → Integrations → Jamf. Enter your Jamf Pro URL, client id, and secret.

In Telara

Connect in Telara

OAuth 2.0

Jamf Pro OAuth client credentials. Store base_url as the Jamf host without scheme, for example yourServer.jamfcloud.com.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Base Url

Knowledge

What gets indexed

ResourceCoverage
ComputerPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
ComputerUp to 1 hourRemoved 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: Computer.

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

Classic API user/password is a different auth class. Prefer the API client Telara’s form asks for.
On-prem Jamf must allow Telara to reach the Jamf Pro URL, not only the enrollment hostname.