> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/other/cisco-meraki.md).

# Cisco Meraki

Pull Cisco Meraki network infrastructure, devices, and admin data into Google Sheets or BigQuery via Coupler.io.

Cisco Meraki is a cloud-managed IT platform for networking, security, and device management. It gives IT teams centralized visibility and control over their network infrastructure — from switches and access points to security appliances — all through a single dashboard.

Connecting Cisco Meraki to Coupler.io lets you pull your network and device data into any reporting or analytics tool without writing a single line of code.

## Why connect Cisco Meraki to Coupler.io?

* **Centralize network reporting** — combine device, network, and admin data in one place for easier oversight
* **Monitor API usage** — track API request logs to spot unusual activity or quota issues
* **Audit admin access** — export admin and SAML configurations for compliance and security reviews
* **Automate refreshes** — keep your dashboards and reports up to date on a schedule

## Prerequisites

Before you connect, make sure you have:

* A Cisco Meraki account with at least **read-only** API access
* A Meraki **API key** — you can generate one in your Meraki Dashboard under **My Profile → API access**
* API access enabled for your organization (an org admin must turn this on under **Organization → Settings**)

{% hint style="success" %}
If you're new to Coupler.io, start with the **Organization devices** entity — it gives you the broadest view of your infrastructure right away.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow.** In Coupler.io, click **Add data flow**, then search for and select **Cisco Meraki** as your source.
{% endstep %}

{% step %}
**Enter your API key.** Paste your Meraki API key into the API key field. If you haven't generated one yet, go to your Meraki Dashboard → **My Profile** → **API access** → **Generate new API key**.
{% endstep %}

{% step %}
**Select an entity.** Choose the data entity you want to import — for example, Organization devices or Organization networks. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to define how far back you want Coupler.io to pull historical data.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync and confirm everything is working.
{% endstep %}
{% endstepper %}

## Cisco Meraki data overview

Cisco Meraki exposes network infrastructure data across eight entities. Whether you're auditing admin access, tracking device health, or analyzing API usage patterns, Coupler.io can pull all of this into your reporting tool of choice.

## Available entities

| Entity                        | What it contains                                                        |
| ----------------------------- | ----------------------------------------------------------------------- |
| Organizations                 | Org name, ID, licensing info, and configuration details                 |
| Datacenters                   | Datacenter locations and network infrastructure metadata                |
| Organization networks         | Network IDs, names, types, tags, and time zones                         |
| Organization devices          | Device serial numbers, models, firmware, status, and network assignment |
| Organization API requests     | Timestamps, endpoints, response codes, admin IDs, and source IPs        |
| Organization admins           | Admin names, emails, roles, and account status                          |
| Organization SAMLs            | SAML provider configurations and role mappings                          |
| Organization network settings | DNS settings, traffic shaping policies, and other network-level config  |

## Metrics and dimensions by entity

#### Organizations

| Field            | Type      | Description                          |
| ---------------- | --------- | ------------------------------------ |
| id               | Dimension | Unique organization identifier       |
| name             | Dimension | Organization display name            |
| url              | Dimension | Dashboard URL for the organization   |
| api\_enabled     | Dimension | Whether API access is enabled        |
| licensing\_model | Dimension | Licensing type (co-term, per-device) |

#### Organization devices

| Field       | Type      | Description                                |
| ----------- | --------- | ------------------------------------------ |
| serial      | Dimension | Device serial number                       |
| model       | Dimension | Device model (e.g., MX67, MR46)            |
| name        | Dimension | Device name as configured in the dashboard |
| network\_id | Dimension | ID of the network the device belongs to    |
| firmware    | Dimension | Installed firmware version                 |
| status      | Dimension | Online/offline/alerting status             |
| mac         | Dimension | MAC address                                |
| lan\_ip     | Dimension | Local IP address                           |

#### Organization networks

| Field            | Type      | Description                                      |
| ---------------- | --------- | ------------------------------------------------ |
| id               | Dimension | Unique network identifier                        |
| name             | Dimension | Network display name                             |
| type             | Dimension | Network type (wireless, appliance, switch, etc.) |
| time\_zone       | Dimension | Configured time zone                             |
| tags             | Dimension | Custom tags applied to the network               |
| organization\_id | Dimension | Parent organization ID                           |

#### Organization API requests

