OnLink · Device management

Import Mobile Devices from Jamf Pro into Assets

OnLink imports mobile device details from Jamf Pro into Jira Service Management Assets through the Jamf Pro API.

Three steps, no scripts. The same pattern covers computers, users and any other Jamf Pro endpoint.

Diagram: Jamf Pro API mobile devices and other endpoints flow through OnLink field mapping into a JSM Assets Mobile Device object type
One Jamf Pro connection in OnLink, any endpoint, mapped with dot notation into Assets.

Three things to get right

Match the API version

The example uses /api/v2/mobile-devices. Jamf also serves v3 and v4; pick one version per data source and check its field names in Fetch API Sample before mapping.

Ask only for the sections you need

section=GENERAL&section=HARDWARE keeps the response small and the sync fast. Add SECURITY or USER_AND_LOCATION when you map those fields.

Key on a value that never changes

mobileDeviceId is stable and always returned. Keying on display name or serial breaks the moment a device is renamed or swapped.

Step 1: Connect OnLink to Jamf Pro

Before you start, have these ready:

  • A Jamf API role and client with read access to the data you want to import
  • The client ID and client secret
  • Your Jamf Pro base URL, for example https://yourserver.jamfcloud.com

Then set up the connection:

  1. In Jira, go to Manage your apps > OnLink.
  2. Select Add Assets Data Source.
  3. For authentication, choose OAuth client credentials.
  4. Enter the token URL using your Jamf Pro base URL.
  5. Add the Jamf client ID and client secret.
OnLink OAuth settings for connecting to the Jamf Pro API
OnLink: OAuth client credentials for the Jamf Pro API, token URL built from your Jamf Pro base URL.

Step 2: Get mobile device details

This example uses the Jamf Pro API v2 mobile devices endpoint. It’s just one example: OnLink can call any supported Jamf Pro API or Classic API method, including v3 and v4 endpoints.

In the OnLink endpoint configuration:

  1. Select the GET method.
  2. Enter the endpoint URL: https://yourserver.jamfcloud.com/api/v2/mobile-devices
  3. Optional: add section parameters to limit what comes back, for example section=GENERAL&section=HARDWARE. The Jamf API reference lists every section.
  4. Configure pagination so OnLink pulls every page of results.

 Click Fetch API Sample to preview the Jamf response. You’ll use it to confirm field paths in the next step.

OnLink endpoint settings to get mobile device details from Jamf Pro
OnLink: GET /api/v2/mobile-devices with section parameters and pagination.

Step 3: Map Jamf fields to Assets attributes

Mapping rules tell OnLink which Jamf field fills which Assets attribute. Two keywords do the work:

  • key sets the unique ID OnLink uses to match and update existing Assets objects.
  • map links a Jamf field path to an Assets attribute. Nested fields use dot notation, like general.osVersion.

Here’s a starter mapping for mobile devices:

OnLink mapping
What it stores
key:mobileDeviceId=id
Unique key; repeat syncs update the existing object
map:deviceType=Device Type
iPhone, iPad, Apple TV
map:general.displayName=Name
Device name shown in Jamf Pro
map:general.osVersion=OS Version
iOS, iPadOS or tvOS version
map:general.ipAddress=IP Address
Last reported IP
map:lastEnrolledDate=Last Enrolled Date
When the device enrolled
map:hardware.serialNumber=Serial Number
Serial, the natural join to Apple Business or Apple School Manager
map:hardware.model=Model
Hardware model
map:userAndLocation.username=Assigned User
Who the device is assigned to

Start with a few fields, check each path against the API sample, then add more. Serial number, model, assigned user and security status are all in the response when you need them.

To run it, click Get Data, wait for Job Logs to show No more pending records, then click Import. Add a schedule and Assets stays in sync with Jamf Pro on its own.

The app handles multi-source data imports into Assets well, overcoming gaps in other native solutions. Support has been responsive, and documentation is clear and thorough.
Gikku John
OnLink customer · Atlassian Marketplace review, Sep 2026
Bring Jamf Pro into Assets with OnLink

No scripts to write or maintain. OnLink connects Jamf Pro, and 100+ other HR, identity and device sources, to JSM Assets in one app.

FAQ: importing Jamf Pro mobile devices into Assets

Yes. Mobile devices are just the example. Swap in any supported Jamf Pro API or Classic API endpoint, then update the mapping to match that response.

Read access only. Create a Jamf API role and client that can read the data you want to import, and give OnLink its client ID and secret.

No. OnLink uses the key field to match existing Assets objects and update them. Pick a field that is unique and always returned by the API.

Set a schedule in OnLink. It runs Get Data and Import automatically, so Assets reflects Jamf without manual runs.

Compare your mapping path with the Fetch API Sample response; nested fields need dot notation, like general.osVersion. If nothing imports at all, check the endpoint URL and the API client’s permissions.

Yes, two kinds. Pio sells a dedicated Jamf Importer app. OnLink imports Jamf Pro alongside Intune, Iru, Workspace ONE, Apple Business and 100+ other sources in one app at one price, with no limit on connections. Here is how they compare.

Yes. Key the Jamf import and the Apple Business or Apple School Manager import on serial number into the same object type, and Assets shows the purchase record next to the live MDM state for every device.

On this page

Jamf Pro data in Assets

Start a free trial of OnLink on the Atlassian Marketplace. Jamf Pro, Intune, Iru, Apple Business and 100+ more in one app.

Try OnLink for Jamf Pro to JSM Assets

Try OnLink free on the Atlassian Marketplace and import your first Jamf Pro devices today.

With Jamf Pro data in Assets, your team can: