For the complete documentation index, see llms.txt. This page is also available as Markdown.

Jamf Pro Cloud

Connection Requirements

Use this adapter when

Your Jamf Pro instance is version 10.49.0 or later and you have generated an API Client (client_id + client_secret) in the Jamf Pro UI. For older Jamf instances using username/password authentication, use the Jamf Pro adapter instead.

1 - Domain

Jamf Cloud instance hostname (e.g., mycompany.jamfcloud.com) or your self-hosted Jamf Pro hostname. Enter without the https:// prefix.

2 - Client ID

The API Client ID generated under Settings -> System -> API Roles and Clients -> API Clients. Sent as client_id in the OAuth2 token exchange.

3 - Client Secret

The API Client secret paired with the Client ID. Jamf displays the secret only once at creation — capture it then. Sent as client_secret in the OAuth2 token exchange.

4 - Fetch users

When enabled, the adapter performs a second pass over the same inventory endpoint with the USER_AND_LOCATION section and emits each unique device-assigned user (default: Disabled). Devices are always fetched.

5 - Aggregate by MAC

When enabled, the adapter falls back to the device's MAC address as the aggregation key if the hostname is missing (default: Enabled). Hostname is always tried first. Disable if MAC duplication across your fleet would create false correlation matches.

6 - Aggregate by IP

When enabled, the adapter falls back to the device's last reported IP address as the aggregation key if both hostname and MAC are unavailable (default: Enabled). Disable in DHCP-heavy environments where IP volatility would produce noisy matches.

7 - Proxy

Optional proxy server in host:port format used to reach Jamf Cloud.

8 - Timeout

The amount of time (in seconds) to wait for Jamf API responses (default: 60). Large tenants can take longer to paginate; raise this if you see timeouts during initial discovery.

Permissions Required

The API Client must be bound to an API Role with the Read Computers privilege. Without this privilege, requests to /api/v1/computers-inventory return HTTP 403.

Last updated