| Field          | Type      | Description                            |
| -------------- | --------- | -------------------------------------- |
| ts             | Dimension | Request timestamp                      |
| admin\_id      | Dimension | ID of the admin who made the request   |
| method         | Dimension | HTTP method (GET, POST, PUT, DELETE)   |
| host           | Dimension | API host                               |
| path           | Dimension | API endpoint path                      |
| query\_string  | Dimension | Query parameters sent with the request |
| response\_code | Metric    | HTTP response code                     |
| source\_ip     | Dimension | IP address of the requester            |

#### Organization admins

| Field           | Type      | Description                        |
| --------------- | --------- | ---------------------------------- |
| id              | Dimension | Admin account ID                   |
| name            | Dimension | Admin display name                 |
| email           | Dimension | Admin email address                |
| org\_access     | Dimension | Organization-level permission role |
| account\_status | Dimension | Active or pending status           |
| last\_active    | Dimension | Timestamp of last login            |

#### Organization SAMLs

| Field                         | Type      | Description                         |
| ----------------------------- | --------- | ----------------------------------- |
| id                            | Dimension | SAML configuration ID               |
| x509\_cert\_sha1\_fingerprint | Dimension | Certificate fingerprint for the IdP |
| slo\_logout\_url              | Dimension | Single logout URL                   |

#### Organization network settings

| Field                         | Type      | Description                         |
| ----------------------------- | --------- | ----------------------------------- |
| network\_id                   | Dimension | Associated network ID               |
| local\_status\_page\_enabled  | Dimension | Whether the local status page is on |
| remote\_status\_page\_enabled | Dimension | Whether remote status page is on    |

## Useful data combinations

* **Devices + Networks** — Use a **Join** transformation on `network_id` to see which devices belong to which network, including the network's name and type.
* **API requests + Admins** — Join on `admin_id` to map raw API logs to human-readable admin names and roles — useful for access audits.
* **Devices across multiple orgs** — Use **Append** to combine Organization devices from multiple Meraki organizations into a single unified device inventory.
* **API request volume over time** — Use **Aggregate** on the API requests entity to count requests by day, admin, or response code for usage trend analysis.

## Use cases by role

{% tabs %}
{% tab title="IT / Network Ops" %}

* Export a full device inventory (model, firmware, status, network) into a spreadsheet for asset tracking
* Monitor firmware versions across all devices to identify upgrade candidates
* Track online/offline device status over time to spot recurring outages
* Join devices with networks to understand which sites are affected by specific hardware
  {% endtab %}

{% tab title="Security & Compliance" %}

* Audit admin accounts and roles to ensure least-privilege access is enforced
* Review SAML configurations for IdP alignment during compliance assessments
* Export API request logs to detect unusual access patterns or unauthorized API calls
* Send admin and API logs to ChatGPT or Claude for anomaly summarization
  {% endtab %}

{% tab title="IT Management" %}

* Build executive dashboards in Looker Studio showing network coverage and device health by site
* Track organization-level API usage to manage quota and identify integration issues
* Combine data from multiple Meraki organizations using Append for a group-wide infrastructure view
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* API access must be explicitly enabled per organization — devices and networks won't appear if the org API toggle is off
* The API requests entity returns logs within the window defined by your start date; very long date ranges may return large volumes of data
* Device status (online/offline) reflects a point-in-time snapshot at sync time, not a real-time feed
* SAML configurations are only available if your organization uses SAML-based authentication
* Some fields (like `tags` on networks) may be empty arrays if no tags have been applied in the Meraki Dashboard

## Cisco Meraki common issues

### Connection issues

<details>

<summary>My API key is rejected even though it looks correct</summary>

Double-check that the key was copied without leading or trailing spaces. Also confirm that API access is enabled for your Meraki organization — an org admin must turn it on under **Organization → Settings → Dashboard API access**. If the key was recently regenerated, the old key is immediately invalidated.

</details>

<details>

<summary>The connection times out during the initial sync</summary>

This often happens when the start date is set too far back and the API requests entity returns a very large number of records. Try setting a more recent start date and re-running. Once the initial sync succeeds, you can gradually move the start date back.

</details>

### Missing data

<details>

<summary>No devices appear in the Organization devices entity</summary>

Verify that the API key belongs to a user with access to the organization that contains those devices. Also check that the devices are assigned to a network — unassigned devices may not appear in API responses.

</details>

<details>

<summary>Some organizations or networks are missing from the results</summary>

