Kandji Integration
The Kandji + Asset Panda integration allows organizations to automatically import Apple device data from Kandji into Asset Panda for centralized asset tracking and visibility. By connecting these platforms, IT administrators can keep Asset Panda collections up to date with hardware details from Kandji, reducing manual data entry and improving audit accuracy.
This is a one-way integration where Asset Panda pulls data from Kandji. Asset Panda does not modify or push data back to Kandji.
Prerequisites
Active Asset Panda subscription
Devices enrolled in Kandji
Admin-level access to both Kandji and Asset Panda
A configured collection in Asset Panda for storing Kandji device records
Kandji Tasks
Setting up Access in Kandji
To sign up for Kandji (if you don’t have an account):
Visit Kandji.
Click Get Started or Request Demo.
Complete the onboarding process.
Once your account is activated, log in to your instance at the URL provided (e.g., https://yourcompany.kandji.io).
Generating an API Token
To generate an API token:
In the Kandji admin portal, go to Settings > Access > API Token Management.
Click Add Token.
Enter a name for the token (e.g., 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.
Asset Panda Tasks
Setting up Kandji in Asset Panda
Log in to Asset Panda with an admin account.
Go to Settings > Account Management.
Under the appropriate module, click Manage under Integrations.
Open the Integration Store for the selected account.
In the Integration Store, locate the Kandji tile and click Add.
Switch to the Integrations in this module tab.
Locate the Kandji tile and click Configure.
To authenticate Asset Panda with Kanji, enter the following details:
Base URL – The web address of the system you are connecting to. This identifies the location of the service.
API Key - In the API Key field, paste the Kandji API key you copied earlier.
Click Test and save connection to verify the credentials.
Once verified, click Continue with mapping to proceed.
Mapping Configuration
Once the connection is authenticated, you’ll be taken to the Mapping List screen. This is where you define how data flows between Kandji and Asset Panda.
Click Add mapping option to create a new mapping.
Provide a Mapping Name (e.g., "Kandji Device Import")
Select External Entity:
DevicesSelect your respective Collection in Asset Panda (e.g., ITAM)
In the Mapping & Sync Direction section, select a Unique Identifier from Kandji
Map this to a unique field in your Asset Panda collection
Add additional fields using the Add more option.
Unique Identifier Table
Kandji Unique Identifier Fields: Description & Guidance
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
Only fields marked as unique in Asset Panda will be available for mapping as a Unique Identifier.
Once your field mapping is complete, click Save to activate the integration.
Last updated

