# 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