Import Mobile Devices from Jamf Pro into Assets

This post walks through importing mobile device details from Jamf Pro into Assets using OnLink.

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.

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.

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:

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.

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.

Try OnLink free on the Atlassian Marketplace and import your first Jamf Pro devices today. The full setup guide has the sample response and troubleshooting tips.

FAQs – Import Jamf Mobile Device to Assets

Can I import Jamf data other than mobile devices?

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.

What Jamf permissions does OnLink need?

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.

Will each run create duplicate objects in Assets?

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.

How do I keep Assets in sync with Jamf Pro?

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

A mapped field is empty. What should I check?

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.