Extended Connector Integration for Cisco Meraki Assets

Oomnitza's Meraki Extended Connector allows organizations to pull device information from Meraki and populate it in Oomnitza. More info in Meraki can be found here: https://meraki.cisco.com/ 

Image result for meraki

Meraki Extended Connector


Details on setting up Oomnitza Extended Connectors can be found in Oomnitza's Articles on Connector Setup.

Note: In addition to the standard fields entered during setup, you'll also need your Meraki Network ID. To retrieve this:

  1. Log into Meraki
  2. Go to https://dashboard.meraki.com/api/v0/organizations and get the Organization ID of your organization
  3. Go to https://dashboard.meraki.com/api/v0/organizations/{organization_id}/networks, entering the Organization ID you just retrieved, and get the desired Network ID



Meraki's REST API uses Token Based authentication. Credentials for Meraki should be added to The Oomnitza Vault.

When creating the Credential, fill out the fields as follows:

Authorization type: API Key

Token Name: X-Cisco-Meraki-API-Key

API Key: <Your Meraki API Key>

Add to: Header


Standard Mappings

The following fields can be mapped from Meraki using Oomnitza's User Interface. For more information on creating Extended Connector Mappings, please see our article on Mapping Extended Connectors.

  • IMEI
  • Last User
  • Location
  • MEID
  • Name
  • OS
  • Phone Number
  • Public IP Address
  • SSID
  • Serial Number
  • System Model
  • System Type
  • Wifi MAC Address

Custom Mappings

Additional fields may be available through Meraki. For details on how to retrieve them, please reach out to support@oomnitza.com or see our article on Mapping Extended Connectors.

Did you know
You can also stream Cisco Meraki network asset data into Oomnitza! See Extended Connector Integration for Cisco Meraki Network Assets.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk