Skip to content

Meraki ​

Reads the Cisco Meraki Dashboard API: organizations (= customers), their devices per model and the license status.

Credentials (gear icon) ​

API key(s) of the Meraki dashboard (profile → API access). Multiple keys are supported in case customers are managed through separate dashboard accounts.

Metrics ​

  • Devices per model series (e.g. MX68, MS120, MR46) — one metric per model, value = unit count.
  • Active license per organization incl. edition and expiration date (co-term and per-device licensing are both supported).

View ​

  • Organizations with device counts and license status; expiring licenses are flagged according to their Meraki status.
  • Customer detail popup with device list and license name.
  • Unused inventory devices (purchased but not assigned to any network) are shown as a cleanup hint.

Specifics ​

  • Organizations that cannot be read — no access any more (403), or a licence read that fails for the night — are left out of the snapshot as a whole and recorded as not read: they keep the figures of their last snapshot instead of being stored with a part of them. An organization deleted in the dashboard is simply no longer listed and is gone at once. If one of several API keys cannot list its organizations, whatever the last snapshot knew stays not read until the key works again.
  • With per-device licensing, a licence counts while it is not expired — an expired licence keeps its record, and a renewed device used to show two.
  • An organization reachable through several keys is read with the first key that can read it.
  • Organization IDs are stable → automatic rename detection.