Reference · built on requestConnectorIdentity, IT & observability

Jamf Pro

Computer and mobile device inventory, smart groups, policies, and MDM commands from Jamf Pro through the Jamf Pro API and Classic API.

Request accessPricing ↗

About

Jamf Pro manages Apple devices: Mac computers, iPhones, iPads, and Apple TVs. The Jamf Pro API lives at /api on each instance, versioned v1 to v3, with JSON, RSQL filtering, sorting, and pagination. The Classic API at /JSSResource covers policies, groups, webhooks, and older inventory endpoints in XML or JSON. Webhooks POST events such as ComputerAdded, ComputerInventoryCompleted, MobileDeviceEnrolled, and SmartGroupComputerMembershipChange to a URL you set.

Through Fibric, an operator reads a device's inventory sections and group memberships and proposes an MDM command or a managed software update plan. You approve it, and the receipt records the command and its result.

This is a reference listing. It documents what Fibric would read from Jamf Pro and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Computer inventory through GET /v1/computers-inventory with sections such as GENERAL, HARDWARE, OPERATING_SYSTEM, SECURITY, DISK_ENCRYPTION, APPLICATIONS, and GROUP_MEMBERSHIPS
  • Mobile device inventory through GET /v2/mobile-devices and /v2/mobile-devices/detail, filterable by lastInventoryUpdateDate
  • FileVault state through /v1/computers-inventory/filevault, and smart and static computer groups through /v2/computer-groups
  • Policies, patch policies, scripts, packages, departments, buildings, and users through the Classic API
  • Webhook events ComputerAdded, ComputerCheckIn, ComputerInventoryCompleted, ComputerPolicyFinished, MobileDeviceEnrolled, MobileDeviceUnEnrolled, PatchSoftwareTitleUpdated, and SmartGroupComputerMembershipChange
  • Available managed software updates and update plans through /v1/managed-software-updates

Proposed actions

  • Target capability: propose an MDM command through POST /v2/mdm/commands, such as DEVICE_LOCK, RESTART_DEVICE, ENABLE_LOST_MODE, or ERASE_DEVICE, by clientManagementId
  • Target capability: propose a Managed Software Update Plan through POST /v1/managed-software-updates/plans
  • Target capability: propose a field update on a computer through PATCH /v1/computers-inventory-detail/{id}
  • Target capability: propose a Smart Computer Group through POST /v2/computer-groups/smart-groups, or a webhook through the Classic webhooks endpoint

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Lock or wipe a leaver's Mac

    When the leaver is flagged, the operator finds the device by user in inventory and proposes DEVICE_LOCK, then ERASE_DEVICE once the machine is back. Each command is a separate approval with a receipt.

    With Offboarding Sweep

  • Plan the next OS update wave

    Available updates from /v1/managed-software-updates/available-updates meet the OPERATING_SYSTEM section of inventory. The operator proposes a Managed Software Update Plan for the group and window you choose.

    With Patch Window

  • Hand an auditor the encryption evidence

    FileVault state, SECURITY section values, and smart group membership are exported per device with the report date, so the evidence names the record it came from.

    With Compliance Evidence

  • Finish setup after enrollment

    A ComputerAdded or MobileDeviceEnrolled webhook starts the list. The operator checks the policies and profiles that should land and proposes what is missing.

    With Onboarding Checklist

Requirements

  • A Jamf Pro instance on 10.49.0 or later for client credentials, or 10.35.0 or later for bearer tokens on the Classic API
  • An API Role with the privileges the operator needs, for example Read Computers, Read Mobile Devices, and Create Managed Software Updates
  • A public HTTPS URL to receive webhook POSTs, configured with content type JSON or XML and NONE or BASIC authentication
  • A recurring inventory policy for computers and the mobile device inventory frequency setting, so records are fresh
Authentication
A bearer token from POST /api/oauth/token using client credentials issued to an API Client bound to API Roles, or from POST /api/v1/auth/token with a Jamf Pro user account's username and password.

Limits

  • Jamf Pro has no built-in rate limiting; Jamf recommends at most 5 concurrent connections and exponential backoff
  • Inventory is collected at most once per day per device unless a policy or a command requests it, so webhooks are the fresh signal
  • Bearer tokens expire after 20 minutes by default; keep-alive issues a new token and invalidates the old one
  • The Classic API computers inventory endpoints are deprecated from 11.15.0, and from 11.17.0 Basic auth only obtains a token

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Jamf Pro ↗

Questions and answers

Which Jamf API should I use?
The Jamf Pro API at /api for inventory, groups, MDM commands, and software updates; it supports RSQL filtering, sorting, and pagination. The Classic API at /JSSResource for policies, webhooks, and objects not yet in the Jamf Pro API. Classic computer inventory endpoints are deprecated from 11.15.0.
How do webhooks work in Jamf Pro?
You subscribe to events on the instance and Jamf Pro POSTs a JSON or XML payload to your URL. Events include ComputerAdded, ComputerCheckIn, ComputerInventoryCompleted, ComputerPolicyFinished, MobileDeviceEnrolled, PatchSoftwareTitleUpdated, and SmartGroupComputerMembershipChange. Inventory events carry the jssID; a follow-up API call fetches the full record.
How does authentication work?
Create an API Role with privileges and an API Client, then exchange the client ID and secret at POST /api/oauth/token for a short-lived bearer token. Username and password can still obtain a token at /api/v1/auth/token. SSO is not supported for API authentication.
Ask about Jamf Pro

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Jamf Pro through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy