Meraki Dashboard API

Name: Meraki Dashboard API
Brand: Meraki Dashboard API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingapiKey799 EndpointsREST

For Agents

Automate Cisco Meraki cloud networking - provision networks, configure SSIDs, manage switches and security appliances, pull device telemetry, and audit configuration. API-key authenticated.

Use for: List all networks in a Meraki organisation, Update the SSID configuration for a wireless network, Get the list of clients currently connected to an access point, Retrieve device uptime and traffic statistics for a switch

Not supported: Does not configure non-Meraki Cisco gear, run on-premises CLI commands, or replace identity providers - use for cloud-managed Meraki organisation, network, and device automation only.

The Cisco Meraki Dashboard API exposes the full Meraki cloud-managed networking platform - organizations, networks, devices, wireless, switching, security appliances, cameras, cellular gateways, and Systems Manager - across 799 endpoints. It uses an X-Cisco-Meraki-API-Key header for authentication and follows REST conventions over JSON, which makes it well suited to network automation, multi-site provisioning, monitoring integrations, and compliance reporting in environments standardised on Meraki hardware.

Jentic One on Github

Install Jentic One Beta

Connect the Meraki Dashboard API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Meraki Dashboard API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmeraki.com%2Fmeraki" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmeraki.com%2Fmeraki" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Meraki Dashboard API.

Provision and configure networks across organisations including SSIDs, VLANs, and firewall rules

Manage Meraki MR access points, MS switches, MX security appliances, MV cameras, and MG cellular gateways from one client

Pull device telemetry - uptime, clients, traffic, channel utilisation - for monitoring dashboards

Apply network and switch configuration templates across multiple sites for consistent rollouts

GET STARTED

Start building with Meraki Dashboard API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Meraki Dashboard API for, with concrete tasks.

★ Multi-Site Network Provisioning

Network engineers automate provisioning of new branches by applying a network template through the API. The /organizations/{organizationId}/networks endpoints create the network, then template binding propagates SSIDs, VLANs, and firewall rules without manual UI configuration, which compresses a multi-day rollout into minutes per site.

Create a new network in the organisation, bind the 'branch-standard' template, claim the inventoried devices into it, and verify devices are online within 10 minutes.

Network Health Monitoring

Operations teams pull device status, client counts, and traffic statistics into Datadog or a custom NOC dashboard. The Meraki API exposes per-device uptime, channel utilisation, and connection metrics, which lets the monitoring system alert on offline devices, congested radios, or saturated WAN uplinks before users report issues.

Every minute, pull device status across the organisation and emit an alert for any device offline more than 5 minutes, including its network and serial number.

Compliance and Configuration Audit

Security and compliance teams periodically audit firewall rules, SSID configurations, and admin lists across all Meraki networks. The API enumerates these settings via /networks/{networkId}/appliance/firewall and related endpoints, which a scheduled audit job can compare against a desired baseline and flag drift.

For each network, fetch firewall L3 rules, compare to the approved baseline JSON, and produce a diff report identifying any rules added, removed, or modified.

AI Agent Network Operations

An AI assistant can answer 'is the New York office's wifi healthy', 'who's connected to the guest SSID', or 'why is this device offline' by chaining Meraki Dashboard API calls. Through Jentic, the agent loads only the relevant operations among 799 endpoints, which keeps the tool surface small enough for reliable selection while preserving full coverage of the platform.

Search Jentic for 'list meraki devices status', execute the device-statuses endpoint for the New York network, and return any device with status=offline along with last-seen timestamp.

Key Endpoints

799 endpoints — the cisco meraki dashboard api exposes the full meraki cloud-managed networking platform - organizations, networks, devices, wireless, switching, security appliances, cameras, cellular gateways, and systems manager - across 799 endpoints.

METHOD

PATH

DESCRIPTION

GET

/organizations

List organisations the API key has access to

GET

/organizations/{organizationId}/networks

List networks in an organisation

GET

/networks/{networkId}/devices

List devices in a network

GET

/networks/{networkId}/clients

List clients seen by the network

GET

/organizations/{organizationId}/devices/statuses

Get current status of all devices in the organisation

PUT

/networks/{networkId}/wireless/ssids/{number}

Update an SSID configuration

GET

/administered/identities/me

Get the authenticated identity

GET

/organizations

List organisations the API key has access to

GET

/organizations/{organizationId}/networks

List networks in an organisation

GET

/networks/{networkId}/devices

List devices in a network

GET

/networks/{networkId}/clients

List clients seen by the network

GET

/organizations/{organizationId}/devices/statuses

Get current status of all devices in the organisation

PUT

/networks/{networkId}/wireless/ssids/{number}

Update an SSID configuration

GET

/administered/identities/me

Get the authenticated identity

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Meraki Dashboard by hand means sending the X-Cisco-Meraki-API-Key header and hand-coding calls across a very large surface of organisation, network, and device endpoints against api.meraki.com. Through Jentic you install once, import the Meraki Dashboard API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Meraki puts the organisation and network ids in the URL path (/organizations/{organizationId}/..., /networks/{networkId}/...), so a rule can pin your agent to one network: it can read its devices and clients and nothing else. You choose the operations it may call, so a PUT that changes an SSID is included only if you add it.

Credential isolation

Your Meraki API key is stored once, encrypted, by your own Jentic One instance and injected as the X-Cisco-Meraki-API-Key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Meraki devices' or 'update an SSID', and Jentic returns just the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs for the full surface.

FAQs

Specific to using Meraki Dashboard API through Jentic.

What authentication does the Meraki Dashboard API use?

The API uses an API key passed in the `X-Cisco-Meraki-API-Key` header. Keys are issued per dashboard user and inherit that user's organisation and network access. Through Jentic the key is held in the encrypted vault and injected on each request so it never enters agent context.

Can I provision a new Meraki network from the API?

Yes. POST /organizations/{organizationId}/networks creates a network in an organisation, and subsequent calls under /networks/{networkId} configure SSIDs, VLANs, firewall rules, and device claiming. Network templates let you bind the new network to a baseline configuration in one call.

What are the rate limits for the Meraki Dashboard API?

Meraki enforces 10 requests per second per organisation, with bursts permitted via a token bucket. The API returns 429 with a Retry-After header when the limit is exceeded; production clients should implement exponential backoff and respect that header.

How do I list connected wireless clients through Jentic?

Run `pip install jentic`, search for `list meraki clients`, load /networks/{networkId}/clients, and execute with the network ID and a timespan. Jentic handles API-key injection and returns the structured client list.

Does the Meraki Dashboard API support all Meraki product lines?

Yes. The API covers MR access points, MS switches, MX security appliances, MV cameras, MG cellular gateways, and Systems Manager endpoint management - all under the same base URL and authentication.

Can I limit what my agent is allowed to do with the Meraki Dashboard API?

Yes. Because Meraki carries the organisation and network ids in the URL path (/organizations/{organizationId}/... and /networks/{networkId}/...), a rule in your own self-hosted Jentic One instance can pin your agent to a single network so it reads only that network's devices and clients. You decide which operations it may call, so a read like GET /networks/{networkId}/devices can be allowed while a PUT /networks/{networkId}/wireless/ssids/{number} that changes an SSID is included only if you add it. Your Meraki API key is held by your Jentic One instance and injected as the X-Cisco-Meraki-API-Key header at execution time, never entering the agent's context.