To use Jamf Pro with the DestinyResource Manager Mobile Device Management (MDM) Integration feature, ensure the following are in place:

• A Jamf Pro API user or modern API Role and Client. Resource Manager stores the Jamf Pro URL, username, and password.

  Note: Destiny Resource Manager exchanges those credentials for a bearer token by using POST /api/v1/auth/token and keeps the token active through /api/v1/auth/keep-alive.

• The API user or role must have privileges to:
  • Read mobile devices and mobile device groups, including smart groups and departments
  • Write mobile device group membership for sync
  • Send MDM commands – at minimum, UnmanageDevice
  • Manage webhooks
• Resource Manager automatically creates three webhook subscriptions on your behalf, so no manual webhook configuration is required if the API user has the right privileges:
  • MobileDeviceEnrolled
  • SmartGroupMobileDeviceMembershipChange
  • MobileDeviceCommandCompleted

Use the following resources to complete the Jamf Pro setup:

• Create API Roles and Clients and assign the required privileges. This is the recommended approach for modern Jamf Pro.
• Review the Jamf Pro API Overview to understand the modern API and bearer token authentication flow that Resource Manager uses.
• Use the modern Jamf Pro API reference for devices, device groups, departments, and webhooks.
• Use the Classic API reference for endpoints that Resource Manager still uses, such as /JSSResource/..., mobiledevices/serialnumber/{sn}, mobiledevicegroups, and mobiledevicecommands/.../UnmanageDevice).
• Review the webhooks concept overview.
• Review the instructions for configuring a webhook by event type and destination URL (Resource Manager performs this setup programmatically).
• Review the Smart Groups concept overview. Resource Manager queries smart mobile device groups during sync.
• Review the admin-console walkthrough for creating a Smart Group.

To use Jamf School with the DestinyResource Manager Mobile Device Management (MDM) Integration feature, gather the following information:

• An API Key generated in the Jamf School UI under Organization > Settings > API.
• The credentials Resource Manager stores: Jamf School URL, Network ID, and API Key. Jamf School uses basic authentication and does not require a bearer token exchange.
• An API key with access rights to Locations, Devices, and Device Groups. Read access is required, and write access is required to allow device commands.

To help with Jamf School setup, do the following:

• Review the Jamf School API learning hub for an overview of the Jamf School API, where to generate API keys, and the base endpoint URL.
• Review the Jamf School developer-portal companion, which includes the correct endpoint format: yourSchool.jamfcloud.com/api.
• Review administrator roles and accounts to determine what access the API user's role provides.
• Review device groups, including static and smart groups. Resource Manager queries these during sync.
• Use your district's or school's interactive API reference, available at: https://<yourSchool>.jamfcloud.com/api/docs.