What You'll Need
- Full administrator access to the Meraki Dashboard
- API access enabled for your Meraki organization
- ~3 minutes to complete setup
- Your Clariti account with adapter management permissions
Get Your Credentials
First, ensure API access is enabled for your organization. In the Meraki Dashboard, go to Organization > Settings and confirm that Dashboard API access is set to "Enable access."
Next, generate your personal API key: click your email/profile in the top-right corner, go to My Profile, scroll down to the API access section, and click Generate API key. Copy the key immediately — Meraki only shows it once.
The API key inherits the permissions of your Meraki admin account. For least-privilege access, consider creating a dedicated read-only admin account for Clariti.
Enter Credentials in Clariti
| Value from vendor console | Paste into Clariti field |
|---|---|
Meraki API Key | API Key |
Verify Connection
Click Test Connection in Clariti. A successful connection returns a green checkmark. The first data sync typically completes within a few minutes.
MX Security Events (optional, license-gated)
Separately from device inventory and offline-device alerts, Clariti also reads MX appliance security events — the IDS/IPS and anti-malware (AMP) detections your MX security appliance reports. Each event Clariti finds is raised as a finding so a compromised host or blocked exploit attempt is visible without opening the Meraki dashboard.
This data requires the MX Advanced Security license on your MX appliances. If your organization doesn't have that license, this is expected and not an error — Clariti simply reports no security-event findings; device inventory and offline-device findings are unaffected either way.
Appliance Firmware Status
Clariti also checks each network's MX security appliance for an available firmware upgrade. When the Meraki dashboard reports a newer firmware version than the appliance is currently running, Clariti raises a finding naming the network, the current firmware, and the version available. This is informational only — it does not affect any other score or metric, and a network with no MX appliance (switches/APs only) simply produces no finding for this check.
Systems Manager Device Compliance (existing-SM tenants only)
If your organization still has a network enrolled in Cisco's Systems Manager (SM) — Meraki's built-in MDM — Clariti reads each SM-managed laptop/phone's disk-encryption status and raises a finding for any device SM reports as unencrypted. Cisco discontinued Systems Manager for new purchases in June 2026, so this only applies to organizations that enrolled devices before then; if your organization has no SM-enabled network, this is expected and produces no findings — device inventory and every other check above are unaffected.
Troubleshooting
- 401 Unauthorized — The API key may have been revoked. Generate a new key from your Meraki profile and update it in Clariti.
- 403 Forbidden — Ensure Dashboard API access is enabled at the organization level and that the admin account has at least read-only access.
- Timeout — Meraki enforces a rate limit of 10 requests per second. Clariti handles throttling automatically with retry logic.