Kandji Integration
The Kandji + Asset Panda integration enables organizations to import Apple device data from Kandji into Asset Panda automatically for centralized asset tracking and visibility. By connecting these platforms, IT administrators can keep Asset Panda Pro collections current with hardware details from Kandji, reducing manual data entry and improving audit accuracy.
This is a one-way integration where Asset Panda Pro pulls data from Kandji. Asset Panda Pro does not modify or push data back to Kandji.
Prerequisites
Active Asset Panda subscription
Configured collection in Asset Panda for storing Kandji device records
Devices enrolled in Kandji
Admin-level access to both Kandji and Asset Panda
Kandji tasks
Set up access in Kandji
This process is required if you don’t have an account.
Visit Kandji.
Click Get Started or Request Demo.
Complete the onboarding process.
After your account is activated, log into your instance at the URL provided (for example,
https://yourcompany.kandji.io).
Generate an API Token
In the Kandji admin portal, select Settings > Access > API Token Management.
Click Add Token.
Enter a name for the token (for example,
Asset Panda Integration).Select the following permissions:
GET /devicesGET /device-details
Click Create Token.
Copy the token and store it securely. This will be used in Asset Panda Pro.
Record your Kandji URL (for example, https://yourcompany.kandji.io). This will be entered in Asset Panda Pro as the Server Host Name.
Asset Panda tasks
Set up the Kandji integration
Log into Asset Panda Pro with an administrator account
Navigate to
Settings > Account Management.Expand the appropriate account and module.
Click Manage in the Integrations card.
Select Integrations Store.
In the Kandji tile, click Add. The Integrations in this module tab is displayed.
In the Kandji tile, click Configure.
Enter the following details:
Base URL: Web address of the system to which you are connecting. This identifies the location of the service.
API Key: Paste the Kandji API key you copied earlier.
Click Test and save connection to verify the credentials. If the connection is valid, a success message is displayed and a green check is displayed above the Authentication tab.
Click Continue with mapping. The Mapping List page is displayed.
Create a mapping to define how data flows between Kandji and Asset Panda:
Enter the Mapping Name (for example,
Kandji Device Import).Select External Entity:
DevicesSelect your respective Collection in Asset Panda Pro (for example, ITAM).
In the Mapping & Sync Direction section, select a Unique Identifier from Kandji and then map it to a unique field in your Asset Panda collection. See Kandji unique identifier fields.
To add additional fields, select Add more and repeat step e.
Only fields marked as unique in Asset Panda Pro are available for mapping as a Unique Identifier.
Once your field mapping is complete, click Save to activate the integration.
Kandji unique identifier fields
Agent Installed
Boolean indicating if Kandji agent is installed on the device
Informational; not unique
Agent Version
Version number of the Kandji agent installed
Informational; not unique
Asset Tag
Custom asset tag assigned in Kandji
Use if standardized and unique
Blueprint ID
Internal identifier for the applied blueprint
Not unique; group-level data
Blueprint Name
Name of the assigned blueprint
Not unique; group-level data
Device ID
Internal Kandji-generated device ID
Recommended unique identifier
Device Name
User-assigned or system device name
Use only if standardized
First Enrollment
Date/time of first enrollment
Informational
Is Missing
Boolean indicating if the device is marked as missing
Not suitable as identifier
Is Removed
Boolean indicating if the device is marked as removed
Not suitable as identifier
Last Check In
Timestamp of last check-in with Kandji
Informational
Last Enrollment
Timestamp of most recent enrollment
Informational
Lost Mode Status
Current status of Lost Mode (on/off)
Informational
MDM Enabled
Indicates whether MDM is enabled on the device
Informational
Model
Model name of the device
Not unique
OS Version
Operating system version
Not unique
Platform
Device platform (e.g., macOS, iOS)
Not unique
Serial Number
Manufacturer's serial number
Common and acceptable identifier
Supplemental Build Version
Additional OS version info
Informational
Supplemental OS Version Extra
Additional OS version metadata
Informational
Tags
Custom tags applied to the device
Not unique
User Active
Boolean indicating if the user is active
Informational
User Email
Email address of the assigned user
Use only if guaranteed unique
User ID
Unique Kandji-assigned user ID
Acceptable if user-focused sync
User Is Archived
Boolean indicating user archive status
Informational
User Name
Display name of the user
Use only if consistently formatted
Last updated

