Mosyle
Apple device management, common in schools that took the free Manager tier and grew into the paid one.
| Category | MDM |
| Authentication | API access token |
| Reaches | managerapi.mosyle.com or businessapi.mosyle.com |
| Needs an agent | No |
| Demo mode | Yes |
Capabilities
Section titled “Capabilities”device.lookupBySerial, device.get, device.listForUser,
device.searchSerial, device.sendCommand
Which lights up device details, the device page, serial autocomplete, and remote commands.
How the API behaves
Section titled “How the API behaves”Two things surprise people:
- Every call is a POST, including the ones that only read. There are no query strings anywhere.
- The access token goes in the body rather than in a header, alongside the operation being requested.
None of this affects configuration. It explains why the connector’s code looks different from the others.
Getting the credentials from Mosyle
Section titled “Getting the credentials from Mosyle”- Sign in to your Mosyle console as an administrator.
- Go to Organisation, Integrations, API (the exact path varies slightly by tier).
- Generate an API access token and copy it.
- Note whether you are on Manager (education) or Business, because the API base differs.
Some Mosyle operations additionally require an administrator email and password alongside the token. Both fields exist in the connector for that reason. Use a dedicated service account rather than a person’s login.
Configuring it in Plugboard
Section titled “Configuring it in Plugboard”Settings, Connectors, Mosyle, Configure.
Settings
Section titled “Settings”| Field | Default | Value |
|---|---|---|
baseUrl | https://managerapi.mosyle.com/v2 | Manager (education) is managerapi.mosyle.com/v2. Business is businessapi.mosyle.com/v1 |
demoMode | false | Return fixture data instead of calling Mosyle |
allowDeviceCommands | false | Allow device commands: lock, restart, shut down, and clear the passcode of an iOS device from the device page. Off keeps the connector read-only |
Credentials
Section titled “Credentials”| Field | Value |
|---|---|
accessToken | The API access token |
email | A Mosyle administrator email, if your operations need it |
password | That administrator’s password |
Save and test.
What Mosyle returns
Section titled “What Mosyle returns”| Field | Notes |
|---|---|
| Serial number | Uppercased |
| Model | Falls back to the device name |
| Device UDID | Used for subsequent calls |
| Assigned user | Email, falling back to username |
| OS version | |
| Status | Enrolment state |
| Battery percentage | Useful at a desk |
| Last check-in |
“It will not charge” is a common school repair, and a battery reading below ten is most of the diagnosis before the device is opened.
Mosyle does not carry warranty or AppleCare. For that, add Apple GSX.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause |
|---|---|
| “No Mosyle access token is configured” | The token field is empty |
401 or an authentication error | Wrong token, or the wrong API base for your tier |
| Test passes, devices do not resolve | Serials are matched uppercased. Confirm the device is in this Mosyle organisation |
| Everything returns sample devices | demoMode is still on |
| Some operations fail but lookup works | Those operations need the administrator email and password as well as the token |