OnLink · Device management
OnLink imports every device your school owns from Apple School Manager into Jira Service Management Assets, using Apple’s Get Organization Devices API: serial number, model, order number, purchase date and the MDM server each device is assigned to. Set it up once and the service desk sees the purchase record next to the live MDM state.
This guide is for K-12 and Higher Ed IT teams.
Buzz
Know exactly which Macs, iPads and Apple TVs the institution bought, on which order, and whether each one ever enrolled in your MDM.
See purchase date, AppleCare status and assigned MDM server on the ticket, without opening Apple School Manager.
Reconcile Apple invoices against what is actually deployed; spot devices that were released from the organization.
The Apple School Manager API is a REST API for the devices your institution enrolls through Automated Device Enrollment. This guide uses one endpoint, Get Organization Devices, which returns every device in your organization with its hardware, order and purchase details.
The same API also covers:
Apple School Manager uses OAuth 2 with a private key, so there’s no password to share. You create an API account in Apple School Manager, then give OnLink its credentials.
Follow Apple’s guide
.pem file downloads once, so store it somewhere safe.school.api. (Apple Business uses business.api instead.)
business.api scope with the same template. Everything else in this guide is identical, so you can run both from one OnLink install.
Configure the request in the data source:
|
Setting
|
Value
|
|---|---|
|
Method |
|
|
URL |
|
|
Response data path |
|
|
Pagination |
Cursor-based ( |
Save and run the data source to pull sample data. Each device comes back like this (trimmed):
{
"type": "orgDevices",
"id": "XABC123X0ABC123X0",
"attributes": {
"serialNumber": "XABC123X0ABC123X0",
"deviceModel": "iMac 21.5\"",
"productFamily": "Mac",
"productType": "iMac16,2",
"deviceCapacity": "750GB",
"color": "SILVER",
"status": "UNASSIGNED",
"orderNumber": "1234567890",
"orderDateTime": "2011-08-15T07:00:00Z",
"addedToOrgDateTime": "2025-04-30T22:05:14.192Z",
"purchaseSourceType": "APPLE"
},
"relationships": {
"assignedServer": { "links": { "related": "https://api-school.apple.com/v1/orgDevices/XABC123X0ABC123X0/assignedServer" } },
"appleCareCoverage": { "links": { "related": "https://api-school.apple.com/v1/orgDevices/XABC123X0ABC123X0/appleCareCoverage" } }
}
}
This is one example. You can point the same data source at any Apple School Manager endpoint, such as a device’s AppleCare coverage.
Create the Assets import (JSM Assets Data Synchronization), then map Apple fields to your Assets attributes. Use one key: line so OnLink knows when to update an existing object instead of creating a new one. Serial number is the natural choice.
|
OnLink mapping
|
What it stores
|
|---|---|
|
|
Unique key for matching objects |
|
|
Model, such as iPad (10th generation) |
|
|
Mac, iPad, iPhone, Apple TV |
|
|
Apple hardware identifier |
|
|
Storage size |
|
|
Device color |
|
|
Assigned or unassigned to an MDM server |
|
|
Purchase order number |
|
|
When the device was ordered |
|
|
When it joined Apple School Manager |
|
|
When it was released |
|
|
Wi-Fi MAC, handy for network teams |
|
|
IMEI for cellular devices |
The full setup guide lists every supported field.
key:serialNumber and a simple Assets filter shows devices you paid for that never enrolled, or enrolled devices with no purchase record.
Check the Client ID, Private Key, Apple Team ID and Apple Client ID, and that the scope is school.api. A key downloaded for a different API account will not work.
Confirm the URL is https://api-school.apple.com/v1/orgDevices and the response data path is data.
Turn on cursor-based pagination (meta.paging.nextCursor) in the data source and test that OnLink requests the next page.
Make sure key:serialNumber=Serial Number is set and that the serial number attribute exists on the object type.
Each map: target must match an existing attribute name exactly, including case.
OnLink connects Apple School Manager, your MDM and your HR systems to Jira Service Management Assets, with 100+ connectors in one app.
They answer different questions. Apple School Manager is the purchase record: what you bought, when, on which order, and which MDM server it’s assigned to. Your MDM knows the device’s current state. Import both and key them on serial number, and you can spot devices you own that never enrolled.
Devices in your organization that enroll through Automated Device Enrollment: those bought from Apple or an authorized reseller or carrier, plus any added with Apple Configurator.
An Administrator or Site Manager in Apple School Manager. You can have up to 50 API accounts, so you can keep one just for OnLink.
No. The organization devices endpoint returns hardware, order and purchase details. It has no student or staff names.
Yes. Add a second data source that calls the AppleCare coverage endpoint and map it to the same object type, keyed on serial number. Your service desk then sees warranty status right on the device.
Yes. Use the same template with the business.api scope for Apple Business and school.api for Apple School Manager, key both on serial number and map to the same object type. Districts that run both see one device list.
Schedule the OnLink sync. Each run fetches every organization device (the endpoint has no filters) and updates existing objects by serial number, so changes in status, assigned server or release date show up on the next run.
Apple School Manager data in Assets
Start a free trial of OnLink on the Atlassian Marketplace. One app covers Apple School Manager, Apple Business, Jamf Pro, Intune and 100+ more.
Set up the Apple School Manager template once and give your service desk the full device picture. Try OnLink on the Atlassian Marketplace or talk to our team. See every other source OnLink connects in One App, Every Source.
With Apple School Manager data in Assets, your team can:
