Skip to content

Cisco Meraki

Since version 3.5.0, IP Fabric supports API-based discovery for Cisco Meraki.

Meraki Requires the Following Settings to Be Applied:

  • API key – Generated in Meraki dashboard
  • Organizations ID – You can specify which organization will be included in the discovery process. If you do not specify, all available IDs will be used
  • Version – Only v1 is supported since IPF v5.0. Similarly to the original v0, even the latest API version has a lot of limitations (Meraki known issues)
  • Base URL – URL of the Meraki Dashboard API, e.g. or For organizations hosted in the China Dashboard, please use .cn instead of .com
  • Slug

Add Connection - Meraki REST

Login IP For Cisco Meraki

For the CLI (SSH/Telnet) discovery, the Login IP represents the IP address that platform uses to discover the device. IP Fabric discovers Cisco Meraki via API, and therefore different logic described below is used to assign Login IP parameter for Meraki devices in the main inventory.

LAN IP is considered to have the highest priority
------- key --> 'lanIp'
wan1Ip has the 2nd highest priority
------- key --> 'wan1Ip'
wan2Ip has the 3rd highest priority
------- key --> 'wan2Ip'
publicIp has the lowest priority
------- key --> 'publicIp'


The publicIp parameter can have duplicate values across inventory as more devices can be accessed via the same public IP address. It can also be inaccurate (e.g., when the WAN circuit fails to the secondary circuit) because it can take quite a long time to refresh the device’s public IP in the dashboard.

To understand what is being sent from Meraki’s Dashboard, we need to investigate the Discovery Snapshot and download the Tasker or Log File from the device:

Discovery Snapshot

The Tasker file contains complete communication between IP Fabric and Meraki Dashboard. We can use the device hostname to locate the JSON source:


Known Issue

Meraki API Limited Functionality