MT Sensor API and MQTT documentation now available!

Meraki Employee
Meraki Employee

MT Sensor API and MQTT documentation now available!

You can now engage with documentation for the recently announced MT Sensor API and MQTT telemetry stream, which can be leveraged to create custom visualizations for analysis, integrate sensor data with building management systems to increase efficiency, or store in a long-term cloud database for historical record keeping.


Explore the documentation here:!get-organization-sensor-readings-history


To learn more about the initial launch, check out the post by @David-H linked below. 



Ana Nennig
Building a reputation

Great documentation on the API thing.
Regarding MQTT, i would recommend "MQTT Explorer" or similiar when connected to the broker. This is straight forward. Simply copy&paste the topics and process it in the next application (e.g. smart home appliance)

Getting noticed

Hi, @ana_nennig. When might one want/need to use MQTT rather than the Dashboard API to collect sensor data?  

Head in the Cloud
Head in the Cloud

With MQTT, the MT sensors regularly push readings (typically in batches) to the broker. Clients can subscribe to get the data from the broker.


If you have an application that supports MQTT, it's pretty much a ready to go solution. If you have non-Meraki IoT devices that also support MQTT, you have the benefit of everything going into a single platform. The data goes from the sensor, via the local MR/MV device(s) that the sensor connects to, direct to the broker.


With the API, you pull the sensor data on demand, either for 'now' or the readings over a period of time. Then probably store them somewhere for other applications to read the data. You are getting the data from Dashboard, not direct from the sensors.


Thanks. That helps a lot. So, if I am already using a SaaS application to poll the dashboard API for MX, MS, MR, and Z data I can get IoT data as well (if it doesn’t make me go over my Dashboard API rate limit budget). If I were to use MQTT, does this have any cost against the Dashboard API rate limit?

Head in the Cloud
Head in the Cloud

MQTT is outside the rate limit, the traffic flows from the sensor location to the broker, there's no impact on Dashboard.


If you don't need the sensor data in real time, you can use this to minimize API calls...!get-organization-sensor-readings-history


There's also this in beta...!get-organization-sensor-readings-history-by-interval


Thanks again.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.