One Dashboard API key puts your MX appliances, MS switches, MR access points and the rest of the Meraki estate on the same pane as your circuits — status, WAN loss and latency, licences, VPN tunnels and firmware — with outages ticketed in the IT Service Management (ITSM) system your team already works in.
The Meraki Dashboard knows the moment an access point drops, a WAN uplink loses packets or a licence is about to lapse — but only if someone is looking at it. SmartTile looks for you. Paste one API key and SmartTile discovers every organisation, network and device behind it, imports the ones you pick onto your sites, and from then on turns what Meraki reports into DOWN, UP, history and tickets — the same way it treats every other device you monitor.
Organisations, networks and devices found automatically. A preview shows every serial before import; each lands on a site matched from its network name, with model, serial, MAC and firmware filled in.
Meraki's own online / offline / alerting / dormant reading every 30 s, plus a direct ping of the LAN address where SmartTile can reach it. Every change is written to the device's state history.
Offline for 28 polls (14 min, adjustable per organisation): e-mail to your recipients and a ticket in your ITSM system at the device's location. Back up: a restored e-mail.
Every point of Meraki's uplink loss / latency series kept for 35 days, per-uplink bandwidth, and threshold tickets on loss, latency, temperature and bandwidth.
Every switch port (link, speed, PoE, errors, LLDP/CDP neighbour), wireless channel utilisation, cellular signal, MX security events and MT readings — refreshed every 10 min.
Licences and subscriptions checked every minute; e-mails at 90, 60, 30, 15, 5 and 1 days and on expiry, with co-term date shifts detected.
AutoVPN pairs and third-party IPsec peers polled every 60 s by VPNAutomate. A watched tunnel down 3 min opens one ticket; restored, it is noted and closed per your policy.
Running and available firmware per network into FirmwareAutomate advisories. Every dashboard configuration change, with the admin's name, lands in AccessAutomate.
| Meraki key belongs to | What works |
|---|---|
| Read-only organisation admin | Discovery, status, outage tickets, loss/latency, ports, licences, VPN monitoring, firmware advisories, change history, config backups. |
| Full organisation admin | Everything above, plus the buttons that change a device: reboot, blink LEDs, cycle a switch port. |
| Optional · off by default | Arming a Meraki firmware window from SmartTile, and VPN auto-heal for third-party tunnels. Each needs its own switch turned on. |
| The moment | Today | With SmartTile |
|---|---|---|
| An AP drops off | Someone notices in the Dashboard — or a user calls. | Meraki reports offline; after your threshold the device goes DOWN, the NOC is e-mailed and a ticket opens at that site. |
| The API goes quiet | Everything stays green because nothing says otherwise. | Three failed status reads in a row turn the organisation's devices UNKNOWN, never green, and the NOC is told monitoring is blind. |
| A device leaves its network | It shows the last good status for weeks. | Flagged not in any network, with who removed it and when, and a warning before anyone re-adds it. |
| A licence is expiring | Discovered the day it stops passing traffic. | A countdown of e-mails from 90 days out. |
/organizations/{id}/devices/statusesstatus every 30 s/organizations/{id}/devices/availabilitiesDOWN / UP and state history/organizations/{id}/devices/uplinksLossAndLatencyWAN loss and latency/organizations/{id}/networks · /devices · /inventory/devicesdiscovery, network membership/organizations/{id}/licenses · subscriptionslicence countdown/organizations/{id}/appliance/vpn/statusesAutoVPN reachability/networks/{id}/events (non_meraki_vpn)third-party tunnel truth/networks/{id}/firmwareUpgradesrunning and available firmware/organizations/{id}/switch/ports/bySwitchport telemetry (plus radios, sensors, security)/organizations/{id}/configurationChangeswho changed what/devices/{serial}/reboot · blinkLeds · switch/ports/cycleonly when a permitted user clicks/networks/{id}/firmwareUpgrades · appliance/vpn/siteToSiteVpnonly with firmware execution / auto-heal onEncrypted (AES-256-GCM) before it is stored and decrypted only to make a call. It is never sent back to the browser.
Each company adds its own key. Every Meraki screen and action is checked against the companies you belong to.
Viewers read; operators can ping, blink and cycle a port; only admins reboot. Every action, allowed or refused, is logged with user and time.
8 calls a second per organisation, backs off on 429, and pauses a key after 50 failures in a row instead of hammering it.
| Objection | Answer |
|---|---|
| “The Meraki Dashboard already alerts.” | It e-mails. SmartTile records the outage, opens the ticket at the right site in your ITSM system, and keeps history next to your circuits and other vendors. |
| “Will you change our config?” | Monitoring only reads. The buttons that change a device need a full-admin key and a permitted user; firmware windows and VPN auto-heal stay off until you turn them on. |
| “Our key sees many organisations.” | Hide the ones you don't want, and import only the devices you pick. |