How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cisco Meraki

Cisco Meraki Sensor API

The sensor API from Cisco Meraki — 13 operation(s) for sensor.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cisco Meraki Sensor API is one of 21 APIs that Cisco Meraki publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sensor. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and authentication docs.

This API exposes 19 operations across 13 paths. It is described by OpenAPI 3.2.0, at version 1.73.0.

Requests are made against a single base URL, https://api.meraki.com/{basePath}.

19 operations 13 paths 0 schemas 1 DELETE13 GET2 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.73.0
Base URL
https://developer.cisco.com/meraki/webhooks/
Authentication
HTTP Bearer
Contact
Meraki Developer Community
Resource Areas
1

Authentication & Security 1

Cisco Meraki Sensor API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 19

Across 13 paths, the API surfaces 19 operations — 1 DELETE, 13 GET, 2 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

sensor 19
GET
/devices/{serial}/sensor/commands
Returns a historical log of all commands
getDeviceSensorCommands 9 params → 200
POST
/devices/{serial}/sensor/commands
Sends a command to a sensor
createDeviceSensorCommand 1 param body → 201
GET
/devices/{serial}/sensor/commands/{commandId}
Returns information about the command's execution, including the status
getDeviceSensorCommand 2 params → 200
GET
/devices/{serial}/sensor/relationships
List the sensor roles for a given sensor or camera device.
getDeviceSensorRelationships 1 param → 200
PUT
/devices/{serial}/sensor/relationships
Assign one or more sensor roles to a given sensor or camera device.
updateDeviceSensorRelationships 1 param body → 200
GET
/networks/{networkId}/sensor/alerts/current/overview/byMetric
Return an overview of currently alerting sensors by metric
getNetworkSensorAlertsCurrentOverviewByMetric 1 param → 200
GET
/networks/{networkId}/sensor/alerts/overview/byMetric
Return an overview of alert occurrences over a timespan, by metric
getNetworkSensorAlertsOverviewByMetric 5 params → 200
GET
/networks/{networkId}/sensor/alerts/profiles
Lists all sensor alert profiles for a network.
getNetworkSensorAlertsProfiles 1 param → 200
POST
/networks/{networkId}/sensor/alerts/profiles
Creates a sensor alert profile for a network.
createNetworkSensorAlertsProfile 1 param body → 200
GET
/networks/{networkId}/sensor/alerts/profiles/{id}
Show details of a sensor alert profile for a network.
getNetworkSensorAlertsProfile 2 params → 200
PUT
/networks/{networkId}/sensor/alerts/profiles/{id}
Updates a sensor alert profile for a network.
updateNetworkSensorAlertsProfile 2 params body → 200
DELETE
/networks/{networkId}/sensor/alerts/profiles/{id}
Deletes a sensor alert profile from a network.
deleteNetworkSensorAlertsProfile 2 params → 204
GET
/networks/{networkId}/sensor/mqttBrokers
List the sensor settings of all MQTT brokers for this network
getNetworkSensorMqttBrokers 1 param → 200
GET
/networks/{networkId}/sensor/mqttBrokers/{mqttBrokerId}
Return the sensor settings of an MQTT broker
getNetworkSensorMqttBroker 2 params → 200
PUT
/networks/{networkId}/sensor/mqttBrokers/{mqttBrokerId}
Update the sensor settings of an MQTT broker
updateNetworkSensorMqttBroker 2 params body → 200
GET
/networks/{networkId}/sensor/relationships
List the sensor roles for devices in a given network
getNetworkSensorRelationships 1 param → 200
GET
/organizations/{organizationId}/sensor/gateways/connections/latest
Returns latest sensor-gateway connectivity data.
getOrganizationSensorGatewaysConnectionsLatest 5 params → 200
GET
/organizations/{organizationId}/sensor/readings/history
Return all reported readings from sensors in a given timespan, sorted by timestamp
getOrganizationSensorReadingsHistory 10 params → 200
GET
/organizations/{organizationId}/sensor/readings/latest
Return the latest available reading for each metric from each sensor, sorted by sensor serial
getOrganizationSensorReadingsLatest 7 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-meraki-sensor-api-openapi.yml Raw ↑

Other APIs Cisco Meraki publishes across the network.

Meraki Webhooks
AE Profile APIs.io
Cisco Meraki Administered API
AE Profile APIs.io
Cisco Meraki Appliance API
AE Profile APIs.io
Cisco Meraki Camera API
AE Profile APIs.io
Cisco Meraki Campus Gateway API
AE Profile APIs.io
Cisco Meraki Cellular Gateway API
AE Profile APIs.io
Cisco Meraki Devices API
AE Profile APIs.io
Cisco Meraki Insight API
AE Profile APIs.io
Cisco Meraki Licensing API
AE Profile APIs.io
Cisco Meraki Networks API
AE Profile APIs.io
Cisco Meraki Organizations API
AE Profile APIs.io
Cisco Meraki Sm API
AE Profile APIs.io
#Sensor
← Back to C APIs
API Details
ID
cisco-meraki:cisco-meraki-sensor-api
Base URL
https://developer.cisco.com/meraki/webhooks/
Docs
https://developer.cisco.com/meraki/webhooks/
Provider
Cisco Meraki
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cisco-meraki-sensor-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cisco-meraki-sensor-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cisco Meraki Sensor API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.