> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/integrations-store/device-management/cisco-meraki-integration.md). # Cisco Meraki Integration You can integrate with Cisco Meraki to create a single source of truth for IT assets and mobile devices. The integration imports network device data from Cisco Meraki into Asset Panda Pro to improve visibility into the deployed infrastructure. You can sync device data by type or configuration (such as company-owned versus company-managed), and manage devices directly in Asset Panda Pro. You can then identify the items that are currently deployed, in need of repair, or ready for replacement. Real-time tracking supports operational efficiency and cost control. ## Prerequisites * Active Asset Panda subscription * Cisco Meraki deployment in your organization * Admin access to both Cisco Meraki and Asset Panda *** ## Generate a Cisco Meraki API Key You authorize data access between Cisco Meraki and Asset Panda by entering your API credentials via a key generated from Meraki. The key establishes a secure connection that enables Asset Panda Pro to retrieve device data from your Meraki environment. {% hint style="info" %} API access must be enabled under **Organization > Settings > Dashboard API access**. {% endhint %} 1. Log into the Cisco Meraki dashboard. 2. Click your username in the upper-right corner to open your profile. 3. Under **API access**, click **Generate new API key**. 4. Copy and securely store the API key. This key is used in Asset Panda Pro to authenticate the connection. *** ## Add the Cisco Meraki Integration in Asset Panda 1. Log into Asset Panda Pro with an administrator account 2. Navigate to Settings icon **Settings** > **Account Management**. 3. Expand the appropriate account and module. 4. Click **Manage** in the **Integrations** card. 5. Select **Integrations Store**. 6. In the **Cisco Meraki** tile, click **Add**. The **Integrations in this module** tab is displayed. 7. In the **Cisco Meraki** tile, click **Configure**. 8. Enter the Meraki **API Key** 9. Click **Test and save connection**. If the connection is valid, a success message is displayed and a green check is displayed above the **Authentication** tab. 10. If the test is successful, click **Continue with Mapping**. 11. [Create a mapping](#create-a-mapping) to define the Meraki data to sync with the Asset Panda Pro collection: 1. Click **Add Mapping**. 2. Enter a **Mapping Name** (for example, `Meraki Devices Import`).

Sync direction is set to one-way from Meraki to Asset Panda Pro by default.

3. Select the **External Entity** to specify the kind of Meraki data to bring into Asset Panda: * **Administrators**: Import admin profiles for visibility into who manages network settings. * **Network Clients**: Sync connected client devices to track endpoints on the network. * **Network Devices**: Import Meraki-managed hardware such as routers, switches, and access points. * **Networks**: Bring in metadata and details about configured networks. * **Organization Devices**: Pull all devices associated with the Meraki organization for comprehensive inventory coverage. 4. Choose the **Collection** in Asset Panda where the Meraki data will be stored. 12. Configure field mapping to map Meraki fields to collection fields: 1. In the mapping configuration, select a **Unique Identifier** from the available Meraki fields. Only fields with guaranteed uniqueness should be used. The following options are supported: * **Network ID**: Unique ID representing each Meraki network. This is the recommended unique identifier when syncing network-level records. * **Name**: Name assigned to a network or device. Use only if naming conventions ensure uniqueness. * **Organization ID**: Identifier of the Meraki organization. This is not suitable as a record-level unique identifier. * **Product types**: General device categories (for example, wireless or switch). This value is not unique. * **Tags**: Custom metadata labels. Use only if standardized and uniquely applied. * **Time zone**: Network’s configured time zone. This value is not appropriate for uniqueness. 2. Map the selected Meraki field to a unique field in the Asset Panda Pro collection. 3. Add additional fields from Meraki to sync into Asset Panda Pro, such as model, status, IP address, or assigned configuration. Only fields marked as unique in Asset Panda collections are available for use as unique identifiers. 4. Click **Save** to complete the integration mapping. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://prohelp.assetpanda.com/integrations-store/device-management/cisco-meraki-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.