Kandji

• How it works
• Prerequisites
• Setup Instructions
  • Step 1: Generate an API Token in Kandji
  • Step 2: Configure the Source in Datable
  • Step 3: Verify Data Collection
• Data Collected
• Configuration Options
  • Polling Frequency
  • Data Filtering
• Troubleshooting
  • No Data Appearing
  • Authentication Errors
  • Incomplete Data
• Security Considerations
• API Rate Limits
• Support

Datable integrates with Kandji to collect device management data, compliance information, and security events from your Apple device fleet managed through Kandji.

How it works

The Kandji integration uses the Kandji API to periodically collect device information, audit logs, and compliance data from your Kandji tenant. This data is then processed and made available for analysis in Datable.

Prerequisites

• Access to your Kandji tenant
• A Kandji API token
• Your Kandji subdomain

Setup Instructions

Step 1: Generate an API Token in Kandji

1. Log in to your Kandji web app
2. Navigate to Settings → Access
3. Select the API tab
4. Click Add API Token
5. Configure the token:
   • Name: Enter a descriptive name (e.g., "Datable Integration")
   • Permissions: Select appropriate read permissions
6. Click Create
7. Copy the API token - you'll need this for configuration

Important: Store this token securely. You won't be able to view it again.

Step 2: Configure the Source in Datable

1. Navigate to the Sources page in Datable
2. Select Kandji from the available sources
3. Provide the following configuration:
   • Source Name: A descriptive name for this source
   • API Key: The token you created in Step 1
   • Endpoint: Your Kandji subdomain (e.g., yourcompany.kandji.io)
4. Click Save to create the source

Step 3: Verify Data Collection

After configuration, Kandji data should begin flowing into Datable within a few minutes. You can verify this by:

1. Checking the source status in the Datable dashboard
2. Viewing recent events in the Data Explorer
3. Confirming device inventory data is being collected

Data Collected

The Kandji integration collects the following types of data:

• Device Inventory: Mac, iPhone, iPad, and Apple TV device information
• Compliance Status: Device compliance with configured baselines
• Audit Logs: Administrative actions and changes
• Security Events: Threat detections and security alerts
• Application Inventory: Installed applications and versions
• User Information: Device assignments and user details

Configuration Options

Polling Frequency

The integration polls Kandji at regular intervals. The default polling frequency is optimized to balance data freshness with API rate limits.

Data Filtering

You can configure filters to collect data from specific:

• Device groups
• Blueprints
• Device types

Troubleshooting

No Data Appearing

• Verify the API token is valid and has not been revoked
• Ensure the Kandji subdomain is correct
• Check that the API token has the necessary read permissions

Authentication Errors

• Regenerate the API token in Kandji
• Update the configuration in Datable with the new token

Incomplete Data

• Verify the API token has permissions for all required endpoints
• Check if certain device groups or blueprints require additional permissions

Security Considerations

• Use API tokens with minimal required permissions (read-only)
• Rotate API tokens regularly
• Monitor API token usage in Kandji's audit logs
• Consider restricting API access by IP address if available

API Rate Limits

Kandji implements API rate limiting. The integration handles rate limits automatically with:

• Exponential backoff retry logic
• Request throttling
• Efficient batch processing

Support

For additional support with the Kandji integration, please contact the Datable support team or refer to the Kandji API documentation.