IPAM for Cisco Meraki networks, kept in sync automatically
Paste a Meraki Dashboard API key, choose the networks to track, and every client they've seen in the last 24 hours appears in your IPAM with its MAC, IP and hostname — refreshed every 2 hours, nothing to install. Stop maintaining a spreadsheet that's wrong before you save it.
Free Sandbox for manual IPAM · Meraki sync on Small Business, 14-day trial
| IP Address | Status | Label | Asset | Tags | Notes | |
|---|---|---|---|---|---|---|
| 10.0.20.1 | allocated | mx68-hq | MX security appliance | - | - | |
| 10.0.20.2 | allocated | ms120-idf1 | MS switch | - | - | |
| 10.0.20.10 | allocated ⚠ Conflict | vm-host-02 | Hypervisor | hypervisor | Also seen from vm-host-old | |
| 10.0.20.11 | allocated | hq-fileserver-01 | File server | storage | - | |
| 10.0.20.40 | allocated | mr36-office | MR access point | - | - | |
| 10.0.20.50 | reserved | Printer gateway | - | - | Held for VLAN 30 move |
The HQ Servers subnet after a Meraki sync.
Why Cisco Meraki networks outgrow the spreadsheet
The Dashboard already knows every client on every network. The sheet only knows what someone typed.
Stale the moment you save it
A new device joins the network, gets a lease, and the sheet never hears about it.
Conflicts you hear about from users
Someone sets a static that overlaps a DHCP lease, and the first sign is a device that keeps dropping.
No single view of what's actually on the wire
The dashboard knows every client; your documentation knows what you remembered to type.
How getIPAM syncs with Meraki
Three steps in the app. Nothing is installed on your network and nothing is imported until you confirm.
Connect
Paste a Meraki Dashboard API key (Dashboard → My Profile → API access). getIPAM lists the organisations that key can see; pick one, then tick the networks you want to track — each network counts as one site on your plan. Nothing is installed and no port is opened: getIPAM talks only to the Meraki cloud, and it only ever reads.
Discover
For each selected network, getIPAM pulls the clients Meraki has seen in the last 24 hours — wired or wireless, whatever the appliance — and turns each into an asset with its MAC, IP, hostname and name. Clients land in the subnets you've already defined; you own the structure, Meraki fills it in. You review the list before anything is written, and you can save the connection without importing at all. Matching is by MAC, so a device you'd already added by hand is reused, not duplicated — and manual records are never overwritten.
Stay in sync
Every 2 hours, or on demand. New clients are added, moved IPs are updated, and a client whose IP is already allocated to something else is flagged as a conflict rather than silently reassigned. Every change sync makes is written to the audit trail, tagged as system so it's distinguishable from edits by people.
Connect through the Meraki Dashboard API to import the clients your networks have seen as assets and keep their IP allocations in sync. Your hardware stays behind your firewall.
Review before anything is written to your IPAM. Nothing is imported until you confirm.
What gets synced
| From Meraki | Becomes in getIPAM | Example |
|---|---|---|
| Client — MAC | Asset (matched or created) | 9c:05:d6:1a:2b:3c |
| Client — IP | IP allocation in the matching subnet | 10.0.20.11 |
| Client — DHCP hostname / description | Asset hostname and name | hq-fileserver-01 / "HQ file server" |
| Organisation and networks | Used to choose what to sync; not stored on the asset | "HQ — Main office" |
getIPAM doesn't import your Meraki networks or VLANs as subnets — you define those in getIPAM (or upload them from a spreadsheet) so the sync has somewhere to land each client. Clients are matched to subnets by IP, not by which Meraki network saw them.
Everything you need to run Meraki IPAM without the busywork
| Subnet | Network | IP Usage | Utilization |
|---|---|---|---|
| LAN | 10.0.10.0/24 | 96 avail158 alloc | 62% |
| Servers | 10.0.20.0/24 | 29 avail3 res122 alloc100 dhcp | 88% |
| Free /24 | 10.0.21.0 – 10.0.29.255 | ||
| Guest | 10.0.30.0/24 | 223 avail31 alloc | 12% |
See your whole address space as a tree
Break a /16 into /24s and a /24 into /28s. Every level shows how full it is, so you know a subnet is filling up before it's full.
- Type
- Server
- Hostname
- hq-fileserver-01
- Location
- HQ comms room
- Owner
- andy
- MAC Address
- 9c:05:d6:1a:2b:3c
- Source
- Meraki integration
- Last updated
- Today, 09:15
- IP assigned 10.0.20.11by Meraki Integration · Today, 09:15
- Asset updatedby andy · Yesterday, 18:02Location: — → Rack 1
- Asset createdby Meraki Integration · 12 Aug, 14:30
Every IP tied to a real device
Each synced client is an asset, not just a row: MAC, IP, the DHCP hostname, and the description if someone has labelled the client in the Dashboard — plus whatever you add: owner, location, tags. Manual and synced records sit side by side, and the source is shown on every one.
Conflicts flagged, never papered over
If a client shows up on an IP that's already allocated to something else, getIPAM records a conflict against the new client and leaves the existing allocation untouched. You get an email digest of new devices and conflicts after each sync.
Built for teams running Cisco Meraki
Multi-site business
You run several Meraki networks under one organisation and need one address plan that covers all of them, not a spreadsheet per site.
MSP
You look after Meraki networks for a handful of clients and want one place that shows what's actually connected at each.
Growing IT team
You've inherited a Meraki estate and an IP sheet that was last accurate the day it was made.
Planning a new VLAN or subnet split?
Use the free getIPAM Subnet Calculator to carve up a CIDR block, then create the subnets in getIPAM so the Meraki sync has somewhere to land.
Pricing for Cisco Meraki networks
Start free. Add Meraki sync when you're ready to stop typing.
Small Business
Small IT teams and MSPs
- 5 users
- 5,000 IP addresses · 5,000 assets
- 5 sites — one per Meraki network
- Meraki sync every 2 hours
- Full REST API
- Excel import/export
- Email alerts for new devices and conflicts
- 12-month audit history
- 14-day free trial
Free Sandbox
Manual IPAM, no commitment
- 1 user
- 250 IPs
- Manual entry and Excel import/export
- 30-day audit history
- Meraki sync
- API
Need more users or sites? Compare all plans →
Meraki IPAM, common questions
How does getIPAM connect to my Meraki network?
Through the Meraki Dashboard API, using a Dashboard API key you create under My Profile → API access. You pick the organisation and the networks to track; getIPAM never connects to your hardware directly.
Do I need to open a port or run an agent?
No. There's no inbound connection to your network and nothing to install. getIPAM reads from the Meraki cloud your hardware already reports to.
Does getIPAM change anything in my Meraki configuration?
No. getIPAM only ever reads from the Dashboard API — it lists organisations and networks, and reads the client list for the networks you selected. It never sends a write.
Which Meraki setups are supported?
Any organisation you can reach with a Dashboard API key. Clients are read per network, so anything a network has seen is included, whichever Meraki appliance saw it.
How many networks can I sync?
As many as your plan allows: each Meraki network counts as one site, so Small Business covers up to five networks under one integration.
What counts as a "connected" client?
Any client the network has seen in the last 24 hours, as reported by the Dashboard API. A device that's been off for longer than that won't appear in the next sync, but its existing record in getIPAM is left alone.
What does the Meraki sync bring in?
Clients: MAC address, IP address, DHCP hostname and description. Each becomes an asset with an IP allocation in the matching subnet. Networks, VLANs and DHCP settings are not imported — you define subnets in getIPAM.
What happens to records I've entered by hand?
They're never overwritten. Matching is by MAC, so a device you added manually is reused rather than duplicated, and its name and hostname are left as you set them. Subnets are never created or changed by sync.
What if a synced client's IP is already in use?
getIPAM records a conflict against the incoming client and leaves the existing allocation untouched, and includes it in your email digest. Nothing is reassigned automatically.
How often does it sync, and what if a sync fails?
Every 2 hours, plus on demand. A failed run is shown against the integration with the error; existing records are left as they were and the next run carries on.
Can I import my existing spreadsheet first?
Yes. Upload an Excel file to create subnets and assets, then connect Meraki. Synced and manual records live side by side with the source shown on each.
Can I self-host getIPAM?
No, getIPAM is a hosted service. For systems without a cloud API, Excel import/export is the way to bring data in.
Connect your Meraki networks and retire the spreadsheet.
Create your account, paste a Dashboard API key, and watch the Servers subnet fill itself in. Start a 14-day Small Business trial — cancel any time.
Also works with: Ubiquiti UniFi · Juniper Mist