# 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](https://docs.coupler.io/sources/category/other/cisco-meraki/data-overview) article. If you're running into sync errors or missing data, check the [Common Issues](https://docs.coupler.io/sources/category/other/cisco-meraki/common-issues) article.
{% endhint %}