The API key used must have access to all organizations you expect to see. If your Meraki account manages multiple organizations, confirm that the key has the appropriate admin role in each one. Keys scoped to a single org won't return data from other orgs.

</details>

<details>

<summary>The Organization API requests entity returns no rows</summary>

Make sure your start date is set within a range where API activity actually occurred. Meraki's API request log retention is limited — logs older than a certain period may no longer be available through the API.

</details>

### Permission errors

<details>

<summary>I get a 403 Forbidden error when syncing</summary>

The API key you're using doesn't have sufficient permissions for the requested entity. Read-only access is the minimum required, but some endpoints (like SAML configurations) may require org-level admin access. Ask your Meraki org admin to review and update your role.

</details>

<details>

<summary>SAML entity returns empty or errors out</summary>

SAML configuration data is only accessible if your organization has SAML enabled and your API key belongs to an org admin. If neither condition is met, this entity will return no data or a permission error.

</details>

### Data discrepancies

<details>

<summary>Device status in Coupler.io doesn't match what I see in the Meraki Dashboard</summary>

Device status is captured as a snapshot at the time of the sync. If a device went offline after the last sync, the status in your destination won't reflect that until the next run. Increase your refresh frequency to keep status data more current.

</details>

<details>

<summary>API request counts differ between Coupler.io and the Meraki Dashboard</summary>

Meraki's Dashboard may display aggregated or deduplicated counts, while the API returns raw log entries. Differences can also result from the start date window you've configured — make sure it aligns with the time range you're comparing against.

</details>

### Rate limits

<details>

<summary>Syncs fail partway through with a rate limit error</summary>

Meraki's API enforces a limit of **5 requests per second** per API key. If you have a large number of organizations, networks, or devices, the connector may hit this limit during a full sync. Try running the data flow during off-peak hours or splitting entities into separate data flows to reduce concurrent API pressure.

</details>

## Cisco Meraki FAQ

<details>

<summary>Where do I find my Cisco Meraki API key?</summary>

Log in to your Meraki Dashboard, click your username in the top-right corner, and go to **My Profile**. Scroll down to the **API access** section and click **Generate new API key**. Copy the key immediately — Meraki only shows it once. You'll also need to make sure API access is enabled for your organization under **Organization → Settings → Dashboard API access**.

</details>

<details>

<summary>Can I pull data from multiple Meraki organizations in one data flow?</summary>

Yes. Add each organization as a separate source within the same data flow, then use the **Append** transformation to combine their data into a single output. This is useful for building a unified device inventory or admin list across multiple orgs.

</details>

<details>

<summary>Which entities are best for security auditing?</summary>

Start with **Organization admins** to review who has access and at what permission level, **Organization SAMLs** to verify IdP configurations, and **Organization API requests** to detect unusual or unauthorized API activity. You can send this combined data to an AI destination like Claude or ChatGPT to help summarize anomalies.

</details>

<details>

<summary>Does Coupler.io sync real-time device status from Meraki?</summary>

No — Coupler.io captures a snapshot of device status at the time of each sync. If a device goes offline between syncs, you won't see that change until the next run. For near-real-time monitoring, set your data flow to refresh hourly.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

You can set any start date using the date picker in the data flow settings. However, Meraki's API has retention limits for certain data — particularly **API request logs**. In practice, logs older than a few months may no longer be available through the API even if you set an earlier start date.

</details>

<details>

<summary>Why does the Organization API requests entity return so much data?</summary>

Every API call made against your Meraki organization is logged, so busy environments can generate thousands of records per day. Set a recent start date to limit the initial volume, and use the **Aggregate** transformation in Coupler.io to summarize request counts by day, admin, or response code instead of loading every raw row.

</details>

<details>

<summary>Can I use Cisco Meraki data with AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Meraki data — such as device lists, admin logs, or API request summaries — directly to these tools for analysis, anomaly detection, or natural language reporting.

</details>

<details>

<summary>What's the difference between Organization networks and Organization network settings?</summary>

**Organization networks** contains metadata about each network — its name, type, time zone, and tags. **Organization network settings** contains the configuration applied to those networks, like local status page toggles and traffic policies. Join them on `network_id` for a complete picture of each network's identity and behavior.

</details>

{% hint style="info" %}
For field-level details on each entity, see the [Data Overview](#cisco-meraki-data-overview) article. If you're running into sync errors or missing data, check the [Common Issues](#cisco-meraki-common-issues) article.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/other/cisco-meraki.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
