OnLink · Device management
OnLink imports every company-owned Mac, iPhone and iPad from Apple Business Manager into Jira Service Management Assets: serial number, model, order number, assigned MDM server and AppleCare status, pulled from the Apple Business API and kept in sync.
Serial, model, capacity, color, order number and order date for every device bought from Apple or an authorized reseller.
Which MDM server (Jamf Pro, Intune, Iru) each device is assigned to, and whether it is still unassigned.
Coverage per device from the AppleCare endpoint, so agents see warranty before they book a repair.
Wi-Fi, Bluetooth and Ethernet MAC addresses plus IMEI, MEID and EID for cellular devices.
Apple Business is where IT teams enroll company-owned Apple devices through Automated Device Enrollment and assign them to an MDM server. The Apple Business API exposes that data, so you can:
An Organization Administrator creates an API account in Apple Business Manager and downloads the private key. OnLink signs a JWT client assertion and exchanges it for a token.
A GET request to the Get Organization Devices endpoint, response path data, cursor pagination. Run it once to see a sample device.
Key on serialNumber so OnLink updates instead of duplicating, then map the 23 supported fields you want.
Apple Business uses OAuth 2. An Organization Administrator creates an API account, which gives you a client ID and a private key. OnLink uses these to sign a client assertion (a JWT) and exchange it for an access token.
business.api and save.
This example uses Apple’s Get Organization Devices endpoint. Configure the request in your data source:
|
Setting
|
Value
|
|---|---|
|
Method |
|
|
URL |
|
|
Response data path |
|
|
Pagination |
Cursor-based |
Add query parameters for the fields you want returned. Save, then run the data source to fetch a sample:
{
"data": [{
"type": "orgDevices",
"id": "C02FK3ABQ6L4",
"attributes": {
"serialNumber": "C02FK3ABQ6L4",
"deviceModel": "MacBook Pro (14-inch, 2024)",
"productFamily": "Mac",
"deviceCapacity": "512GB",
"color": "SPACE BLACK",
"status": "ASSIGNED",
"orderNumber": "W1234567890",
"wifiMacAddress": "a4:83:e7:1c:52:9f",
"purchaseSourceType": "APPLE"
}
}],
"meta": { "paging": { "nextCursor": "MDowOjE3NDYx...", "limit": 100 } }
}
Apple pages results with cursors, so set up pagination before a full import. The endpoint has no filters; each run fetches every device.
Devices are just one example. Point the same data source at any Apple Business API method, such as AppleCare coverage or users, and map what comes back.
Create the Assets import (JSM Assets Data Synchronization) and map Apple fields to your object type’s attributes. Use serialNumber as the key, so OnLink updates existing objects instead of creating duplicates.
|
OnLink mapping
|
What it stores
|
|---|---|
key:serialNumber=Serial Number |
Unique key: OnLink updates the existing object instead of creating a new one
|
map:deviceModel=Device Model |
Model, such as MacBook Pro (14-inch, 2024)
|
map:productFamily=Product Family |
Mac, iPhone, iPad, Apple TV
|
map:productType=Product Type |
Apple hardware identifier
|
map:deviceCapacity=Device Capacity |
Storage size
|
map:color=Color |
Device color
|
map:status=Status |
ASSIGNED or UNASSIGNED to an MDM server
|
map:orderNumber=Order Number |
Purchase order number
|
map:orderDateTime=Order Date Time |
When the device was ordered
|
map:purchaseSourceType=Purchase Source Type |
APPLE, reseller or carrier
|
map:wifiMacAddress=Wi-Fi MAC Address |
For the network team
|
map:imei=IMEI |
Cellular devices
|
map:assignedServer=Assigned Server |
The MDM server the device is assigned to
|
map:appleCareCoverage=AppleCare Coverage |
Warranty and AppleCare status
|
Map only what you need, and make sure each target attribute exists in Assets with the same spelling. The full setup guide lists all 23 fields.
Good employee experience depends on context. HR knows the person; IT knows the device. When both live in Assets, onboarding, support and offboarding stop depending on someone remembering to check a second system. OnLink brings HR data and Apple device data in from the same app.
HR data from Workday, BambooHR or ADP and the Apple device record land in the same Assets schema, so the onboarding ticket already shows which MacBook is waiting for the new hire.
When HR marks a leaver, the offboarding ticket lists every Apple device assigned to them, with serial and order number, so recovery is a checklist instead of a search.
If you are using Apple Business Manager, OnLink gets your devices into Assets in an afternoon. Start a free trial on the Atlassian Marketplace or follow the step-by-step setup guide.
A REST API for Apple Business Manager. It returns device information for every device enrolled through Automated Device Enrollment, lets you change MDM server assignments, and manages users and user groups. This guide uses the Get Organization Devices endpoint.
An Organization Administrator. Each account has a client ID and a private key that downloads once; OnLink uses them with the business.api scope.
Yes, with the same template and the school.api scope. The Apple School Manager guide walks through it.
No. The organization devices endpoint returns hardware, order and purchase details only. Linking a device to its owner happens in Assets, using your HR or identity source.
On the schedule you set for the OnLink sync. The endpoint has no filters, so each run fetches every device and updates existing objects by serial number.
This guide is an import. For write-back, such as changing the assigned MDM server from a Jira workflow, OnLink AI can call any REST API, including the Apple Business API, from Jira and JSM automations.
Apple Business data in Assets
Start a free trial of OnLink on the Atlassian Marketplace. One app covers Apple Business, Apple School Manager, Jamf Pro, Intune and 100+ more.
Get OnLink on the Atlassian Marketplace and start a free trial, or follow the step-by-step setup guide. Every other source OnLink connects is listed in One App, Every Source.
With Apple Business data in Assets, your team can:
RELATED