Jamf Pro
Jamf Pro connects your managed Apple device (computer) inventory into Navigator.
Beta. This connector was built from Jamf Pro’s documentation and hasn’t been verified against a live account yet. It may return incomplete data or fail in ways we haven’t seen. If something looks wrong, contact [email protected].
At a glance
| Data provided | Devices |
|---|---|
| Authentication | OAuth2 client credentials (API Client) |
| Where to configure | Connectors → Add a Connector → Jamf Pro |
Required permissions
Create an API Role with read access to computer inventory (General, Hardware, Operating System, Storage, User and Location, and Disk Encryption categories), then create an API Client tied to that role.
| Credential | Where to find it |
|---|---|
| Client ID / Client Secret | Jamf Pro → Settings → System → API Roles and Clients |
| Jamf Pro URL | Your own Jamf Cloud instance address, e.g. https://yourorg.jamfcloud.com |
Setup
- In Jamf Pro, go to Settings → System → API Roles and Clients.
- Create an API Role with read access to computer inventory, using the categories listed above.
- Create an API Client and assign it the role you just created. Note the Client ID and generate a Client Secret.
- In Navigator, go to Connectors → Add a Connector → Jamf Pro.
- Enter your Jamf Pro URL, Client ID, and Client Secret.
- Save. Navigator validates the credentials and enqueues a first sync immediately.
Vendor documentation
Jamf’s own instructions: Jamf Pro API overview, including how to set up an API Role and Client.
What data this connector provides
- Devices: managed computer inventory, including hostname, serial number, model, operating system name and version, MAC address (including a secondary network interface, where present), disk encryption (FileVault) status, RAM, and storage capacity.
- The email address of the user assigned to each device, where Jamf Pro has that association, so it can be cross-referenced against your other identity sources.
Known limitations
- This connector only covers computer inventory. Jamf Pro’s own directory of end users is a separate, older part of its API whose data hasn’t been confirmed to represent real end users rather than internal admin accounts, so it isn’t imported as a standalone Users list. The device-to-user email association above is still available.
- Windows feature-update-level detail (for organizations managing Windows machines through Jamf Pro) isn’t broken out beyond the reported OS version string.
- This connector was built from Jamf’s published API reference rather than tested against a live instance. If you notice a field that looks wrong or missing, let us know so it can be corrected against real data.