Iru (formerly Kandji)
Iru is the current name for Kandji. Plugboard’s connector provides read-only
Apple device lookup and fleet inventory. The saved connector identifier remains
kandji, so existing configurations and device records continue to match.
Older Plugboard versions show Kandji in the connector picker.
| Category | MDM |
| Authentication | API token |
| API origin | https://yourorg.api.iru.com or the existing https://yourorg.api.kandji.io |
| Needs an agent | No |
| Demo mode | No |
Iru confirms that migrated tenants can use either API domain and existing Kandji integrations continue to work. A branding change does not require you to replace a working API origin. See the Iru brand update.
Capabilities
Section titled “Capabilities”device.lookupBySerial, device.get and paginated device.list support device
details and fleet inventory. This connector does not send remote commands or
implement Iru Identity, Compliance, application inventory or the full range of
Windows/Android features in Iru’s wider platform.
Create an API token
Section titled “Create an API token”- In Iru, open Account Menu, Access, API tokens. Older Kandji navigation places this under Settings, Access.
- Create a token named
Plugboardwith the device list and device details read permissions required for this connector. - Copy the token into Plugboard’s credential field and keep its permissions limited to these reads.
- Note the API origin shown for your tenant. It differs from your browser
console URL. Enter the origin without
/api/v1; Plugboard adds API paths.
The Iru upgrade guide
documents the current Access menu and the change to yourorg.iru.com for the
browser console. Do not migrate your Iru tenant merely to rename this connector.
Configure Plugboard
Section titled “Configure Plugboard”Open Admin, Connectors, Iru (formerly Kandji), Configure; select Kandji on an older Plugboard deployment.
| Field | Value |
|---|---|
baseUrl |
API origin, for example https://yourorg.api.iru.com; existing Kandji API origins are supported |
consoleUrl |
Optional browser console URL, for example https://yourorg.iru.com, used by Open Iru console |
apiToken |
Your device-read API token, entered in Credentials |
Choose Save and test. Updated builds report Connected to Iru; older builds report Connected to Kandji. Existing tokens/configurations are not rewritten.
Inventory limits
Section titled “Inventory limits”Device lookup maps serial number, model, device ID and assigned user. The fleet
mapper reports only its declared summary fields; uncollected fields remain empty.
It does not fetch every device’s extended /details inventory on each sync.
Warranty and AppleCare are not supplied by this connector; see
Apple GSX.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Check |
|---|---|
401 on test |
The token value and whether Iru has revoked it |
403 |
Device list/details read permissions on the token |
| No matching device | The serial exists in the tenant; Plugboard uppercases lookup serials |
| DNS or connection failure | The API origin matches your tenant; do not use its sign-in URL |
| No console link | Configure consoleUrl separately from the API origin |
Alternatives
Section titled “Alternatives”Jamf Pro, Intune, Mosyle and Chrome Enterprise.