Device Management

Cisco Meraki

Run your Cisco Meraki organizations conversationally - networks, devices, dashboard admins, inventory, and license overview.

Dex connects to the Cisco Meraki Dashboard API v1 so admins can manage a Meraki organization in plain language - read and update the organization, list and create networks, list devices and their statuses, manage dashboard admins, list and claim inventory, and read the license overview. Available as an MSP global app: one Dashboard API key is shared across every organization the admin can reach, and each Dex tenant is confined to its own Meraki Organization via the organization_id. Dex works organization-nested Dashboard API routes; network-by-id and device-by-serial routes stay out of scope on a tenant-scoped connection.

Start free →See Dex Live

What Dex does with Cisco Meraki

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Read and update a Meraki organization - name and API settings, confirmed before writing
List the organization roster on the MSP-master connection to map each tenant to its Organization
List networks in the organization, and create a network - with approval
List devices and device statuses across the organization
List, create, update, and revoke dashboard admins - privilege-impacting, with approval
List inventory devices and claim serials, orders, or licenses into inventory - with approval
Read the organization license overview
Deploy as an MSP global app - one Dashboard API key, each customer confined to its Meraki Organization

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>List the networks in this Meraki organization
>Which devices are offline right now? Show me the device statuses
>Show me the dashboard admins for this organization
>Add a read-only dashboard admin for jdoe@example.com and confirm the access level first
>What does the license overview look like for this organization?

Policy actions

Every action Dex can take on Cisco Meraki is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`meraki_list_organizations`	List Meraki organizations visible to the API key (master connection only)	—
`meraki_get_organization`	Read a Meraki organization's details	—
`meraki_update_organization`	Update a Meraki organization (name / API settings)	approval
`meraki_list_networks`	List networks in this Meraki organization	—
`meraki_create_network`	Create a network in this Meraki organization	approval
`meraki_list_devices`	List devices in this Meraki organization	—
`meraki_list_device_statuses`	List device statuses in this Meraki organization	—
`meraki_list_admins`	List dashboard admins for this Meraki organization	—
`meraki_create_admin`	Create a dashboard admin in this Meraki organization - privilege-impacting	approval
`meraki_update_admin`	Update a dashboard admin in this Meraki organization - privilege-impacting	approval
`meraki_delete_admin`	Revoke a dashboard admin in this Meraki organization - privilege-impacting	approval
`meraki_list_inventory_devices`	List inventory devices for this Meraki organization	—
`meraki_claim_inventory`	Claim serials, orders, or licenses into this Meraki organization's inventory - inventory-impacting	approval
`meraki_get_licenses_overview`	Read license overview for this Meraki organization	—

How to configure Cisco Meraki

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In the Meraki Dashboard, go to My Profile > API access (an organization admin) and generate a Dashboard API key - the value is shown once.
2
Confirm Organization > Settings has Dashboard API access enabled.
3
On the MSP-master connection, leave organization_id blank so Dex can list the organization roster to find each tenant's Organization ID.
4
For each tenant, look up the numeric Organization ID (GET /api/v1/organizations on the master, or Dashboard > Organization > Settings) and save it as organization_id on that tenant's connection.
5
Dex validates the key with a live call before saving and reports which auth scheme the account honoured. Copy the Organization ID exactly - it is longer than a JavaScript number, so a rounded value points at a different organization.

Credentials required

api_key: Meraki Dashboard API key from My Profile > API access (secret, shown once)
organization_id: This tenant's numeric Meraki Organization ID - leave blank on the MSP-master connection, set it on each tenant's connection for per-organization isolation

Requirements

•A Meraki Dashboard API key from an organization admin, with Dashboard API access enabled in Organization > Settings
•The numeric Organization ID for each tenant, copied exactly as plain decimal digits
•Dex works organization-nested Dashboard API routes; network-by-id and device-by-serial routes are default-denied on a tenant-scoped connection
•CoAdmin-only app - not available in Dex Go today
•For MSPs, deploy as a global app with per-organization scoping via organization_id